fxruby-users Mailing List for FXRuby (Page 22)
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: Vlada <su...@ce...> - 2003-11-26 22:30:25
|
> >FXRuby 1.0.27
> >fox 1.0.46
> >
> >Compilation goes well in both.
>
> OK.
>
> >-----------
> >irb(main):001:0> require 'fox'
> >
> >LoadError: /usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so:
>
> <snip>
>
> What output do you get if you type:
>
> ldd /usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so
>
> at the shell prompt?
>
ok ... there is no problem with "didn't find library". It does find
all the libraries, but it seems not enough. There is some strange
problem with unknown symbols. But ok I'll satisfy you with ldd:
-------------
ldd /usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so
libFOX-1.0.so.0 => /usr/local/lib/libFOX-1.0.so.0 (0x40659000)
libGLU.so.1 => /usr/X11R6/lib/libGLU.so.1 (0x40918000)
libGL.so.1 => /usr/X11R6/lib/libGL.so.1 (0x4098b000)
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x409f2000)
libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40aad000)
libtiff.so.3 => /usr/lib/libtiff.so.3 (0x40aba000)
libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x40afe000)
libz.so.1 => /lib/libz.so.1 (0x40b1b000)
libpng.so.2 => /usr/lib/libpng.so.2 (0x40b28000)
libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x40b54000)
libdl.so.2 => /lib/libdl.so.2 (0x40b9d000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x40ba0000)
libm.so.6 => /lib/libm.so.6 (0x40bce000)
libc.so.6 => /lib/libc.so.6 (0x40bef000)
libstdc++.so.5 => /usr/lib/i686/libstdc++.so.5 (0x40cff000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40db6000)
libpthread.so.0 => /lib/libpthread.so.0 (0x40dbd000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
-------------
and now once again the previous data.
-----------
irb(main):001:0> require 'fox'
LoadError: /usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so:
undefined symbol: acquireSelection__8FXWindowPCUiUi -
/usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so
from /usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so
from (irb):1
--------------
nm /usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so | grep acquireS
0019b32c T FXWindow_acquireSelection__FP8FXWindowUl
001c05f8 t _wrap_FXWindow_acquireSelection__FiPUlUl
U acquireSelection__8FXWindowPCUiUi
U acquireSelection__8FXWindowPCUlUi
--------------
nm /usr/local/lib/libFOX-1.0.so.0 | grep acquireS
00209480 T acquireSelection__8FXWindowPCUlUi
-------------
The first is errormessage from irb. It says that acq...blabla...UiUi
is unknown symbol. Listing from those shared libraries clearly says,
that this unknown symbol is very similar to acq...blabla...UlUi
I don't know if this similarity is key to solution, but it's strange
isn't it ?
I had one more idea from last time. And it was nm *.o like this:
ruby install.rb setup
cd ext/fox
/x/my/r/FX/ext/fox 0> nm *.o | grep acq
00003974 T FXWindow_acquireClipboard__FP8FXWindowUl
000037dc T FXWindow_acquireSelection__FP8FXWindowUl
00028c98 t _wrap_FXWindow_acquireClipboard__FiPUlUl
00028aa8 t _wrap_FXWindow_acquireSelection__FiPUlUl
U acquireClipboard__8FXWindowPCUlUi
U acquireSelection__8FXWindowPCUlUi
/x/my/r/FX/ext/fox 0> nm *.so | grep acq
0019b4c4 T FXWindow_acquireClipboard__FP8FXWindowUl
0019b32c T FXWindow_acquireSelection__FP8FXWindowUl
001c07e8 t _wrap_FXWindow_acquireClipboard__FiPUlUl
001c05f8 t _wrap_FXWindow_acquireSelection__FiPUlUl
U acquireClipboard__8FXWindowPCUiUi
U acquireClipboard__8FXWindowPCUlUi
U acquireSelection__8FXWindowPCUiUi
U acquireSelection__8FXWindowPCUlUi
This means that this unknown symbol wasn't present in the *.o
but somehow it appear during the linking phase.
The linking command on my system was:
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
-lGLU -lGL -lX11 -lXext -ltiff -ljpeg -lz -lpng -lstdc++ -ldl -lcrypt
-lm -lc
gcc --version says 2.95.4
I'm not experienced enough to say if this is correct, but it doesn't
seem bad to me at least.
Ha, I got it !!!! The fxscintilla was anouncing those unknown symbols.
And because I havn't used it, i didn't even now that i compiled/installed
it in some ancient time. Recompilation of fxscintilla against fox1.0.27 solved
the problem.
Vlada
--
signed long mail;
|
|
From: Will M. <wi...@co...> - 2003-11-26 05:00:29
|
Joel VanderWerf wrote:
> > Will Merrell wrote:
> > the documentation and examples are so scant
> > that it is really hard to figure out, at least in my case.
>
> Arg, that's my fault.
Hey, don't beat yourself up, I knew your code was pretty alpha level. You
made it clear that it isn't done yet. And I *DID* figure it out. I am just
glad you wrote something that solves my problem and works well. Thanks!
> I will soon upload FoxTails 0.2, which is 1.8-friendly
> and has a tree browser widget. Maybe I'll have some
> time to document better...
That will be great, although, at this point its really Observable that I am
most working with at the moment. Once I get the current stuff working I may
use Foxtails more.
BTW any idea when you will release it?
> (The tree browser is like the other FoxTails widgets
> in that it allows multiple views and automatically
> syncs between model and view.)
Sounds great
> In the meantime, pls. feel free to ask questions,
> either here or to me directly.
If I could figure out what the questions are I'll ask them ;^)
As for documentation, I have some suggestions. The part I had the most
trouble with (still do for that matter) is figuring out how to work
observable things in other objects like windows. For example, if a value in
that window over there changes how do I find out about it and react to it
over here in this window. Specfically, how do I write a when_var for a
different object. None of the examples seemed to cover this case. To work it
out I wrote a little test program that I will include below. Some better
documentation in this area would help a lot.
===================== begin include ============================
#!/usr/bin/env ruby
require 'foxtails'
include Fox
include FoxTails
class OutputWindow < FXMainWindow
observable :mydata
def initialize(app, projName)
createWindow(app, projName)
end
def createWindow(app, projName)
@app = app
@outputdlg = FXDialogBox.new(app, projName, DECOR_ALL, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0)
outputText = FTTextField.new(@outputdlg, 20, self, :mydata)
outputText.dynamic = true
end
def create
@outputdlg.create
@outputdlg.position(200, 30, 150, 20)
@outputdlg.show(PLACEMENT_DEFAULT)
end
end
class TestWindow < FXMainWindow
observable :outp, :locdata
def initialize(*args)
super
inputText = FTTextField.new(self, 20, self, :locdata)
inputText.dynamic = true
outputText = FTTextField.new(self, 20, self, :locdata)
outputText.dynamic = true
end
def create
super
position(0, 30, 150, 60)
show(PLACEMENT_DEFAULT)
@outp = OutputWindow.new(self, "Output")
@outp.create
@outp.when_mydata CHANGES do
self.locdata = @outp.mydata
end
when_locdata CHANGES do
@outp.mydata = @locdata
end
end
end
class TestApp < FTApp
def initialize
super("Test", "TEST")
TestWindow.new(self, "Test")
end
end
TestApp.new.run
====================== end include =============================
|
|
From: Joel V. <vj...@PA...> - 2003-11-26 00:28:18
|
Will Merrell wrote: > For the last week or two I have been trying to implement a Delphi style > "Object Inspector" to work with this, and it has been kicking my butt. I am > trying to use the FoxTails/Observable extensions. I like the way it works > when I can figure it out, but the documentation and examples are so scant > that it is really hard to figure out, at least in my case. Arg, that's my fault. I will soon upload FoxTails 0.2, which is 1.8-friendly and has a tree browser widget. Maybe I'll have some time to document better... (The tree browser is like the other FoxTails widgets in that it allows multiple views and automatically syncs between model and view.) In the meantime, pls. feel free to ask questions, either here or to me directly. Joel |
|
From: Lyle J. <jl...@cf...> - 2003-11-25 22:21:45
|
cj...@ma... wrote: > Sorry for all the noise, I'll be quiet now. No problem, glad we were able to get it resolved! |
|
From: <cj...@ma...> - 2003-11-25 21:57:37
|
> FXApp is a class from the original FOX library Just worked that out - and that I had a dodgey Debian libfox and libfox-dev package installed. Removed them, and reinstalled the current ones (libfox1.0 and libfox1.0-dev) and it all works. I guess the Debian package maintainer screwed up the updates so I didn't have the current versions. Sorry for all the noise, I'll be quiet now. |
|
From: Lyle J. <ly...@kn...> - 2003-11-25 13:59:51
|
On Nov 25, 2003, at 2:10 AM, cj...@ma... wrote: >> FXIMPLEMENT(FXApp, FXObject, ...) >> somewhere in FXApp.cpp. This is the one that actually defines >> FXApp::metaClass and the other declarations from FXDECLARE. > > Ok, but I can't see FXApp.cpp anywhere - FXRbApp.cpp is there though. > I assume it's meant to be built from FXApp.i (though I don't have SWIG > installed), because it isn't in the source archive. Is this a simple > omission? FXApp is a class from the original FOX library (libFOX.so) and so its source files (FXApp.cpp and FXApp.h) are found in the FOX source code tree. Go to the directory where you originally built FOX and look under the 'src' directory, e.g. /home/cjh/fox-1.0.42/src/FXApp.cpp Hope this helps, Lyle |
|
From: Hugh S. S. E. E. <hg...@dm...> - 2003-11-25 10:27:32
|
On Mon, 24 Nov 2003, ly...@kn... wrote:
>
> On Mon, 24 Nov 2003 16:38:39 +0000 (GMT), Hugh Sasse Staff Elec Eng
> <hg...@dm...> wrote :
>
> > OK. ...Incidentally, I don't see that in the rightmost pane of the
> > rdocs... addTimeout is followed by append.
>
> The 'app' method is listed as a read-only attribute of the FXId class, on
> this page:
[...]
> You are correct that none of the attribute accessor methods (such as
> FXId#app) show up in RDoc's "Methods" pane. Perhaps that is a feature
> recommendation that could be made to RDoc's developer(s).
Will do, I've been bitten by this too often!
>
> > > What kind of object are you trying to call getApp() on? It is only
> > > defined for FXDC, FXFileDict, FXIconDict and FXId (and their subclasses,
> > > of course).
> >
> > I substituted @@app the last time it cropped up, and can't remember
> > which object it was, but in creating new
[...]
>
> Since 'app' is a (read-only) attribute of the FXId class, you can access its
> value using the FXId#app instance method, e.g.
[...]
Thank you.
>
> These are equivalent. There is no FXId class variable named "@@app", nor is
No, sorry, that's one I added to my application which holds the
FXApp itself.
> there an FXId instance variable "@app", however.
>
Hugh
|
|
From: Lyle J. <ly...@kn...> - 2003-11-25 02:45:01
|
On Nov 24, 2003, at 5:26 PM, Will Merrell wrote: > Actually, I would love a site where we could post some code and give > and get > feedback. I have no idea if what I am writing is good Ruby/Fox/FXRuby > code > or not. Any ideas or possibilities? May such a thing already exists? It's not quite what you're asking for, but you could carve out a section of the FOX Community Wiki site (http://fifthplanet.net) for this purpose. |
|
From: Lyle J. <ly...@kn...> - 2003-11-25 02:37:02
|
On Nov 24, 2003, at 5:16 PM, cj...@ma... wrote: >> The FXDECLARE macro itself is defined in FXObject.h: > > Yup, but this doesn't define the static, just declares it. Where are > these > statics defined? Oh, yes. The FXIMPLEMENT macro (also found in FXObject.h) is the counterpart of the FXDECLARE macro, and you should find the statement: FXIMPLEMENT(FXApp, FXObject, ...) somewhere in FXApp.cpp. This is the one that actually defines FXApp::metaClass and the other declarations from FXDECLARE. |
|
From: Will M. <wi...@co...> - 2003-11-24 23:26:33
|
On Sunday, November 23, 2003 6:10 PM, Fredrik Jagenheim wrote: > I want to make something that's pretty simple. I want to have > a couple of objects drawn on a canvas. These objects should > be event-aware, so I get notified if they're clicked, dragged > or otherwise manipulated. As it happens, I am using FXRuby, Fox and Ruby to prototype an app I have in mind and so far have implemented a small application that does a lot of what you ask. Right now its spread across a half dozen files so I won't include it here, but if there is (or could be) a site to post "in progress" code, I would be happy to share it. (I am hoping soon to create a website of my own for this project, but for now its on my "real soon now" list.) Actually, I would love a site where we could post some code and give and get feedback. I have no idea if what I am writing is good Ruby/Fox/FXRuby code or not. Any ideas or possibilities? May such a thing already exists? > But I can't even figure out which FX object to inherit from. > Neither 'FXDrawable' or 'FXImage' implements the 'connect' method. > > And since I can't even get to know when SEL_PAINT is requested, > I don't know how I can get to know if a key has been pressed > from SEL_KEYPRESSED. The aproach I took was to simply use an FXWindow and set up a couple of event handlers on mouse down, move and up. Each object (stored in a simple array of objects. Boy this language is fun!) handles its own drawing and has a method to determine if the mouse coordiates are inside it. So when I click on an object, the FXWindow iterates over each object until one says "That's me!" and then that one becomes the current object for all subsequent operations. Most of this is handled by a base "drawable object" class that handles most of this, and then each type of object is subclassed from it. For the last week or two I have been trying to implement a Delphi style "Object Inspector" to work with this, and it has been kicking my butt. I am trying to use the FoxTails/Observable extensions. I like the way it works when I can figure it out, but the documentation and examples are so scant that it is really hard to figure out, at least in my case. > I guess my lack of knowledge of how to program GUI is > the major culprit here, but could someone please point > me to some documents which could help me out? The stuff > I find on FXRuby seems to assume that I already know > Fox and the document on Fox assumes that I'm using > C++, although I'd suppose it's pretty easy to translate > into Ruby? You're right, the documentation is a bit thinner than I would like too, but you can work it out by studying the examples and using lots of "print" statements. I recomend launching your app from a command line so you can see the output as it happens. I also recomend the "code'a'little, test'a'little" approach. Start with something that works, make small changes, then test your changes, fixing then until they work. Repeat. Frequently. -- Will Merrell |
|
From: <cj...@ma...> - 2003-11-24 23:16:46
|
> The symbol it claims is missing (FXApp::metaClass) is a static member of Thanks Lyle, I'll chase it. None of the examples work, since I can't even "require 'fox'". I didn't get any compile errors, but at least I have more idea where to look. Will let you know. > The FXDECLARE macro itself is defined in FXObject.h: Yup, but this doesn't define the static, just declares it. Where are these statics defined? Clifford Heath. |
|
From: <ly...@kn...> - 2003-11-24 22:49:23
|
On Tue, 25 Nov 2003 09:07:15 +1100, cj...@ma... wrote :
> > OK. Can you show me the output of:
> > ldd /usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so
> > on your system?
>
> $ ldd /usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so
> libFOX-1.0.so.0 => /usr/lib/libFOX-1.0.so.0 (0x404dc000)
<snip>
The symbol it claims is missing (FXApp::metaClass) is a static member of the
FXApp class, and it is declared by the FXDECLARE macro that appears in the
FXApp class definition:
class FXAPI FXApp : public FXObject {
FXDECLARE(FXApp)
... and so on ...
};
The FXDECLARE macro itself is defined in FXObject.h:
#define FXDECLARE(classname) \
public: \
struct FXMapEntry { ... }; \
static const FXMetaClass metaClass; \
... and so on ...
So I can't see why this would be missing, unless something went wrong when
building the FOX library (libFOX.so). Just curious, can you run any of the
FOX example programs (i.e. those for the C++ library)? They are found under
the "tests" subdirectory of the FOX source code distribution.
Hope this helps,
Lyle
|
|
From: <ly...@kn...> - 2003-11-24 22:03:49
|
On Tue, 25 Nov 2003 08:45:35 +1100, cj...@ma... wrote :
> > Please see the topic "Cannot load library" under the "Things That Can
> > Go Wrong" section of this page:
>
> I have done, it isn't that problem.
OK. Can you show me the output of:
ldd /usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so
on your system?
|
|
From: <ly...@kn...> - 2003-11-24 17:15:52
|
On Mon, 24 Nov 2003 16:38:39 +0000 (GMT), Hugh Sasse Staff Elec Eng
<hg...@dm...> wrote :
> OK. ...Incidentally, I don't see that in the rightmost pane of the
> rdocs... addTimeout is followed by append.
The 'app' method is listed as a read-only attribute of the FXId class, on
this page:
http://www.fxruby.org/doc/api/classes/Fox/FXId.html
You are correct that none of the attribute accessor methods (such as
FXId#app) show up in RDoc's "Methods" pane. Perhaps that is a feature
recommendation that could be made to RDoc's developer(s).
> > What kind of object are you trying to call getApp() on? It is only
> > defined for FXDC, FXFileDict, FXIconDict and FXId (and their subclasses,
> > of course).
>
> I substituted @@app the last time it cropped up, and can't remember
> which object it was, but in creating new
> code I saw it again in code I was pasting, so raised the matter
> pre-emptively this time. In this case it is a child of FXId so
> should be OK.
Since 'app' is a (read-only) attribute of the FXId class, you can access its
value using the FXId#app instance method, e.g.
theWindowApp = theWindow.app
or, if you wish, you can use the (undocumented) getApp() method:
theWindowApp = theWindow.getApp()
These are equivalent. There is no FXId class variable named "@@app", nor is
there an FXId instance variable "@app", however.
|
|
From: Hugh S. S. E. E. <hg...@dm...> - 2003-11-24 17:00:47
|
On Mon, 24 Nov 2003, Lyle Johnson wrote:
> Hugh Sasse Staff Elec Eng wrote:
>
> > I am getting errors complaining about the getApp method being
> > indefined, though I used it successfully in the past. Indeed, it
s/in/un/; :-)
>
> The getApp() method is still there, although only its alias "app" is
> documented in the API docs.
OK. ...Incidentally, I don't see that in the rightmost pane of the
rdocs... addTimeout is followed by append.
>
> What kind of object are you trying to call getApp() on? It is only
> defined for FXDC, FXFileDict, FXIconDict and FXId (and their subclasses,
> of course).
I substituted @@app the last time it cropped up, and can't remember
which object it was, but in creating new
code I saw it again in code I was pasting, so raised the matter
pre-emptively this time. In this case it is a child of FXId so
should be OK.
Thank you,
Hugh
|
|
From: Lyle J. <jl...@cf...> - 2003-11-24 15:57:17
|
Hugh Sasse Staff Elec Eng wrote: > I am getting errors complaining about the getApp method being > indefined, though I used it successfully in the past. Indeed, it > does not seem to be listed at fxruby.org in the API docs. Should I > be using something else, is this change inadvertent, or is something > else amiss with my code? The getApp() method is still there, although only its alias "app" is documented in the API docs. What kind of object are you trying to call getApp() on? It is only defined for FXDC, FXFileDict, FXIconDict and FXId (and their subclasses, of course). |
|
From: Hugh S. S. E. E. <hg...@dm...> - 2003-11-24 15:43:30
|
I am getting errors complaining about the getApp method being indefined, though I used it successfully in the past. Indeed, it does not seem to be listed at fxruby.org in the API docs. Should I be using something else, is this change inadvertent, or is something else amiss with my code? Thank you, Hugh |
|
From: Lyle J. <jl...@cf...> - 2003-11-24 15:38:43
|
Fredrik Jagenheim wrote: > I want to make something that's pretty simple. I want to have a couple > of objects drawn on a canvas. These objects should be event-aware, so > I get notified if they're clicked, dragged or otherwise manipulated. Good, I think you will get a lot of people interested in the final product (including me ;) > But I can't even figure out which FX object to inherit from. Neither > 'FXDrawable' or 'FXImage' implements the 'connect' method. Right, the only objects that implement connect() are those that have a message target, namely, subclasses of FXWindow and FXDataTarget. I suspect that in your case you'll want to start out with the FXCanvas object (which is showcased in the scribble.rb example program) and work from that. > And since I can't even get to know when SEL_PAINT is requested, I > don't know how I can get to know if a key has been pressed from > SEL_KEYPRESSED. If the question is "when are SEL_PAINT messages sent", it's whenever part (or all) of a window is exposed and needs to be repainted. > I guess my lack of knowledge of how to program GUI is the major > culprit here, but could someone please point me to some documents > which could help me out? The stuff I find on FXRuby seems to assume > that I already know Fox and the document on Fox assumes that I'm using > C++, although I'd suppose it's pretty easy to translate into Ruby? The three primary sources for FOX documentation are the two sites you mentioned (the FOX home page at http://www.fox-toolkit.org and the FXRuby home page at http://www.fxruby.org) as well as the FOX Community Wiki site, found here: http://fifthplanet.net Hope this helps, Lyle |
|
From: Lyle J. <jl...@cf...> - 2003-11-24 15:30:42
|
Vlada wrote:
> I'm not sure if writing onthe right address, but didn't found any other.
This is the right place to ask questions about FXRuby.
> FXRuby 1.0.27
> fox 1.0.46
>
> Compilation goes well in both.
OK.
> -----------
> irb(main):001:0> require 'fox'
>
> LoadError: /usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so:
<snip>
What output do you get if you type:
ldd /usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so
at the shell prompt?
|
|
From: Lyle J. <ly...@kn...> - 2003-11-24 13:46:35
|
On Nov 24, 2003, at 3:52 AM, cj...@ma... wrote: > I have Ruby 1.8.0 on Debian, and built FXRuby-1.0.27 last night. > In irb, require 'fox' yields: > > LoadError: /usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so: > undefined symbol: _ZN5FXApp9metaClassE - > /usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so > from /usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so > > c++filt says _ZN5FXApp9metaClassE is FXApp::metaClass. > > Any idea why this symbol is undefined? > Please see the topic "Cannot load library" under the "Things That Can Go Wrong" section of this page: http://www.fxruby.org/doc/build.html I am guessing that the FOX library (libFOX.so) is installed in a directory that isn't in the load path for dynamic libraries. Hope this helps, Lyle |
|
From: Fredrik J. <fr...@po...> - 2003-11-23 23:10:04
|
Hi, I want to make something that's pretty simple. I want to have a couple of objects drawn on a canvas. These objects should be event-aware, so I get notified if they're clicked, dragged or otherwise manipulated. But I can't even figure out which FX object to inherit from. Neither 'FXDrawable' or 'FXImage' implements the 'connect' method. And since I can't even get to know when SEL_PAINT is requested, I don't know how I can get to know if a key has been pressed from SEL_KEYPRESSED. I guess my lack of knowledge of how to program GUI is the major culprit here, but could someone please point me to some documents which could help me out? The stuff I find on FXRuby seems to assume that I already know Fox and the document on Fox assumes that I'm using C++, although I'd suppose it's pretty easy to translate into Ruby? TIA, //F |
|
From: Vlada <su...@ce...> - 2003-11-22 15:36:21
|
Hi,
I'm not sure if writing onthe right address, but didn't found any other.
FXRuby 1.0.27
fox 1.0.46
Compilation goes well in both.
ldconfig done...
-----------
irb(main):001:0> require 'fox'
LoadError: /usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so:
undefined symbol: acquireSelection__8FXWindowPCUiUi -
/usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so
from /usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so
from (irb):1
--------------
nm /usr/local/lib/ruby/site_ruby/1.8/i686-linux/fox.so | grep acquireS
0019b32c T FXWindow_acquireSelection__FP8FXWindowUl
001c05f8 t _wrap_FXWindow_acquireSelection__FiPUlUl
U acquireSelection__8FXWindowPCUiUi
U acquireSelection__8FXWindowPCUlUi
--------------
nm /usr/local/lib/libFOX-1.0.so.0 | grep acquireS
00209480 T acquireSelection__8FXWindowPCUlUi
-------------
My library experience is low, so I don't know what to try next.
Vlada...
and please cc me, I'm not on the list.
--
signed short mail;
|
|
From: <ly...@kn...> - 2003-11-20 15:46:53
|
On Thu, 20 Nov 2003 15:38:28 +0100 (CET), Mahmut Ozcan <mah...@ya...> wrote : > > As stated on the FXRuby home page, FXRuby only works > > with FOX 1.0.x. So > > you're already heading for trouble trying to use FOX > > 1.1.41; it shouldn't > > even compile against FOX 1.1.41, much less link. > > > > > May I ask u when it will be possible to use the FOX > 1.1.x version? FOX 1.1.x is the (unstable) development branch and as such is changing rapidly. When the API is frozen and this version becomes the new stable version (i.e. FOX 1.2) then you should expect to see a compatible version of FXRuby. > > You should go back to this version of fox-lib, > > especially since it compiled > > and linked correctly. > > > > Is FXRuby stable with that version of foxlib (1.0.x) ? Yes, as stated on the FXRuby home page, FXRuby is compatible with any version of fox-1.0. |
|
From: <ly...@kn...> - 2003-11-19 17:18:56
|
On Wed, 19 Nov 2003 18:08:15 +0100 (CET), Mahmut Ozcan <mah...@ya...> wrote : > First thanks to all persons worked and continue to > working on FXRuby. It's great! Thanks! > Ok, let's say when the things seems wrong : > > I'm working on Linux (SuSE 8.1) > > -fox-lib-1.1.41 > -latest stable snapshot of Ruby (yesterday, 1.8.1) > -FXRuby-1.0.27 As stated on the FXRuby home page, FXRuby only works with FOX 1.0.x. So you're already heading for trouble trying to use FOX 1.1.41; it shouldn't even compile against FOX 1.1.41, much less link. > Before the !ABOVE! steps I've tried the following and > succeed > (Of course I've completely removed the !BELOW! libs > and ruby after that) > > -fox-lib-1.0.47 !!! > -Ruby 1.8.0 !!! > -FXRuby-1.0.27.tar.gz. You should go back to this version of fox-lib, especially since it compiled and linked correctly. > With that config I have tried all the examples in the > examples directory. It seems all going well. If that was working, why did you change it? ;) But to summarize, be sure to use one of the fox-1.0.x releases with FXRuby. Hope this helps, Lyle P.S. Please send questions like this to the fxruby-users mailing list. The fxruby-announce mailing list is for announcements only. |
|
From: Lyle J. <ly...@kn...> - 2003-11-19 02:15:28
|
On Nov 18, 2003, at 6:00 PM, Tom Kunz wrote: > Thanks for the insight, I would have spent hours in the API docs=20 > trying to figure that part out.=A0 I know this might be out of scope = for=20 > this list, but do you have any pointers to how I should try to=20 > accomplish native Win printing from within Ruby?=A0 Scintilla? Or=20 > something else? I don't know from first-hand experience, and a quick google for "win32=20= printer ruby" didn't yield much of interest ;) You might just try=20 taking the question to the general ruby-talk list, to see how (if)=20 other people have handled this.= |
3 messages has been excluded from this view by a project administrator.
