fxruby-users Mailing List for FXRuby (Page 2)
Status: Inactive
Brought to you by:
lyle
Menu
▾
▴
fxruby-users — General-purpose discussion list for FXRuby
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(75) |
Jul
(90) |
Aug
(61) |
Sep
(56) |
Oct
(56) |
Nov
(39) |
Dec
(83) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(56) |
Feb
(45) |
Mar
(61) |
Apr
(40) |
May
(95) |
Jun
(79) |
Jul
(63) |
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
|
From: Simon S. <ne...@ad...> - 2004-07-08 11:43:46
|
On Thursday 08 July 2004 09:42, Meino Christian Cramer wrote: > From: Simon Strandgaard <ne...@ad...> > > > AEditor has only been tested with fox 1.0.x so far. > > I hanv't tried 1.2.x yet (will try 1.2.x when I get back from vacation). > > Ok, I got it running with FOX/FXRuby 1.0.x Im happy to hear that. > As soon as FXRuby/FOX 1.2.x is installed in parallel, nothing works > anymore: hmm.. undefined symbol.. it seems as fxruby 1.2 and 1.0 cannot coexist. I have no solution to this. Maybe Lyle Johnson knows what is happening. =2D- Siimon Strandgaard /usr/lib/ruby/gems/1.8/gems/fxruby-1.2.0/ext/fox/fox.so: /usr/lib/ruby/gem= s/1.8/gems/fxruby-1.2.0/ext/fox/fox.so:=20 undefined symbol: XcursorSupportsARGB=20 =2D /usr/lib/ruby/gems/1.8/gems/fxruby-1.2.0/ext/fox/fox.so (LoadError) =A0 from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:54:in `require_gem' =A0 from /usr/lib/ruby/site_ruby/1.8/fox.rb:11 =A0 from /usr/lib/ruby/site_ruby/1.8/aeditor/main.rb:13:in `require' =A0 from /usr/lib/ruby/site_ruby/1.8/aeditor/main.rb:13:in=20 `get_version_fox_toolkit' =A0 from /usr/lib/ruby/site_ruby/1.8/aeditor/cli.rb:66:in `show_version' =A0 from /usr/lib/ruby/site_ruby/1.8/aeditor/cli.rb:20:in `parse' =A0 from /usr/lib/ruby/site_ruby/1.8/aeditor/cli.rb:19:in `call' =A0 from /usr/lib/ruby/1.8/optparse.rb:1269:in `order!' =A0 =A0... 6 levels... =A0 from /usr/lib/ruby/site_ruby/1.8/aeditor/cli.rb:83:in `parse' =A0 from /usr/lib/ruby/site_ruby/1.8/aeditor/main.rb:26 =A0 from /usr/bin/aeditor:2:in `require' =A0 from /usr/bin/aeditor:2 |
|
From: Andre' W. <an...@sy...> - 2004-07-07 20:59:08
|
Thank you so much for everyone's help, I couldn't do without you!
Someday someone has to write a tutorial on that. (maybe I will, if
ever got some experience)
So here is my final code. Any hints on optimization would be
appreciated.
require 'fox'
include Fox
class Test
def initialize
app =3D FXApp.new
main_window =3D FXMainWindow.new(app, "test", nil, nil, D=
ECOR_ALL, 500, 330, 540, 370)
# Canvas & image
canvas =3D FXCanvas.new(main_window, nil, 0, LAYOUT_FIX_W=
IDTH|LAYOUT_FIX_HEIGHT, 0, 0, 30, 30)
@buffer =3D FXImage.new(app, nil, IMAGE_KEEP)
@buffer.create
canvas.connect(SEL_PAINT) { |sender, sel, evt|=20
FXDCWindow.new(sender, evt) { |dc|
dc.drawImage(@buffer, 0, 0)
}
}
canvas.connect(SEL_CONFIGURE) { |sender, sel, evt|
@buffer.create unless @buffer.created?
@buffer.resize(sender.width, sender.height)
draw
}
app.create
main_window.show
# sets the pixel
setPixel(10, 10, FXRGB(0,0,0))
=20
app.run
=20
end
def draw
FXDCWindow.new(@buffer) { |dc|
dc.setForeground(FXRGB(255, 255, 255))
dc.fillRectangle(0, 0, @buffer.width, @buffer.hei=
ght)
}
end
def setPixel(x, y, color)
FXDCWindow.new(@buffer) { |dc|
dc.foreground =3D color
dc.drawPoint(x, y)
}
end
end
t =3D Test.new
Regards to all,
Andr=E9
--=20
=A9 Andre' Wagner - 2004 - All rights reserved
|
|
From: Oliver S. <ol...@mo...> - 2004-07-07 17:59:50
|
Hi, I'll give this a shot...
I think what you want is the canvas/dc paradigm. An FXImageView is usually
for displaying static image files such as .bmp or .jpg. Since you want to
create an image from scratch, the right way to do it is to replace your
FXImageView with an FXCanvas and forget about the FXImage for now. It's
kind of complicated to explain briefly, but think of an FXDCWindow (which
contains an FXDC) as an artist. You give the artist a brush and some paint
and a canvas and tell him to draw lines and pixels. So something like this
untested code:
@canvas = FXCanvas.new(...)
@canvas.connect(SEL_PAINT) {
FXDCWindow.new(@canvas) { |dc|
dc.foreground = "white"
dc.fillRectangle(0, 0, @canvas.width, @canvas.height)
dc.foreground = "black"
dc.drawPoint(20, 20) # draw a pixel
}
}
But it gets more complicated. Note that you should paint on the canvas
during the SEL_PAINT handler. This ensures that FOX knows to display the
changes on the screen. You can tell FOX to send a new SEL_PAINT message by
calling @canvas.update when you need it.
Now, while that method works, the problem with drawing on an FXCanvas is
that the user can see you draw. So during slow operations the user will see
flicker as you update the painting. That's where the FXImage comes in. The
FXImage is an off-screen buffer that you can paint on just like an FXCanvas.
Look at the bounce.rbw example - it uses the FXCanvas to display the scene
to the user, but all actual drawing is done on the FXImage "behind the
scenes". When the FXImage has been changed, the program calls
@canvas.update. Then, when SEL_PAINT arrives, it uses dc.drawImage to throw
the entire FXImage onto the canvas at once. Thus, less chance of flicker.
This technique is called 'double buffering'.
Actually, bounce.rbw is a great place to start. You can see how it creates
the FXImage - first by calling the constructor, but then in SEL_CONFIGURE
(sent when the window is created or resized) the buffer is actually created
(i.e. memory for it is allocated) and given a size. Drawing to the buffer
before it's created may be the source of your crash, although I'm not sure.
So, to summarize, you can draw to an FXImage anytime after it's created and
sized, but when you're done call @canvas.update and wait for the SEL_PAINT
to flip the image onto the FXCanvas the user will see. Or, just draw to the
FXCanvas directly from SEL_PAINT if you don't care about flicker or only
need to draw once. Read the help for FXDC for a list of drawing methods and
operations. Drawing an entire screen of individual pixels is going to be
pretty slow, by the way... :| Hope some of this is helpful,
Oliver
> -----Original Message-----
> From: fxr...@li...
> [mailto:fxr...@li...]On Behalf Of Andre'
> Wagner
> Sent: Wednesday, July 07, 2004 10:10 AM
> To: fxr...@li...
> Subject: Re: [Fxruby-users] hard time using images
>
>
> Thank you so much for the very complete info! However, I still can't
> draw :-( So let us speak ruby. I wrote this small class:
>
> require 'fox'
> include Fox
>
> class Test
>
> def initialize
> app = FXApp.new
> main_window = FXMainWindow.new(app, "test", nil,
> nil, DECOR_ALL, 500, 330,
> 540, 370)
>
> # Image
> image = FXImage.new(app, nil, 0, 30, 30)
> imageview = FXImageView.new(main_window, image)
>
> # Set a pixel
> image.setPixel(10, 10, FXRGB(255, 255, 255))
>
> app.create
> main_window.show
> app.run
> end
>
> end
> t = Test.new
>
> When the code gets into the setPixel, I get a segfault. What am I
> missing?
>
> Thank you in advance,
>
> André
>
> --
> © Andre' Wagner - 2004 - All rights reserved
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> digital self defense, top technical experts, no vendor pitches,
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Fxruby-users mailing list
> Fxr...@li...
> https://lists.sourceforge.net/lists/listinfo/fxruby-users
|
|
From: Andre' W. <an...@sy...> - 2004-07-07 17:08:28
|
Thank you so much for the very complete info! However, I still can't
draw :-( So let us speak ruby. I wrote this small class:
require 'fox'
include Fox
class Test
def initialize
app =3D FXApp.new
main_window =3D FXMainWindow.new(app, "test", nil, nil, D=
ECOR_ALL, 500, 330,
540, 370)
# Image
image =3D FXImage.new(app, nil, 0, 30, 30)
imageview =3D FXImageView.new(main_window, image)
# Set a pixel
image.setPixel(10, 10, FXRGB(255, 255, 255))
=20
app.create
main_window.show
app.run
end
end
t =3D Test.new
When the code gets into the setPixel, I get a segfault. What am I
missing?
Thank you in advance,
Andr=E9
--=20
=A9 Andre' Wagner - 2004 - All rights reserved
|
|
From: Hugh S. S. E. E. <hg...@dm...> - 2004-07-07 16:06:56
|
On Wed, 7 Jul 2004, Vincent Cojot wrote:
>
> Hi Hugh,
>
> A couple things you might want to try:
>
> - Make sure your Solaris 9 patch level is up-to-date. /usr/ccs/bin/ld should
> not segfault. Install a Recommended Cluster and/or a Maintenance update.
We will follow this up in due course -- it is my colleague who looks
after that side of things, and I've told him about this,
Meanwhile....
>
> - You might want to try to 'export LD=/usr/ccs/bin/ld' before you run
> configure to make sure that 'ld' will link the shared library instead of
> using 'g++ -shared'. This solved problems for me under Solaris 8 but of
> course YMMV...
About the only thing I have not meddled with is LD_LIBRARY_PATH,
which has been sufficient to the task I think.
I got these results as the first combination which worked:
+ echo /usr/ccs/bin/ld /progs/SUNWspro/bin/cc g++ gmake
/usr/ccs/bin/ld /progs/SUNWspro/bin/cc g++ gmake
+ exit 0
versions:
ld: Software Generation Utilities - Solaris Link Editors: 5.9-1.375
cc: Sun WorkShop 6 update 2 C 5.3 2001/05/15
gcc (GCC) 3.3.2
GNU Make 3.80
This is as a result of this script to try everything exhaustively:
#!/bin/sh -vx
# vim:sw=2
for ld in /usr/ccs/bin/ld /usr/ucb/ld /usr/local/bin/ld
do
LD=$ld
export LD
for cc in gcc /progs/SUNWspro/bin/cc /usr/ucb/cc
do
CC=$cc
export CC
for cxx in g++ CC
do
CXX=$cxx
export CXX
for make in gmake make
do
MAKE=$make
export MAKE
$MAKE distclean
./configure && $MAKE && echo $LD $CC $CXX $MAKE && exit 0
done
done
done
done
That g++ should work together with cc seems odd to me. Are there
any tests I can run on this to really thrash it before accepting it
as functioning correctly? While I'm at it, are there any tests that
it would be useful to the Fox/FXRuby community to do on this system?
>
> Good luck,
>
> Vincent
Thank you,
Hugh
|
|
From: rich l. <fx...@gm...> - 2004-07-07 15:04:00
|
I'd use FXGLCanvas - but I really don't have experience with anything else. I've used FXGLViewer I think... and that wasn't that bad... If you're looking for a tutorial, I might be able to write one for you on FXGLCanvas... At: http://fox-toolkit.net/cgi-bin/wiki.pl?Documentation there is a link: [Developing GUIs with FOX and Ruby] That has a bit of a tutorial on FXGLCanvas I think... -Rich On Wed, 7 Jul 2004 11:45:35 -0300, Andre' Wagner <an...@sy...> wr= ote: > I'm writing a emulator, so basicly what I'm gonna do is draw single > pixels in a image. (as fast as possible) >=20 > Andr=E9 >=20 >=20 >=20 > In Wednesday, July 7, 2004 you wrote: >=20 > > Are you wanting to draw an image (graph, chart) or import and > > manipulate an image (bmp, jpg)? >=20 > > -Rich >=20 > > On Wed, 7 Jul 2004 11:08:50 -0300, Andre' Wagner <an...@sy...= > wrote: > >> Hello folks, > >> > >> I think I'm failing to understand how do I manipulate a image widget > >> in my application. I putted the FXImage in my app - and it appears ok > >> - but if I try to setPixel in it then I get a segfault. > >> > >> I peeked into the examples, and I see they use a FXDCWindow and a > >> FXCanvas, but I can't understand it very well. I looked into the > >> tutorial and the docs but I haven't found anything that cleared my > >> mind. > >> > >> Is there a image tutorial for FXRuby or something like that on the > >> net? Or might someone give me a few pointers here? > >> > >> Thank you in advance, > >> > >> Andr=E9 > >> > >> -- > >> =A9 Andre' Wagner - 2004 - All rights reserved > >> > >> ------------------------------------------------------- > >> This SF.Net email sponsored by Black Hat Briefings & Training. > >> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > >> digital self defense, top technical experts, no vendor pitches, > >> unmatched networking opportunities. Visit www.blackhat.com > >> _______________________________________________ > >> Fxruby-users mailing list > >> Fxr...@li... > >> https://lists.sourceforge.net/lists/listinfo/fxruby-users > >> >=20 > > ------------------------------------------------------- > > This SF.Net email sponsored by Black Hat Briefings & Training. > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > > digital self defense, top technical experts, no vendor pitches, > > unmatched networking opportunities. Visit www.blackhat.com > > _______________________________________________ > > Fxruby-users mailing list > > Fxr...@li... > > https://lists.sourceforge.net/lists/listinfo/fxruby-users >=20 > -- > =A9 Andre' Wagner - 2004 - All rights reserved >=20 > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Fxruby-users mailing list > Fxr...@li... > https://lists.sourceforge.net/lists/listinfo/fxruby-users > |
|
From: Andre' W. <an...@sy...> - 2004-07-07 14:43:32
|
I'm writing a emulator, so basicly what I'm gonna do is draw single pixels in a image. (as fast as possible) Andr=E9 In Wednesday, July 7, 2004 you wrote: > Are you wanting to draw an image (graph, chart) or import and > manipulate an image (bmp, jpg)? > -Rich > On Wed, 7 Jul 2004 11:08:50 -0300, Andre' Wagner <an...@sy...= > wrote: >> Hello folks, >>=20 >> I think I'm failing to understand how do I manipulate a image widget >> in my application. I putted the FXImage in my app - and it appears ok >> - but if I try to setPixel in it then I get a segfault. >>=20 >> I peeked into the examples, and I see they use a FXDCWindow and a >> FXCanvas, but I can't understand it very well. I looked into the >> tutorial and the docs but I haven't found anything that cleared my >> mind. >>=20 >> Is there a image tutorial for FXRuby or something like that on the >> net? Or might someone give me a few pointers here? >>=20 >> Thank you in advance, >>=20 >> Andr=E9 >>=20 >> -- >> =A9 Andre' Wagner - 2004 - All rights reserved >>=20 >> ------------------------------------------------------- >> This SF.Net email sponsored by Black Hat Briefings & Training. >> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >> digital self defense, top technical experts, no vendor pitches, >> unmatched networking opportunities. Visit www.blackhat.com >> _______________________________________________ >> Fxruby-users mailing list >> Fxr...@li... >> https://lists.sourceforge.net/lists/listinfo/fxruby-users >> > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 -=20 > digital self defense, top technical experts, no vendor pitches,=20 > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Fxruby-users mailing list > Fxr...@li... > https://lists.sourceforge.net/lists/listinfo/fxruby-users --=20 =A9 Andre' Wagner - 2004 - All rights reserved |
|
From: Jeroen v. d. Z. <je...@fo...> - 2004-07-07 14:37:22
|
On Wednesday 07 July 2004 10:08 am, Andre' Wagner wrote: > Hello folks, > > I think I'm failing to understand how do I manipulate a image widget > in my application. I putted the FXImage in my app - and it appears ok > - but if I try to setPixel in it then I get a segfault. > > I peeked into the examples, and I see they use a FXDCWindow and a > FXCanvas, but I can't understand it very well. I looked into the > tutorial and the docs but I haven't found anything that cleared my > mind. > > Is there a image tutorial for FXRuby or something like that on the > net? Or might someone give me a few pointers here? > > Thank you in advance, > > Andr=E9 The think to keep in mind is that there's two sides to FXImage: the array of pixels which is kept in your program and the device-specific bitmap which is kept in the display server. Now, to keep memory down, by default FXImage ditches the pixel array in the program, since USING the image in drawing operations normally requires only the bitmap in the display server. Of course, sometimes you need the local pixel array, and there's a way to hang on to that, by passing the IMAGE_KEEP option. Also, there is a way to regenerate the server-side bitmap from the local pixel array, which you can do by calling render(). Finally, since you can use drawing commands to draw things into the bitmap that is kept in the server, you can read back the bitmap into the local image pixel array by calling restore(). The API setPixel() works on the local image pixel array, and you must make sure that the pixel array is kept around for that to work properly. Note also that the local pixel array is only deleted after the server-side bitmap has been populated, which means basically that prior to create() you still have full access to the local pixel array. Hope this helps, - Jeroen |
|
From: rich l. <fx...@gm...> - 2004-07-07 14:36:28
|
Are you wanting to draw an image (graph, chart) or import and manipulate an image (bmp, jpg)? -Rich On Wed, 7 Jul 2004 11:08:50 -0300, Andre' Wagner <an...@sy...> wr= ote: > Hello folks, >=20 > I think I'm failing to understand how do I manipulate a image widget > in my application. I putted the FXImage in my app - and it appears ok > - but if I try to setPixel in it then I get a segfault. >=20 > I peeked into the examples, and I see they use a FXDCWindow and a > FXCanvas, but I can't understand it very well. I looked into the > tutorial and the docs but I haven't found anything that cleared my > mind. >=20 > Is there a image tutorial for FXRuby or something like that on the > net? Or might someone give me a few pointers here? >=20 > Thank you in advance, >=20 > Andr=E9 >=20 > -- > =A9 Andre' Wagner - 2004 - All rights reserved >=20 > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Fxruby-users mailing list > Fxr...@li... > https://lists.sourceforge.net/lists/listinfo/fxruby-users > |
|
From: Andre' W. <an...@sy...> - 2004-07-07 14:06:46
|
Hello folks, I think I'm failing to understand how do I manipulate a image widget in my application. I putted the FXImage in my app - and it appears ok - but if I try to setPixel in it then I get a segfault. I peeked into the examples, and I see they use a FXDCWindow and a FXCanvas, but I can't understand it very well. I looked into the tutorial and the docs but I haven't found anything that cleared my mind. Is there a image tutorial for FXRuby or something like that on the net? Or might someone give me a few pointers here? Thank you in advance, Andr=E9 --=20 =A9 Andre' Wagner - 2004 - All rights reserved |
|
From: Lyle J. <ly...@kn...> - 2004-07-07 09:48:13
|
On Jul 6, 2004, at 6:03 AM, Simon Strandgaard wrote: > if one initializes FXFontDialog with an illegal fontdesc, then no > font appears to choose among.. the dialog box is just empty. > If I put a check in the 'All Fonts:', then I see the full list of > fonts. > Wouldn't it be an idea to make FXFontDialog robust to illegal font > descriptions? This is probably something that would need to be addressed directly in the FOX toolkit, since FXRuby just wraps the FXFontDialog as-is. However, I've added this one to the FXRuby bug list for now and will see if there is something we can do in the Ruby layer. |
|
From: Vincent C. <co...@st...> - 2004-07-07 09:33:41
|
Hi Hugh, A couple things you might want to try: - Make sure your Solaris 9 patch level is up-to-date. /usr/ccs/bin/ld should not segfault. Install a Recommended Cluster and/or a Maintenance update. - You might want to try to 'export LD=/usr/ccs/bin/ld' before you run configure to make sure that 'ld' will link the shared library instead of using 'g++ -shared'. This solved problems for me under Solaris 8 but of course YMMV... Good luck, Vincent ,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-, Vincent S. Cojot, Computer Engineering. STEP project. _.,-*~'`^`'~*-,._.,-*~ Ecole Polytechnique de Montreal, Comite Micro-Informatique. _.,-*~'`^`'~*-,. Linux Xview/OpenLook resources page _.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~' http://step.polymtl.ca/~coyote _.,-*~'`^`'~*-,._ co...@st... They cannot scare me with their empty spaces Between stars - on stars where no human race is I have it in me so much nearer home To scare myself with my own desert places. - Robert Frost |
|
From: Hugh S. S. E. E. <hg...@dm...> - 2004-07-07 09:22:55
|
On Tue, 6 Jul 2004, jeroen wrote:
> On Tuesday 06 July 2004 10:26 am, Hugh Sasse Staff Elec Eng wrote:
>> The last thing I get on building the Fox library is
>>
>> g++ -shared FX4Splitter.lo FXAccelTable.lo FXApp.lo
>> FXArrowButton.lo FXBMPIcon.lo FXBMPImage.lo FXBitmap.lo
[....]
>> -ldl -lpthread -ljpeg -lpng -lz -lbz2 -lm -lGL -lGLU -lc
>> -Wl,-soname -Wl,libFOX-1.2.so.0 -o .libs/libFOX-1.2.so.0.0.6
>> collect2: ld terminated with signal 11 [Segmentation Fault], core
>> dumped
>> gmake[1]: *** [libFOX-1.2.la] Error 1
>> gmake[1]: Leaving directory `/export/home/Scratch/hgs/fox-1.2.6/src'
>> gmake: *** [all-recursive] Error 1
>>
>> The only thing that seems obvious to me is to ensure that the LD
>> used is gnu ld and not the Sun one. Given this is invoked by g++,
>> how might I be certain about this? It is not defined in the (top)
>> Makefile. Anything else I should look out for?
>
> I keep up with FOX compiling on SUN; it should compile out of the
> box using SUN's own compiler. If you have a problem with compiling
I'll give that a go, but Ruby compiles with GCC, so will the
libraries interoperate? There are dire warnings about this in the
changes docs for GCC, and I don't know enough to test for the
ramificiations in any particular case.
> using GCC, my first suggestion is to make sure GCC is properly
> installed [its a complex beast!]. Make sure you have a recent
I believe it is. It does fail some tests when built, but I can
compile most things with it [pine, exim, Ruby, Perl,...]. I know of
no post-install diag/test suite I could use but would be glad to
hear about one. Given that many `make check` tests fail but even
unexpected failures are to be expected I think the chances of such a
thing coming into being are slim.
> GCC, and that your paths are set properly [in particular, GCC's
3.3.2. I've avoided 3.4.0 because it is .0, but now 3.4.1 is out I
may try building that.
> installation typically includes "repaired" header files which may
> be necessary].
Can you explicitly tell me how to test for these things? I've not
even been able to extract which linker it is using from GCC or G++.
It occurs to me that I might get something out of strace, but I get
a lot of information out of that! :-)
>
> On some machines you need to use native linker, and some GNU ld; I
> don't know what the recommendation is for the SPARC target.
ld: /usr/ccs/bin/ld /usr/lib/ld.so /usr/lib/ld /usr/ucb/ld /usr/local/bin/ld
and sum says they are all different, the last being Gnu ld
41228 18 /usr/ccs/bin/ld
12100 4 /usr/ucb/ld
40682 3969 /usr/local/bin/ld
and Sun Workshop compiler doesn't seem to have an ld in the same
dir as the compiler.
>
> SUN has a collection of GNU software on their site, I don't know
Yes, I think we used that gcc to build this one.
> if this includes GCC but if it does then that might be helpful,
Is there any way to test this though? I could spend ages fiddling
with different GCC's, different versions of binutils, etc, and when
it works I still won't know why.
> assuming the SUN developers are more on top of this situation that
> we are.
>
>
> Regards,
>
>
> - Jeroen
>
Thank you,
Hugh
|
|
From: jeroen <je...@fo...> - 2004-07-07 03:47:41
|
On Tuesday 06 July 2004 10:26 am, Hugh Sasse Staff Elec Eng wrote: > The last thing I get on building the Fox library is > > g++ -shared FX4Splitter.lo FXAccelTable.lo FXApp.lo > FXArrowButton.lo FXBMPIcon.lo FXBMPImage.lo FXBitmap.lo > FXBitmapFrame.lo FXBitmapView.lo FXButton.lo FXBZStream.lo > FXCURCursor.lo FXCanvas.lo FXCharset.lo FXCheckButton.lo > FXColorBar.lo FXColorDialog.lo FXColorNames.lo FXColorSelector.lo > FXColorWell.lo FXColorWheel.lo FXComboBox.lo FXComposite.lo > FXCursor.lo FXDC.lo FXDCPrint.lo FXDCWindow.lo FXDLL.lo > FXDataTarget.lo FXDebugTarget.lo FXDelegator.lo FXDial.lo > FXDialogBox.lo FXDict.lo FXDirBox.lo FXDirDialog.lo FXDirList.lo > FXDirSelector.lo FXDocument.lo FXDragCorner.lo FXDrawable.lo > FXDriveBox.lo FXException.lo FXFile.lo FXFileDialog.lo FXFileDict.lo > FXFileList.lo FXFileSelector.lo FXFileStream.lo FXFoldingList.lo > FXFont.lo FXFontDialog.lo FXFontSelector.lo FXFrame.lo > FXGIFCursor.lo FXGIFIcon.lo FXGIFImage.lo FXGLCanvas.lo FXGLCone.lo > FXGLContext.lo FXGLCube.lo FXGLCylinder.lo FXGLObject.lo > FXGLShape.lo FXGLSphere.lo FXGLTriangleMesh.lo FXGLViewer.lo > FXGLVisual.lo FXGradientBar.lo FXGroupBox.lo FXGZStream.lo FXHash.lo > FXHeader.lo FXHorizontalFrame.lo FXICOIcon.lo FXICOImage.lo > FXIcon.lo FXIconList.lo FXId.lo FXImage.lo FXImageFrame.lo > FXImageView.lo FXInputDialog.lo FXJPGIcon.lo FXJPGImage.lo > FXLabel.lo FXList.lo FXListBox.lo FXMDIButton.lo FXMDIChild.lo > FXMDIClient.lo FXMainWindow.lo FXMat3d.lo FXMat4d.lo FXMat3f.lo > FXMat4f.lo FXMatrix.lo FXMemoryStream.lo FXMenuBar.lo > FXMenuButton.lo FXMenuCaption.lo FXMenuCascade.lo FXMenuCheck.lo > FXMenuRadio.lo FXMenuCommand.lo FXMenuPane.lo FXMenuSeparator.lo > FXMenuTitle.lo FXMessageBox.lo FXObject.lo FXObjectList.lo > FXOptionMenu.lo FXPCXIcon.lo FXPCXImage.lo FXPNGIcon.lo > FXPNGImage.lo FXPPMIcon.lo FXPPMImage.lo FXPacker.lo FXPicker.lo > FXPopup.lo FXPoint.lo FXPrintDialog.lo FXProgressBar.lo > FXProgressDialog.lo FXQuatd.lo FXQuatf.lo FXRGBIcon.lo FXRGBImage.lo > FXRadioButton.lo FXRangef.lo FXRanged.lo FXRealSlider.lo > FXRealSpinner.lo FXRecentFiles.lo FXRectangle.lo FXRegion.lo > FXRegistry.lo FXReplaceDialog.lo FXRex.lo FXRootWindow.lo FXRuler.lo > FXScrollArea.lo FXScrollBar.lo FXScrollPane.lo FXScrollWindow.lo > FXSearchDialog.lo FXSeparator.lo FXSettings.lo FXShell.lo > FXShutter.lo FXSize.lo FXSlider.lo FXSpinner.lo FXSpheref.lo > FXSphered.lo FXSplitter.lo FXSpring.lo FXStatusBar.lo > FXStatusLine.lo FXStream.lo FXString.lo FXStringDict.lo > FXSwitcher.lo FXTGAIcon.lo FXTGAImage.lo FXTIFIcon.lo FXTIFImage.lo > FXTabBar.lo FXTabBook.lo FXTabItem.lo FXTable.lo FXText.lo > FXTextCodec.lo FXTextField.lo FXThread.lo FXToggleButton.lo > FXToolBar.lo FXToolBarGrip.lo FXToolBarShell.lo FXToolBarTab.lo > FXToolTip.lo FXTopWindow.lo FXTreeList.lo FXTreeListBox.lo > FXTriStateButton.lo FXUndoList.lo FXURL.lo FXUTF8Codec.lo > FXUTF16Codec.lo FXUTF32Codec.lo FXVec2d.lo FXVec2f.lo FXVec3d.lo > FXVec3f.lo FXVec4d.lo FXVec4f.lo FXVerticalFrame.lo FXVisual.lo > FXWindow.lo FXWizard.lo FXWString.lo FXXBMIcon.lo FXXBMImage.lo > FXXPMIcon.lo FXXPMImage.lo fxbmpio.lo fxfilematch.lo fxgifio.lo > fxicoio.lo fxjpegio.lo fxparsegeometry.lo fxpcxio.lo fxpngio.lo > fxppmio.lo fxpriv.lo fxpsio.lo fxfsquantize.lo fxezquantize.lo > fxwuquantize.lo fxrgbio.lo fxtargaio.lo fxtifio.lo fxutils.lo > fxwinkbd.lo fxxbmio.lo fxxpmio.lo icons.lo vsscanf.lo -Wl,--rpath > -Wl,/usr/openwin/lib -L/usr/openwin/lib -lXext -lX11 -lsocket -lnsl > -ldl -lpthread -ljpeg -lpng -lz -lbz2 -lm -lGL -lGLU -lc > -Wl,-soname -Wl,libFOX-1.2.so.0 -o .libs/libFOX-1.2.so.0.0.6 > collect2: ld terminated with signal 11 [Segmentation Fault], core > dumped > gmake[1]: *** [libFOX-1.2.la] Error 1 > gmake[1]: Leaving directory `/export/home/Scratch/hgs/fox-1.2.6/src' > gmake: *** [all-recursive] Error 1 > > The only thing that seems obvious to me is to ensure that the LD > used is gnu ld and not the Sun one. Given this is invoked by g++, > how might I be certain about this? It is not defined in the (top) > Makefile. Anything else I should look out for? I keep up with FOX compiling on SUN; it should compile out of the box using SUN's own compiler. If you have a problem with compiling using GCC, my first suggestion is to make sure GCC is properly installed [its a complex beast!]. Make sure you have a recent GCC, and that your paths are set properly [in particular, GCC's installation typically includes "repaired" header files which may be necessary]. On some machines you need to use native linker, and some GNU ld; I don't know what the recommendation is for the SPARC target. SUN has a collection of GNU software on their site, I don't know if this includes GCC but if it does then that might be helpful, assuming the SUN developers are more on top of this situation that we are. Regards, - Jeroen -- +----------------------------------------------------------------------------+ | Copyright (C) 23:40 07/ 6/2004 Jeroen van der Zijp. All Rights Reserved. | +----------------------------------------------------------------------------+ |
|
From: RLMuller <RLM...@Co...> - 2004-07-06 20:26:46
|
> Oh, you needn't duck out. It's more to do with Fox or > fxruby than Ruby as such. I've written a few thousand > lines with fxruby, but I still find Fox very difficult. Here's why I need to drop out: while you've *written* a few thousand lines of FXRuby, I've only *copied* a few thousand lines of Ruby from; -- samples in the Ruby installation -- books: yours, Matz', Thomas et al's, Feldt et al's. -- answers posted to questions on Ruby-Users & FXRuby-Users. I've got most of them running, sometimes with modified to explicate their functionality or to provide minor enhancements. But there are still a slew of Ruby and FXRuby features I want to investigate. So I'm still to uninformed to weigh in on serious enhancements such as yours. Best wishes, Richard ----- Original Message ----- From: "Hal Fulton" <ha...@hy...> To: <fxr...@li...> Sent: Tuesday, July 06, 2004 12:45 PM Subject: Re: [Fxruby-users] tree list navigation > RLMuller wrote: > > Woops. This is getting over my head: I'm too new at Ruby to address the > > issues you raised below. I'm ducking out of this thread, though I > > reiterate that I look forward to seeing your results. > > Oh, you needn't duck out. It's more to do with Fox or fxruby than > Ruby as such. I've written a few thousand lines with fxruby, but > I still find Fox very difficult. > > So duck back in any time. And if I do get it to work, I will share > it with you and the rest of the list. > > Hal > > > > Regards, > > Richard > > > > ----- Original Message ----- > > From: "Hal Fulton" <ha...@hy...> > > To: <fxr...@li...> > > Sent: Tuesday, July 06, 2004 10:49 AM > > Subject: Re: [Fxruby-users] tree list navigation > > > > > > > >>RLMuller wrote: > >> > >>>>But I'm more concerned with "How do I do it?" > >>>>than what key to map. > >>> > >>> > >>>I think you asked "What to do?", i.e. ignore undisplayed data (an > > > > interface > > > >>>issue), rather than "How do I do it?", i.e. a programming issue. I just > >>>felt that choice of a key was at the interface level also. > >>> > >>>In any case, I'd look forward to seeing your working model. > >> > >> > >>I see what you mean. But I was trying to talk about a programming issue. > >>Note I said: > >> > >> > This seems an order of magnitude easier to me than drag/drop. > >> > Am I wrong? Easier to code, not to use, I mean. > >> > >>And also: > >> > >> > It would be nice if there were some concept of "next" and > >> > "previous" that was independent of the actual tree structure, > >> > but dependent on the current collapsed/expanded state of the > >> > tree. > >> > >>Which is obviously an implementation issue, not interface. > >> > >>The interface explanation was in anticipation of the (unspoken but > >>natural) question: "Why would you want to do that?" > >> > >>You're right, of course -- on the keyboard, something like alt-down > >>is far better than something like F8. > >> > >>Let me restate this more clearly: > >> > >>1. I'd love to be able to manually drag/drop items in a tree list. > >>2. However, knowing a little about tree lists and a little about > >>drag/drop, I would estimate that adding this functionality would be > >>dozens of lines of code if not hundreds, and would be dozens of hours > >>of painful debugging. > >>3. Therefore I'm considering simple "move up one" and "move down one" > >>keyboard shortcuts. > >>4. I believe this would be simpler to code. > >>5. Now to get to the meat of the matter: > >>6. To code this simply would involve a concept of "next" and > >>"previous" that ignored the collapsed/expanded status of each node. > >>7. Therefore I've been looking in the API to see whether methods > >>exist for this kind of traversal. AFAICT they don't. > >>8. Therefore I'll apparently have to code some methods myself. > >>9. So can anyone offer me any advice or assistance? > >> > >>Thanks, > >>Hal > >> > >> > >> > >>>Regards, > >>>Richard > >>> > >>>----- Original Message ----- > >>>From: "Hal Fulton" <ha...@hy...> > >>>To: <fxr...@li...> > >>>Sent: Tuesday, July 06, 2004 9:29 AM > >>>Subject: Re: [Fxruby-users] tree list navigation > >>> > >>> > >>> > >>> > >>>>RLMuller wrote: > >>>> > >>>> > >>>>>Hi Hal, > >>>>> > >>>>>It sounds intuitive to me, i.e. navigating on what's visible and > >>> > >>>ignoring > >>> > >>> > >>>>>what's not. For what it's worth, I'd be inclined to map > > > > alt-down-arrow > > > >>>to > >>> > >>> > >>>>>that functionality, rather than F8. > >>>> > >>>>That makes sense. But I'm more concerned with "How do I do it?" than > >>>>what key to map. > >>>> > >>>>It would seem that some wrestling and testing should make it work. > >>>>There's apparently no built-in way to treat a tree list in this way. > >>>> > >>>>Hal > >>>> > >>>> > >>>> > >>>> > >>>>>Regards, > >>>>>Richard > >>>>> > >>>>>----- Original Message ----- > >>>>>From: "Hal Fulton" <ha...@hy...> > >>>>>To: <fxr...@li...> > >>>>>Sent: Tuesday, July 06, 2004 7:43 AM > >>>>>Subject: [Fxruby-users] tree list navigation > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>I'm thinking of using a couple of function keys to move items > >>>>>>up/down in a tree list. > >>>>>> > >>>>>>This seems an order of magnitude easier to me than drag/drop. > >>>>>>Am I wrong? Easier to code, not to use, I mean. > >>>>>> > >>>>>>So anyway: > >>>>>> > >>>>>>It would be nice if there were some concept of "next" and > >>>>>>"previous" that was independent of the actual tree structure, > >>>>>>but dependent on the current collapsed/expanded state of the > >>>>>>tree. > >>>>>> > >>>>>>For example: Suppose I have a new entry NEW, and I have F8 > >>>>>>mapped to a "move down" command. > >>>>>> > >>>>>>Here I'm representing collapsed and expanded nodes by + and - > >>>>>>respectively. Use a monospaced font to look at this. :) > >>>>>> > >>>>>>Given this tree: > >>>>>> > >>>>>> - NEW > >>>>>> + Stooges > >>>>>> + Dwarves > >>>>>> + Fates > >>>>>> + Muses > >>>>>> > >>>>>>Suppose I select NEW and press F8 three times -- I'd expect > >>>>>>this as a result: > >>>>>> > >>>>>> + Stooges > >>>>>> + Dwarves > >>>>>> + Fates > >>>>>> - NEW > >>>>>> + Muses > >>>>>> > >>>>>>On the other hand, suppose I start with this tree: > >>>>>> > >>>>>> - NEW > >>>>>> - Stooges > >>>>>> - Larry > >>>>>> - Curly > >>>>>> - Moe > >>>>>> + Dwarves > >>>>>> + Fates > >>>>>> + Muses > >>>>>> > >>>>>>and again select NEW and press F8 three times. I'd then expect: > >>>>>> > >>>>>> - Stooges > >>>>>> - Larry > >>>>>> - Curly > >>>>>> - NEW > >>>>>> - Moe > >>>>>> + Dwarves > >>>>>> + Fates > >>>>>> + Muses > >>>>>> > >>>>>>In other words, traverse the tree "as is" -- is this doable?? > >>>>>> > >>>>>>Obviously I'd like to be able to move not just single items but > >>>>>>entire subtrees. > >>>>>> > >>>>>>Thanks for any insight... > >>>>>> > >>>>>> > >>>>>>Hal > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>------------------------------------------------------- > >>>>>>This SF.Net email sponsored by Black Hat Briefings & Training. > >>>>>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > >>>>>>digital self defense, top technical experts, no vendor pitches, > >>>>>>unmatched networking opportunities. Visit www.blackhat.com > >>>>>>_______________________________________________ > >>>>>>Fxruby-users mailing list > >>>>>>Fxr...@li... > >>>>>>https://lists.sourceforge.net/lists/listinfo/fxruby-users > >>>>> > >>>>> > >>>>> > >>>>>--- > >>>>>Outgoing mail is certified Virus Free. > >>>>>Checked by AVG anti-virus system (http://www.grisoft.com). > >>>>>Version: 6.0.713 / Virus Database: 469 - Release Date: 7/4/2004 > >>>>> > >>>>> > >>>>> > >>>>>------------------------------------------------------- > >>>>>This SF.Net email sponsored by Black Hat Briefings & Training. > >>>>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > >>>>>digital self defense, top technical experts, no vendor pitches, > >>>>>unmatched networking opportunities. Visit www.blackhat.com > >>>>>_______________________________________________ > >>>>>Fxruby-users mailing list > >>>>>Fxr...@li... > >>>>>https://lists.sourceforge.net/lists/listinfo/fxruby-users > >>>>> > >>>> > >>>> > >>>> > >>>> > >>>>------------------------------------------------------- > >>>>This SF.Net email sponsored by Black Hat Briefings & Training. > >>>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > >>>>digital self defense, top technical experts, no vendor pitches, > >>>>unmatched networking opportunities. Visit www.blackhat.com > >>>>_______________________________________________ > >>>>Fxruby-users mailing list > >>>>Fxr...@li... > >>>>https://lists.sourceforge.net/lists/listinfo/fxruby-users > >>> > >>> > >>> > >>>--- > >>>Outgoing mail is certified Virus Free. > >>>Checked by AVG anti-virus system (http://www.grisoft.com). > >>>Version: 6.0.713 / Virus Database: 469 - Release Date: 7/4/2004 > >>> > >>> > >>> > >>>------------------------------------------------------- > >>>This SF.Net email sponsored by Black Hat Briefings & Training. > >>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > >>>digital self defense, top technical experts, no vendor pitches, > >>>unmatched networking opportunities. Visit www.blackhat.com > >>>_______________________________________________ > >>>Fxruby-users mailing list > >>>Fxr...@li... > >>>https://lists.sourceforge.net/lists/listinfo/fxruby-users > >>> > >> > >> > >> > >> > >>------------------------------------------------------- > >>This SF.Net email sponsored by Black Hat Briefings & Training. > >>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > >>digital self defense, top technical experts, no vendor pitches, > >>unmatched networking opportunities. Visit www.blackhat.com > >>_______________________________________________ > >>Fxruby-users mailing list > >>Fxr...@li... > >>https://lists.sourceforge.net/lists/listinfo/fxruby-users > > > > > > > > --- > > Outgoing mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.713 / Virus Database: 469 - Release Date: 7/4/2004 > > > > > > > > ------------------------------------------------------- > > This SF.Net email sponsored by Black Hat Briefings & Training. > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > > digital self defense, top technical experts, no vendor pitches, > > unmatched networking opportunities. Visit www.blackhat.com > > _______________________________________________ > > Fxruby-users mailing list > > Fxr...@li... > > https://lists.sourceforge.net/lists/listinfo/fxruby-users > > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Fxruby-users mailing list > Fxr...@li... > https://lists.sourceforge.net/lists/listinfo/fxruby-users --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.713 / Virus Database: 469 - Release Date: 7/4/2004 |
|
From: <ly...@kn...> - 2004-07-06 19:32:27
|
On 06 Jul 2004 12:22:56 -0700, Peter Watkins <wat...@lu...> wrote : > Well I got fxruby working per the http://www.fxruby.org/doc/build.html > page. Either there were some missing parts when I first read it, or I'm > going really blind. I hadn't run ldconfig -- that was my problem. Good! > Then I tried running the scintilla-test.rb example that comes with > fxruby, but it failed as follows: > > root@ulaneo-dynip141 examples]# ruby scintilla-test.rb > scintilla-test.rb:23:in `initialize': uninitialized constant > ScintillaTest::FXMenubar (NameError) > from scintilla-test.rb:75:in `new' > from scintilla-test.rb:75 > > Is this a pretty good indication that I botched something installing > fxscintilla or fxruby? No, this is a pretty good indication that I failed to try that example program before the 1.2a1 release. ;) I will of course add this to my list for the 1.2a2 release, but for now try editing that example program to change the spelling of "FXMenubar" to "FXMenuBar" and see if that allows it to run. Note that there may be some other bits of code in that example that also need to be ported to the new API, and so it will require some trial and error. If it gets to be too much of a hassle, rest assured that I'll get that example updated before the 1.2a2 release. Thanks very much for the report! Lyle |
|
From: <ly...@kn...> - 2004-07-06 19:26:47
|
On Tue, 06 Jul 2004 11:22:26 +0100, "Bil" <bi...@vi...> wrote : > I should say that I've had no problems installing the FXRuby 1.2 gem on Ruby1.8.1 / Win2k. I've even had success in writing/converting some code with it (started a simple svg editor and a menubar-from-yaml libray). For an alpha release, this is quite an achievement. Thanks Lyle! Thanks for the feedback. I haven't gotten a lot of feedback yet on that first alpha release and wasn't sure what that indicated. ;) > The only problem I've encountered is that I can't load JPEG/PNG any more - They just appear as 32x32 icons with JPEG or PNG written on them. I can load GIF/ICO with the same code, though. Sounds like I goofed when I built the FOX library itself. Will make sure this problem is corrected before the 1.2a2 release. > I would like to know roughly when the FXRegion#new(FXPoint_array, winding) function will be available... I will make sure that this one's available for the 1.2a2 release. Actually, as of last night, all of the remaining classes are wrapped and documented. I do however want to add some new example programs and test cases to exercise those new classes before cutting a 1.2a2 release, so that will probably get pushed 'til this weekend. |
|
From: Peter W. <wat...@lu...> - 2004-07-06 19:23:17
|
Well I got fxruby working per the http://www.fxruby.org/doc/build.html page. Either there were some missing parts when I first read it, or I'm going really blind. I hadn't run ldconfig -- that was my problem. Now I have another problem. :-/ I realized that I hadn't installed the fxruby gem with fxscintilla enabled, so I uninstalled fxruby via "gem --uninstall ruby" and then reinstalled it per the following command (my input and the program output are separated by a line): [root@ulaneo-dynip141 fox]# ruby fxruby-1.2.0.gem --force -- --with-fxscintilla-include=/usr/local/include/fxscintilla --with-fxscintilla-lib=/usr/local/lib ----------------------------------------------------- ruby extconf.rb --with-fxscintilla-include=/usr/local/include/fxscintilla --with-fxscintilla-lib=/usr/local/lib checking for sys/time.h... yes checking for signal.h... yes checking for png_create_read_struct() in -lpng... yes checking for deflate() in -lz... yes checking for jpeg_mem_init() in -ljpeg... yes checking for TIFFSetErrorHandler() in -ltiff... yes checking for XShmQueryVersion() in -lXext... yes checking for XFindContext() in -lX11... yes checking for glXCreateContext() in -lGL... yes checking for gluNewQuadric() in -lGLU... yes creating Makefile make gcc -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c librb.c g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c core_wrap.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c dc_wrap.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c dialogs_wrap.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c frames_wrap.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c FXRbApp.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c FXRbDataTarget.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c FXRbGLViewer.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c FXRuby.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c iconlist_wrap.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c icons_wrap.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c image_wrap.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c impl.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c label_wrap.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c layout_wrap.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c list_wrap.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c markfuncs.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c mdi_wrap.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c menu_wrap.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c opengl_wrap.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c scintilla_wrap.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c table_wrap.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c text_wrap.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c treelist_wrap.cpp g++ -fPIC -g -O2 -O0 -Iinclude -DWITH_FXSCINTILLA -I. -I/usr/local/lib/ruby/1.8/i686-linux -I/usr/local/lib/ruby/1.8/i686-linux -I. -DHAVE_SYS_TIME_H -DHAVE_SIGNAL_H -I/usr/local/include/fxscintilla -I/usr/local/include/fox-1.2 -c ui_wrap.cpp gcc -shared -L"/usr/local/lib" -L"/usr/local/lib" -L"/usr/X11R6/lib" -o fox.so librb.o core_wrap.o dc_wrap.o dialogs_wrap.o frames_wrap.o FXRbApp.o FXRbDataTarget.o FXRbGLViewer.o FXRuby.o iconlist_wrap.o icons_wrap.o image_wrap.o impl.o label_wrap.o layout_wrap.o list_wrap.o markfuncs.o mdi_wrap.o menu_wrap.o opengl_wrap.o scintilla_wrap.o table_wrap.o text_wrap.o treelist_wrap.o ui_wrap.o -lfxscintilla -lFOX-1.2 -lGLU -lGL -lX11 -lXext -ltiff -ljpeg -lz -lpng -lstdc++ -ldl -lcrypt -lm -lc make install make: Nothing to be done for `install'. Successfully installed fxruby version 1.2.0 ----------------------------------------------------------------- Then I tried running the scintilla-test.rb example that comes with fxruby, but it failed as follows: root@ulaneo-dynip141 examples]# ruby scintilla-test.rb scintilla-test.rb:23:in `initialize': uninitialized constant ScintillaTest::FXMenubar (NameError) from scintilla-test.rb:75:in `new' from scintilla-test.rb:75 Is this a pretty good indication that I botched something installing fxscintilla or fxruby? Peter |
|
From: Bil <bi...@vi...> - 2004-07-06 18:53:56
|
Lyle, I should say that I've had no problems installing the FXRuby 1.2 gem on= Ruby1.8.1 / Win2k. I've even had success in writing/converting some code= with it (started a simple svg editor and a menubar-from-yaml libray). For= an alpha release, this is quite an achievement. Thanks Lyle! The only problem I've encountered is that I can't load JPEG/PNG any more -= They just appear as 32x32 icons with JPEG or PNG written on them. I can= load GIF/ICO with the same code, though. I would like to know roughly when the FXRegion#new(FXPoint_array, winding)= function will be available. It is in FXRegion.rb, but I assume it is not= mapped into C yet. I will need it to get any further on my svg editor. I= am in no way demanding that it is done - it is just so I can plan what I= am doing. If it is going to be a long time, I will make the effort to wrap= Windows PolyRegions, which was what I was going to do before 1.2 arrived= with good timing (if I can work out how to compile extensions on= Windows...ack!). Thanks, bil |
|
From: Hal F. <ha...@hy...> - 2004-07-06 16:45:40
|
RLMuller wrote: > Woops. This is getting over my head: I'm too new at Ruby to address the > issues you raised below. I'm ducking out of this thread, though I > reiterate that I look forward to seeing your results. Oh, you needn't duck out. It's more to do with Fox or fxruby than Ruby as such. I've written a few thousand lines with fxruby, but I still find Fox very difficult. So duck back in any time. And if I do get it to work, I will share it with you and the rest of the list. Hal > Regards, > Richard > > ----- Original Message ----- > From: "Hal Fulton" <ha...@hy...> > To: <fxr...@li...> > Sent: Tuesday, July 06, 2004 10:49 AM > Subject: Re: [Fxruby-users] tree list navigation > > > >>RLMuller wrote: >> >>>>But I'm more concerned with "How do I do it?" >>>>than what key to map. >>> >>> >>>I think you asked "What to do?", i.e. ignore undisplayed data (an > > interface > >>>issue), rather than "How do I do it?", i.e. a programming issue. I just >>>felt that choice of a key was at the interface level also. >>> >>>In any case, I'd look forward to seeing your working model. >> >> >>I see what you mean. But I was trying to talk about a programming issue. >>Note I said: >> >> > This seems an order of magnitude easier to me than drag/drop. >> > Am I wrong? Easier to code, not to use, I mean. >> >>And also: >> >> > It would be nice if there were some concept of "next" and >> > "previous" that was independent of the actual tree structure, >> > but dependent on the current collapsed/expanded state of the >> > tree. >> >>Which is obviously an implementation issue, not interface. >> >>The interface explanation was in anticipation of the (unspoken but >>natural) question: "Why would you want to do that?" >> >>You're right, of course -- on the keyboard, something like alt-down >>is far better than something like F8. >> >>Let me restate this more clearly: >> >>1. I'd love to be able to manually drag/drop items in a tree list. >>2. However, knowing a little about tree lists and a little about >>drag/drop, I would estimate that adding this functionality would be >>dozens of lines of code if not hundreds, and would be dozens of hours >>of painful debugging. >>3. Therefore I'm considering simple "move up one" and "move down one" >>keyboard shortcuts. >>4. I believe this would be simpler to code. >>5. Now to get to the meat of the matter: >>6. To code this simply would involve a concept of "next" and >>"previous" that ignored the collapsed/expanded status of each node. >>7. Therefore I've been looking in the API to see whether methods >>exist for this kind of traversal. AFAICT they don't. >>8. Therefore I'll apparently have to code some methods myself. >>9. So can anyone offer me any advice or assistance? >> >>Thanks, >>Hal >> >> >> >>>Regards, >>>Richard >>> >>>----- Original Message ----- >>>From: "Hal Fulton" <ha...@hy...> >>>To: <fxr...@li...> >>>Sent: Tuesday, July 06, 2004 9:29 AM >>>Subject: Re: [Fxruby-users] tree list navigation >>> >>> >>> >>> >>>>RLMuller wrote: >>>> >>>> >>>>>Hi Hal, >>>>> >>>>>It sounds intuitive to me, i.e. navigating on what's visible and >>> >>>ignoring >>> >>> >>>>>what's not. For what it's worth, I'd be inclined to map > > alt-down-arrow > >>>to >>> >>> >>>>>that functionality, rather than F8. >>>> >>>>That makes sense. But I'm more concerned with "How do I do it?" than >>>>what key to map. >>>> >>>>It would seem that some wrestling and testing should make it work. >>>>There's apparently no built-in way to treat a tree list in this way. >>>> >>>>Hal >>>> >>>> >>>> >>>> >>>>>Regards, >>>>>Richard >>>>> >>>>>----- Original Message ----- >>>>>From: "Hal Fulton" <ha...@hy...> >>>>>To: <fxr...@li...> >>>>>Sent: Tuesday, July 06, 2004 7:43 AM >>>>>Subject: [Fxruby-users] tree list navigation >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>>I'm thinking of using a couple of function keys to move items >>>>>>up/down in a tree list. >>>>>> >>>>>>This seems an order of magnitude easier to me than drag/drop. >>>>>>Am I wrong? Easier to code, not to use, I mean. >>>>>> >>>>>>So anyway: >>>>>> >>>>>>It would be nice if there were some concept of "next" and >>>>>>"previous" that was independent of the actual tree structure, >>>>>>but dependent on the current collapsed/expanded state of the >>>>>>tree. >>>>>> >>>>>>For example: Suppose I have a new entry NEW, and I have F8 >>>>>>mapped to a "move down" command. >>>>>> >>>>>>Here I'm representing collapsed and expanded nodes by + and - >>>>>>respectively. Use a monospaced font to look at this. :) >>>>>> >>>>>>Given this tree: >>>>>> >>>>>> - NEW >>>>>> + Stooges >>>>>> + Dwarves >>>>>> + Fates >>>>>> + Muses >>>>>> >>>>>>Suppose I select NEW and press F8 three times -- I'd expect >>>>>>this as a result: >>>>>> >>>>>> + Stooges >>>>>> + Dwarves >>>>>> + Fates >>>>>> - NEW >>>>>> + Muses >>>>>> >>>>>>On the other hand, suppose I start with this tree: >>>>>> >>>>>> - NEW >>>>>> - Stooges >>>>>> - Larry >>>>>> - Curly >>>>>> - Moe >>>>>> + Dwarves >>>>>> + Fates >>>>>> + Muses >>>>>> >>>>>>and again select NEW and press F8 three times. I'd then expect: >>>>>> >>>>>> - Stooges >>>>>> - Larry >>>>>> - Curly >>>>>> - NEW >>>>>> - Moe >>>>>> + Dwarves >>>>>> + Fates >>>>>> + Muses >>>>>> >>>>>>In other words, traverse the tree "as is" -- is this doable?? >>>>>> >>>>>>Obviously I'd like to be able to move not just single items but >>>>>>entire subtrees. >>>>>> >>>>>>Thanks for any insight... >>>>>> >>>>>> >>>>>>Hal >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>------------------------------------------------------- >>>>>>This SF.Net email sponsored by Black Hat Briefings & Training. >>>>>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >>>>>>digital self defense, top technical experts, no vendor pitches, >>>>>>unmatched networking opportunities. Visit www.blackhat.com >>>>>>_______________________________________________ >>>>>>Fxruby-users mailing list >>>>>>Fxr...@li... >>>>>>https://lists.sourceforge.net/lists/listinfo/fxruby-users >>>>> >>>>> >>>>> >>>>>--- >>>>>Outgoing mail is certified Virus Free. >>>>>Checked by AVG anti-virus system (http://www.grisoft.com). >>>>>Version: 6.0.713 / Virus Database: 469 - Release Date: 7/4/2004 >>>>> >>>>> >>>>> >>>>>------------------------------------------------------- >>>>>This SF.Net email sponsored by Black Hat Briefings & Training. >>>>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >>>>>digital self defense, top technical experts, no vendor pitches, >>>>>unmatched networking opportunities. Visit www.blackhat.com >>>>>_______________________________________________ >>>>>Fxruby-users mailing list >>>>>Fxr...@li... >>>>>https://lists.sourceforge.net/lists/listinfo/fxruby-users >>>>> >>>> >>>> >>>> >>>> >>>>------------------------------------------------------- >>>>This SF.Net email sponsored by Black Hat Briefings & Training. >>>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >>>>digital self defense, top technical experts, no vendor pitches, >>>>unmatched networking opportunities. Visit www.blackhat.com >>>>_______________________________________________ >>>>Fxruby-users mailing list >>>>Fxr...@li... >>>>https://lists.sourceforge.net/lists/listinfo/fxruby-users >>> >>> >>> >>>--- >>>Outgoing mail is certified Virus Free. >>>Checked by AVG anti-virus system (http://www.grisoft.com). >>>Version: 6.0.713 / Virus Database: 469 - Release Date: 7/4/2004 >>> >>> >>> >>>------------------------------------------------------- >>>This SF.Net email sponsored by Black Hat Briefings & Training. >>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >>>digital self defense, top technical experts, no vendor pitches, >>>unmatched networking opportunities. Visit www.blackhat.com >>>_______________________________________________ >>>Fxruby-users mailing list >>>Fxr...@li... >>>https://lists.sourceforge.net/lists/listinfo/fxruby-users >>> >> >> >> >> >>------------------------------------------------------- >>This SF.Net email sponsored by Black Hat Briefings & Training. >>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >>digital self defense, top technical experts, no vendor pitches, >>unmatched networking opportunities. Visit www.blackhat.com >>_______________________________________________ >>Fxruby-users mailing list >>Fxr...@li... >>https://lists.sourceforge.net/lists/listinfo/fxruby-users > > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.713 / Virus Database: 469 - Release Date: 7/4/2004 > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Fxruby-users mailing list > Fxr...@li... > https://lists.sourceforge.net/lists/listinfo/fxruby-users > |
|
From: RLMuller <RLM...@Co...> - 2004-07-06 16:12:25
|
Woops. This is getting over my head: I'm too new at Ruby to address the issues you raised below. I'm ducking out of this thread, though I reiterate that I look forward to seeing your results. Regards, Richard ----- Original Message ----- From: "Hal Fulton" <ha...@hy...> To: <fxr...@li...> Sent: Tuesday, July 06, 2004 10:49 AM Subject: Re: [Fxruby-users] tree list navigation > RLMuller wrote: > >>But I'm more concerned with "How do I do it?" > >>than what key to map. > > > > > > I think you asked "What to do?", i.e. ignore undisplayed data (an interface > > issue), rather than "How do I do it?", i.e. a programming issue. I just > > felt that choice of a key was at the interface level also. > > > > In any case, I'd look forward to seeing your working model. > > > I see what you mean. But I was trying to talk about a programming issue. > Note I said: > > > This seems an order of magnitude easier to me than drag/drop. > > Am I wrong? Easier to code, not to use, I mean. > > And also: > > > It would be nice if there were some concept of "next" and > > "previous" that was independent of the actual tree structure, > > but dependent on the current collapsed/expanded state of the > > tree. > > Which is obviously an implementation issue, not interface. > > The interface explanation was in anticipation of the (unspoken but > natural) question: "Why would you want to do that?" > > You're right, of course -- on the keyboard, something like alt-down > is far better than something like F8. > > Let me restate this more clearly: > > 1. I'd love to be able to manually drag/drop items in a tree list. > 2. However, knowing a little about tree lists and a little about > drag/drop, I would estimate that adding this functionality would be > dozens of lines of code if not hundreds, and would be dozens of hours > of painful debugging. > 3. Therefore I'm considering simple "move up one" and "move down one" > keyboard shortcuts. > 4. I believe this would be simpler to code. > 5. Now to get to the meat of the matter: > 6. To code this simply would involve a concept of "next" and > "previous" that ignored the collapsed/expanded status of each node. > 7. Therefore I've been looking in the API to see whether methods > exist for this kind of traversal. AFAICT they don't. > 8. Therefore I'll apparently have to code some methods myself. > 9. So can anyone offer me any advice or assistance? > > Thanks, > Hal > > > > Regards, > > Richard > > > > ----- Original Message ----- > > From: "Hal Fulton" <ha...@hy...> > > To: <fxr...@li...> > > Sent: Tuesday, July 06, 2004 9:29 AM > > Subject: Re: [Fxruby-users] tree list navigation > > > > > > > >>RLMuller wrote: > >> > >>>Hi Hal, > >>> > >>>It sounds intuitive to me, i.e. navigating on what's visible and > > > > ignoring > > > >>>what's not. For what it's worth, I'd be inclined to map alt-down-arrow > > > > to > > > >>>that functionality, rather than F8. > >> > >>That makes sense. But I'm more concerned with "How do I do it?" than > >>what key to map. > >> > >>It would seem that some wrestling and testing should make it work. > >>There's apparently no built-in way to treat a tree list in this way. > >> > >>Hal > >> > >> > >> > >>>Regards, > >>>Richard > >>> > >>>----- Original Message ----- > >>>From: "Hal Fulton" <ha...@hy...> > >>>To: <fxr...@li...> > >>>Sent: Tuesday, July 06, 2004 7:43 AM > >>>Subject: [Fxruby-users] tree list navigation > >>> > >>> > >>> > >>> > >>>>I'm thinking of using a couple of function keys to move items > >>>>up/down in a tree list. > >>>> > >>>>This seems an order of magnitude easier to me than drag/drop. > >>>>Am I wrong? Easier to code, not to use, I mean. > >>>> > >>>>So anyway: > >>>> > >>>>It would be nice if there were some concept of "next" and > >>>>"previous" that was independent of the actual tree structure, > >>>>but dependent on the current collapsed/expanded state of the > >>>>tree. > >>>> > >>>>For example: Suppose I have a new entry NEW, and I have F8 > >>>>mapped to a "move down" command. > >>>> > >>>>Here I'm representing collapsed and expanded nodes by + and - > >>>>respectively. Use a monospaced font to look at this. :) > >>>> > >>>>Given this tree: > >>>> > >>>> - NEW > >>>> + Stooges > >>>> + Dwarves > >>>> + Fates > >>>> + Muses > >>>> > >>>>Suppose I select NEW and press F8 three times -- I'd expect > >>>>this as a result: > >>>> > >>>> + Stooges > >>>> + Dwarves > >>>> + Fates > >>>> - NEW > >>>> + Muses > >>>> > >>>>On the other hand, suppose I start with this tree: > >>>> > >>>> - NEW > >>>> - Stooges > >>>> - Larry > >>>> - Curly > >>>> - Moe > >>>> + Dwarves > >>>> + Fates > >>>> + Muses > >>>> > >>>>and again select NEW and press F8 three times. I'd then expect: > >>>> > >>>> - Stooges > >>>> - Larry > >>>> - Curly > >>>> - NEW > >>>> - Moe > >>>> + Dwarves > >>>> + Fates > >>>> + Muses > >>>> > >>>>In other words, traverse the tree "as is" -- is this doable?? > >>>> > >>>>Obviously I'd like to be able to move not just single items but > >>>>entire subtrees. > >>>> > >>>>Thanks for any insight... > >>>> > >>>> > >>>>Hal > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>>------------------------------------------------------- > >>>>This SF.Net email sponsored by Black Hat Briefings & Training. > >>>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > >>>>digital self defense, top technical experts, no vendor pitches, > >>>>unmatched networking opportunities. Visit www.blackhat.com > >>>>_______________________________________________ > >>>>Fxruby-users mailing list > >>>>Fxr...@li... > >>>>https://lists.sourceforge.net/lists/listinfo/fxruby-users > >>> > >>> > >>> > >>>--- > >>>Outgoing mail is certified Virus Free. > >>>Checked by AVG anti-virus system (http://www.grisoft.com). > >>>Version: 6.0.713 / Virus Database: 469 - Release Date: 7/4/2004 > >>> > >>> > >>> > >>>------------------------------------------------------- > >>>This SF.Net email sponsored by Black Hat Briefings & Training. > >>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > >>>digital self defense, top technical experts, no vendor pitches, > >>>unmatched networking opportunities. Visit www.blackhat.com > >>>_______________________________________________ > >>>Fxruby-users mailing list > >>>Fxr...@li... > >>>https://lists.sourceforge.net/lists/listinfo/fxruby-users > >>> > >> > >> > >> > >> > >>------------------------------------------------------- > >>This SF.Net email sponsored by Black Hat Briefings & Training. > >>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > >>digital self defense, top technical experts, no vendor pitches, > >>unmatched networking opportunities. Visit www.blackhat.com > >>_______________________________________________ > >>Fxruby-users mailing list > >>Fxr...@li... > >>https://lists.sourceforge.net/lists/listinfo/fxruby-users > > > > > > > > --- > > Outgoing mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.713 / Virus Database: 469 - Release Date: 7/4/2004 > > > > > > > > ------------------------------------------------------- > > This SF.Net email sponsored by Black Hat Briefings & Training. > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > > digital self defense, top technical experts, no vendor pitches, > > unmatched networking opportunities. Visit www.blackhat.com > > _______________________________________________ > > Fxruby-users mailing list > > Fxr...@li... > > https://lists.sourceforge.net/lists/listinfo/fxruby-users > > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Fxruby-users mailing list > Fxr...@li... > https://lists.sourceforge.net/lists/listinfo/fxruby-users --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.713 / Virus Database: 469 - Release Date: 7/4/2004 |
|
From: Hugh S. S. E. E. <hg...@dm...> - 2004-07-06 15:26:40
|
The last thing I get on building the Fox library is
g++ -shared FX4Splitter.lo FXAccelTable.lo FXApp.lo
FXArrowButton.lo FXBMPIcon.lo FXBMPImage.lo FXBitmap.lo
FXBitmapFrame.lo FXBitmapView.lo FXButton.lo FXBZStream.lo
FXCURCursor.lo FXCanvas.lo FXCharset.lo FXCheckButton.lo
FXColorBar.lo FXColorDialog.lo FXColorNames.lo FXColorSelector.lo
FXColorWell.lo FXColorWheel.lo FXComboBox.lo FXComposite.lo
FXCursor.lo FXDC.lo FXDCPrint.lo FXDCWindow.lo FXDLL.lo
FXDataTarget.lo FXDebugTarget.lo FXDelegator.lo FXDial.lo
FXDialogBox.lo FXDict.lo FXDirBox.lo FXDirDialog.lo FXDirList.lo
FXDirSelector.lo FXDocument.lo FXDragCorner.lo FXDrawable.lo
FXDriveBox.lo FXException.lo FXFile.lo FXFileDialog.lo FXFileDict.lo
FXFileList.lo FXFileSelector.lo FXFileStream.lo FXFoldingList.lo
FXFont.lo FXFontDialog.lo FXFontSelector.lo FXFrame.lo
FXGIFCursor.lo FXGIFIcon.lo FXGIFImage.lo FXGLCanvas.lo FXGLCone.lo
FXGLContext.lo FXGLCube.lo FXGLCylinder.lo FXGLObject.lo
FXGLShape.lo FXGLSphere.lo FXGLTriangleMesh.lo FXGLViewer.lo
FXGLVisual.lo FXGradientBar.lo FXGroupBox.lo FXGZStream.lo FXHash.lo
FXHeader.lo FXHorizontalFrame.lo FXICOIcon.lo FXICOImage.lo
FXIcon.lo FXIconList.lo FXId.lo FXImage.lo FXImageFrame.lo
FXImageView.lo FXInputDialog.lo FXJPGIcon.lo FXJPGImage.lo
FXLabel.lo FXList.lo FXListBox.lo FXMDIButton.lo FXMDIChild.lo
FXMDIClient.lo FXMainWindow.lo FXMat3d.lo FXMat4d.lo FXMat3f.lo
FXMat4f.lo FXMatrix.lo FXMemoryStream.lo FXMenuBar.lo
FXMenuButton.lo FXMenuCaption.lo FXMenuCascade.lo FXMenuCheck.lo
FXMenuRadio.lo FXMenuCommand.lo FXMenuPane.lo FXMenuSeparator.lo
FXMenuTitle.lo FXMessageBox.lo FXObject.lo FXObjectList.lo
FXOptionMenu.lo FXPCXIcon.lo FXPCXImage.lo FXPNGIcon.lo
FXPNGImage.lo FXPPMIcon.lo FXPPMImage.lo FXPacker.lo FXPicker.lo
FXPopup.lo FXPoint.lo FXPrintDialog.lo FXProgressBar.lo
FXProgressDialog.lo FXQuatd.lo FXQuatf.lo FXRGBIcon.lo FXRGBImage.lo
FXRadioButton.lo FXRangef.lo FXRanged.lo FXRealSlider.lo
FXRealSpinner.lo FXRecentFiles.lo FXRectangle.lo FXRegion.lo
FXRegistry.lo FXReplaceDialog.lo FXRex.lo FXRootWindow.lo FXRuler.lo
FXScrollArea.lo FXScrollBar.lo FXScrollPane.lo FXScrollWindow.lo
FXSearchDialog.lo FXSeparator.lo FXSettings.lo FXShell.lo
FXShutter.lo FXSize.lo FXSlider.lo FXSpinner.lo FXSpheref.lo
FXSphered.lo FXSplitter.lo FXSpring.lo FXStatusBar.lo
FXStatusLine.lo FXStream.lo FXString.lo FXStringDict.lo
FXSwitcher.lo FXTGAIcon.lo FXTGAImage.lo FXTIFIcon.lo FXTIFImage.lo
FXTabBar.lo FXTabBook.lo FXTabItem.lo FXTable.lo FXText.lo
FXTextCodec.lo FXTextField.lo FXThread.lo FXToggleButton.lo
FXToolBar.lo FXToolBarGrip.lo FXToolBarShell.lo FXToolBarTab.lo
FXToolTip.lo FXTopWindow.lo FXTreeList.lo FXTreeListBox.lo
FXTriStateButton.lo FXUndoList.lo FXURL.lo FXUTF8Codec.lo
FXUTF16Codec.lo FXUTF32Codec.lo FXVec2d.lo FXVec2f.lo FXVec3d.lo
FXVec3f.lo FXVec4d.lo FXVec4f.lo FXVerticalFrame.lo FXVisual.lo
FXWindow.lo FXWizard.lo FXWString.lo FXXBMIcon.lo FXXBMImage.lo
FXXPMIcon.lo FXXPMImage.lo fxbmpio.lo fxfilematch.lo fxgifio.lo
fxicoio.lo fxjpegio.lo fxparsegeometry.lo fxpcxio.lo fxpngio.lo
fxppmio.lo fxpriv.lo fxpsio.lo fxfsquantize.lo fxezquantize.lo
fxwuquantize.lo fxrgbio.lo fxtargaio.lo fxtifio.lo fxutils.lo
fxwinkbd.lo fxxbmio.lo fxxpmio.lo icons.lo vsscanf.lo -Wl,--rpath
-Wl,/usr/openwin/lib -L/usr/openwin/lib -lXext -lX11 -lsocket -lnsl
-ldl -lpthread -ljpeg -lpng -lz -lbz2 -lm -lGL -lGLU -lc
-Wl,-soname -Wl,libFOX-1.2.so.0 -o .libs/libFOX-1.2.so.0.0.6
collect2: ld terminated with signal 11 [Segmentation Fault], core
dumped
gmake[1]: *** [libFOX-1.2.la] Error 1
gmake[1]: Leaving directory `/export/home/Scratch/hgs/fox-1.2.6/src'
gmake: *** [all-recursive] Error 1
The only thing that seems obvious to me is to ensure that the LD
used is gnu ld and not the Sun one. Given this is invoked by g++,
how might I be certain about this? It is not defined in the (top)
Makefile. Anything else I should look out for?
Thank you,
Hugh
|
|
From: Hal F. <ha...@hy...> - 2004-07-06 14:49:28
|
RLMuller wrote: >>But I'm more concerned with "How do I do it?" >>than what key to map. > > > I think you asked "What to do?", i.e. ignore undisplayed data (an interface > issue), rather than "How do I do it?", i.e. a programming issue. I just > felt that choice of a key was at the interface level also. > > In any case, I'd look forward to seeing your working model. I see what you mean. But I was trying to talk about a programming issue. Note I said: > This seems an order of magnitude easier to me than drag/drop. > Am I wrong? Easier to code, not to use, I mean. And also: > It would be nice if there were some concept of "next" and > "previous" that was independent of the actual tree structure, > but dependent on the current collapsed/expanded state of the > tree. Which is obviously an implementation issue, not interface. The interface explanation was in anticipation of the (unspoken but natural) question: "Why would you want to do that?" You're right, of course -- on the keyboard, something like alt-down is far better than something like F8. Let me restate this more clearly: 1. I'd love to be able to manually drag/drop items in a tree list. 2. However, knowing a little about tree lists and a little about drag/drop, I would estimate that adding this functionality would be dozens of lines of code if not hundreds, and would be dozens of hours of painful debugging. 3. Therefore I'm considering simple "move up one" and "move down one" keyboard shortcuts. 4. I believe this would be simpler to code. 5. Now to get to the meat of the matter: 6. To code this simply would involve a concept of "next" and "previous" that ignored the collapsed/expanded status of each node. 7. Therefore I've been looking in the API to see whether methods exist for this kind of traversal. AFAICT they don't. 8. Therefore I'll apparently have to code some methods myself. 9. So can anyone offer me any advice or assistance? Thanks, Hal > Regards, > Richard > > ----- Original Message ----- > From: "Hal Fulton" <ha...@hy...> > To: <fxr...@li...> > Sent: Tuesday, July 06, 2004 9:29 AM > Subject: Re: [Fxruby-users] tree list navigation > > > >>RLMuller wrote: >> >>>Hi Hal, >>> >>>It sounds intuitive to me, i.e. navigating on what's visible and > > ignoring > >>>what's not. For what it's worth, I'd be inclined to map alt-down-arrow > > to > >>>that functionality, rather than F8. >> >>That makes sense. But I'm more concerned with "How do I do it?" than >>what key to map. >> >>It would seem that some wrestling and testing should make it work. >>There's apparently no built-in way to treat a tree list in this way. >> >>Hal >> >> >> >>>Regards, >>>Richard >>> >>>----- Original Message ----- >>>From: "Hal Fulton" <ha...@hy...> >>>To: <fxr...@li...> >>>Sent: Tuesday, July 06, 2004 7:43 AM >>>Subject: [Fxruby-users] tree list navigation >>> >>> >>> >>> >>>>I'm thinking of using a couple of function keys to move items >>>>up/down in a tree list. >>>> >>>>This seems an order of magnitude easier to me than drag/drop. >>>>Am I wrong? Easier to code, not to use, I mean. >>>> >>>>So anyway: >>>> >>>>It would be nice if there were some concept of "next" and >>>>"previous" that was independent of the actual tree structure, >>>>but dependent on the current collapsed/expanded state of the >>>>tree. >>>> >>>>For example: Suppose I have a new entry NEW, and I have F8 >>>>mapped to a "move down" command. >>>> >>>>Here I'm representing collapsed and expanded nodes by + and - >>>>respectively. Use a monospaced font to look at this. :) >>>> >>>>Given this tree: >>>> >>>> - NEW >>>> + Stooges >>>> + Dwarves >>>> + Fates >>>> + Muses >>>> >>>>Suppose I select NEW and press F8 three times -- I'd expect >>>>this as a result: >>>> >>>> + Stooges >>>> + Dwarves >>>> + Fates >>>> - NEW >>>> + Muses >>>> >>>>On the other hand, suppose I start with this tree: >>>> >>>> - NEW >>>> - Stooges >>>> - Larry >>>> - Curly >>>> - Moe >>>> + Dwarves >>>> + Fates >>>> + Muses >>>> >>>>and again select NEW and press F8 three times. I'd then expect: >>>> >>>> - Stooges >>>> - Larry >>>> - Curly >>>> - NEW >>>> - Moe >>>> + Dwarves >>>> + Fates >>>> + Muses >>>> >>>>In other words, traverse the tree "as is" -- is this doable?? >>>> >>>>Obviously I'd like to be able to move not just single items but >>>>entire subtrees. >>>> >>>>Thanks for any insight... >>>> >>>> >>>>Hal >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>>------------------------------------------------------- >>>>This SF.Net email sponsored by Black Hat Briefings & Training. >>>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >>>>digital self defense, top technical experts, no vendor pitches, >>>>unmatched networking opportunities. Visit www.blackhat.com >>>>_______________________________________________ >>>>Fxruby-users mailing list >>>>Fxr...@li... >>>>https://lists.sourceforge.net/lists/listinfo/fxruby-users >>> >>> >>> >>>--- >>>Outgoing mail is certified Virus Free. >>>Checked by AVG anti-virus system (http://www.grisoft.com). >>>Version: 6.0.713 / Virus Database: 469 - Release Date: 7/4/2004 >>> >>> >>> >>>------------------------------------------------------- >>>This SF.Net email sponsored by Black Hat Briefings & Training. >>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >>>digital self defense, top technical experts, no vendor pitches, >>>unmatched networking opportunities. Visit www.blackhat.com >>>_______________________________________________ >>>Fxruby-users mailing list >>>Fxr...@li... >>>https://lists.sourceforge.net/lists/listinfo/fxruby-users >>> >> >> >> >> >>------------------------------------------------------- >>This SF.Net email sponsored by Black Hat Briefings & Training. >>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >>digital self defense, top technical experts, no vendor pitches, >>unmatched networking opportunities. Visit www.blackhat.com >>_______________________________________________ >>Fxruby-users mailing list >>Fxr...@li... >>https://lists.sourceforge.net/lists/listinfo/fxruby-users > > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.713 / Virus Database: 469 - Release Date: 7/4/2004 > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Fxruby-users mailing list > Fxr...@li... > https://lists.sourceforge.net/lists/listinfo/fxruby-users > |
|
From: RLMuller <RLM...@Co...> - 2004-07-06 14:17:44
|
> But I'm more concerned with "How do I do it?" > than what key to map. I think you asked "What to do?", i.e. ignore undisplayed data (an interface issue), rather than "How do I do it?", i.e. a programming issue. I just felt that choice of a key was at the interface level also. In any case, I'd look forward to seeing your working model. Regards, Richard ----- Original Message ----- From: "Hal Fulton" <ha...@hy...> To: <fxr...@li...> Sent: Tuesday, July 06, 2004 9:29 AM Subject: Re: [Fxruby-users] tree list navigation > RLMuller wrote: > > Hi Hal, > > > > It sounds intuitive to me, i.e. navigating on what's visible and ignoring > > what's not. For what it's worth, I'd be inclined to map alt-down-arrow to > > that functionality, rather than F8. > > That makes sense. But I'm more concerned with "How do I do it?" than > what key to map. > > It would seem that some wrestling and testing should make it work. > There's apparently no built-in way to treat a tree list in this way. > > Hal > > > > Regards, > > Richard > > > > ----- Original Message ----- > > From: "Hal Fulton" <ha...@hy...> > > To: <fxr...@li...> > > Sent: Tuesday, July 06, 2004 7:43 AM > > Subject: [Fxruby-users] tree list navigation > > > > > > > >>I'm thinking of using a couple of function keys to move items > >>up/down in a tree list. > >> > >>This seems an order of magnitude easier to me than drag/drop. > >>Am I wrong? Easier to code, not to use, I mean. > >> > >>So anyway: > >> > >>It would be nice if there were some concept of "next" and > >>"previous" that was independent of the actual tree structure, > >>but dependent on the current collapsed/expanded state of the > >>tree. > >> > >>For example: Suppose I have a new entry NEW, and I have F8 > >>mapped to a "move down" command. > >> > >>Here I'm representing collapsed and expanded nodes by + and - > >>respectively. Use a monospaced font to look at this. :) > >> > >>Given this tree: > >> > >> - NEW > >> + Stooges > >> + Dwarves > >> + Fates > >> + Muses > >> > >>Suppose I select NEW and press F8 three times -- I'd expect > >>this as a result: > >> > >> + Stooges > >> + Dwarves > >> + Fates > >> - NEW > >> + Muses > >> > >>On the other hand, suppose I start with this tree: > >> > >> - NEW > >> - Stooges > >> - Larry > >> - Curly > >> - Moe > >> + Dwarves > >> + Fates > >> + Muses > >> > >>and again select NEW and press F8 three times. I'd then expect: > >> > >> - Stooges > >> - Larry > >> - Curly > >> - NEW > >> - Moe > >> + Dwarves > >> + Fates > >> + Muses > >> > >>In other words, traverse the tree "as is" -- is this doable?? > >> > >>Obviously I'd like to be able to move not just single items but > >>entire subtrees. > >> > >>Thanks for any insight... > >> > >> > >>Hal > >> > >> > >> > >> > >> > >> > >> > >> > >>------------------------------------------------------- > >>This SF.Net email sponsored by Black Hat Briefings & Training. > >>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > >>digital self defense, top technical experts, no vendor pitches, > >>unmatched networking opportunities. Visit www.blackhat.com > >>_______________________________________________ > >>Fxruby-users mailing list > >>Fxr...@li... > >>https://lists.sourceforge.net/lists/listinfo/fxruby-users > > > > > > > > --- > > Outgoing mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.713 / Virus Database: 469 - Release Date: 7/4/2004 > > > > > > > > ------------------------------------------------------- > > This SF.Net email sponsored by Black Hat Briefings & Training. > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > > digital self defense, top technical experts, no vendor pitches, > > unmatched networking opportunities. Visit www.blackhat.com > > _______________________________________________ > > Fxruby-users mailing list > > Fxr...@li... > > https://lists.sourceforge.net/lists/listinfo/fxruby-users > > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Fxruby-users mailing list > Fxr...@li... > https://lists.sourceforge.net/lists/listinfo/fxruby-users --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.713 / Virus Database: 469 - Release Date: 7/4/2004 |
|
From: Hugh S. S. E. E. <hg...@dm...> - 2004-07-06 13:46:23
|
On Tue, 6 Jul 2004, Hugh Sasse Staff Elec Eng wrote: > Can someone confirm > MD5 (fox-1.2.6.tar.gz) = a178e70c8ec1422ead2216f6406d3679 > please? My usual strategy of searching the web for agreement has > failed. > > Thank you, > Hugh Pardon me replying to myself, but my results agree with this found with google groups: http://groups.google.co.uk/groups?q=a178e70c8ec1422ead2216f6406d3679&hl=en&lr=&ie=UTF-8&selm=cc6epu%242c4m%241%40FreeBSD.csie.NCTU.edu.tw&rnum=1 just in case someone searches the archives.... Hugh |
3 messages has been excluded from this view by a project administrator.
