fxruby-users Mailing List for FXRuby (Page 27)
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: <kun...@ho...> - 2003-09-12 16:26:16
|
jeroen wrote: >>For someone not too familiar with the framework yet, can I find and use >>this database somewhere, to build upon when starting to build my own >>list if needed? > > > If you do it from FOX, it is a matter of adding entries under the > registry group FILETYPES with key,value pairs as follows: > > "key" is the extension. Note FOX's system can handle sub-extensions like > .tar.gz and .gz. Also, you can use the entire filename as well, e.g. > you can map README to a certain command. > That sounds really useful and powerful. :) > "value" is of the form: > command string ';' extension string ';' bigicon [ ':' bigiconopen ] ';' miniicon [ ':' miniiconopen ] ';' mimetype > > So for example for a .jpg image type one would add: > > jpg = "/usr/local/bin/xv %s &;JPEG Image;image.xpm;mini/image.xpm;image/jpeg" > > Note the "%s" which is replaced by the actual filename. > > You can also map directory names, as in: > > /home/jeroen = ";Home Directory;kfm_home.xpm;mini/kfm_home.xpm;application/x-folder" > > > In this case the "key" is a directory name. It must start with / or \. > FOX allows subdirectories, so you can do something like: > > /include - ... > > which causes directories of the form <blabla>/include to have a certain icon. > > The icons are found by consulting the registry entry: iconpath in the > group SETTINGS. Under windows, it is a ';' separated list of directories. > Thanks, great explanation. Although I don't seem to have any of these registry entries (according to search at least...) where should they be added? Or should the application create them? > I have looked at it a little bit, and involves quite a bit of work; nevertheless, > it can be done. I have not decided yet whether we should deliver a tool to > populate the FOX database from the native-stored information, or just use > the native-stored information. Continuing to use the FOX database, as you > see, has more flexibility in terms of the bindings, while the latter is > not so flexible and makes adding our own bindings more difficult. > I'd definitely would want a tool to populate my own db with, which I then could edit. Or, if it was built into the toolkit itself, it could first read directly from the defaults, then anything in the local db would override if pointing to the same. Either way, I do not like the non-flexible solution. Thanks again, -- Kristoffer -- Sent using: Mozilla Thunderbird 0.2 (20030901) http://www.mozilla.org/projects/thunderbird/ |
|
From: <kun...@ho...> - 2003-09-12 16:11:26
|
ly...@kn... wrote: > The current FXRuby release(s), numbered 1.0.x, are only for use with FOX > 1.0.x releases. Because FOX 1.1 is an unstable development series, there > will be no FXRuby 1.1 releases. As soon the current FOX 1.1 development line > is released as FOX 1.2 (i.e. as the new "stable" branch"), there will be a > compatible FXRuby 1.2. > So, this means I'm out of luck with the "fixed" FXDirList widget then? -- Kristoffer -- Sent using: Mozilla Thunderbird 0.2 (20030901) http://www.mozilla.org/projects/thunderbird/ |
|
From: jeroen <je...@fo...> - 2003-09-12 13:24:04
|
On Friday 12 September 2003 03:42 am, you wrote:
> First off, Sorry for the double mailing to the list. I had a bit of
> trouble with my email provider...
>
> jeroen wrote:
> >The FXDirList in FOX 1.0 did have this bug under Windows; the new one in
> >FOX 1.1.x however shows the list of drives as it was supposed to.
>
> Ah, great. My bad - will find an upgrade then, if it is available for
> FXRuby. :)
>
> >The workaround for the old FXDirList is to prefix the drive letter in
> >front of the path; if you don't, the routines which turn a path into
> >a normalized absolute path will slap the default drive letter in front
> >[it will also expand environment variables and simplify the path].
>
> Actually, I did prefix with the drive letter. I realized afterward that
> there was a bigger problem than it ignoring my path, it probably really
> should show all drives, which it didn't. OTOH, this is apparently fixed
> in newer versions, so I'll upgrade.
AFAIK, explicitly placing the prefix worked with the old FXDirList.
Anyway, its moot as the new one shows ALL the drive letters.
> >As for the file types, it is as follows. On Windows, FOX uses the
> >registry but continues to follow its own bindings-database;
>
> For someone not too familiar with the framework yet, can I find and use
> this database somewhere, to build upon when starting to build my own
> list if needed?
If you do it from FOX, it is a matter of adding entries under the
registry group FILETYPES with key,value pairs as follows:
"key" is the extension. Note FOX's system can handle sub-extensions like
.tar.gz and .gz. Also, you can use the entire filename as well, e.g.
you can map README to a certain command.
"value" is of the form:
command string ';' extension string ';' bigicon [ ':' bigiconopen ] ';' miniicon [ ':' miniiconopen ] ';' mimetype
So for example for a .jpg image type one would add:
jpg = "/usr/local/bin/xv %s &;JPEG Image;image.xpm;mini/image.xpm;image/jpeg"
Note the "%s" which is replaced by the actual filename.
You can also map directory names, as in:
/home/jeroen = ";Home Directory;kfm_home.xpm;mini/kfm_home.xpm;application/x-folder"
In this case the "key" is a directory name. It must start with / or \.
FOX allows subdirectories, so you can do something like:
/include - ...
which causes directories of the form <blabla>/include to have a certain icon.
The icons are found by consulting the registry entry: iconpath in the
group SETTINGS. Under windows, it is a ';' separated list of directories.
> >it *is*
> >possible to write a tool which populates this bindings database
> >from the "normal" Windows associations [the native file- associations
> >are splattered all over the place, and in some cases the icons have to
> >be lifted out of executables].
>
> Yeah, true that. Though I thought that there would be some kind of
> central repository or something, since a *lot* of third party programs,
> file managers and the like does manage to use the correct icons even if
> they don't use the built-in Win components. Of course, they might just
> have been doing a huge amount of hacking.
I have looked at it a little bit, and involves quite a bit of work; nevertheless,
it can be done. I have not decided yet whether we should deliver a tool to
populate the FOX database from the native-stored information, or just use
the native-stored information. Continuing to use the FOX database, as you
see, has more flexibility in terms of the bindings, while the latter is
not so flexible and makes adding our own bindings more difficult.
> >On Unix, one can simply drop a text file (the FOX registry is
> > human-readable text on UNIX) into $HOME/.foxrc/Desktop and have bindings
> > available for all applications.
>
> Yeah, I've seen how the system works, and I think I can manage to build
> my own associations if I have to. The thing I'd really like though was
> to steal any system associations, if available, at least to provide a
> start. :)
That certainly seems to be an argument for building a separate tool to
populate the registry.
> Thanks a lot, that makes things a bit clearer... I'll probably come back
> with some more in a moment, though. ;)
Regards,
Jeroen
--
+----------------------------------------------------------------------------+
| Copyright (C) 05:50 09/12/2003 Jeroen van der Zijp. All Rights Reserved. |
+----------------------------------------------------------------------------+
|
|
From: Recheis M. <Mei...@av...> - 2003-09-12 10:25:03
|
hi, thanks for your offer, but i am currently developing a similar tool for = Ruby. i did today download DlgEditor and was really surprised, because mine = looks exactly the same, though i didn't see yours till today.=20 i got also a shutter to the right and a switcher to the left, containing the properties. but our tools are also a lot different. i don't do explicit layout. i make use of the layout managers, which is = the fox way. also i got a treelist showing the widget hierarchy, so you can browse = and never loose a widget. - best regards, Meinrad -----Urspr=FCngliche Nachricht----- Von: Kristoffer Lund=E9n [mailto:kun...@ho...] Gesendet: Freitag, 12. September 2003 10:42 An: je...@fo... Cc: fxr...@li... Betreff: [Fxruby-users] Re: Fxruby-users digest, Vol 1 #57 - 2 msgs First off, Sorry for the double mailing to the list. I had a bit of=20 trouble with my email provider... jeroen wrote: >The FXDirList in FOX 1.0 did have this bug under Windows; the new one = in >FOX 1.1.x however shows the list of drives as it was supposed to. =20 > > =20 > Ah, great. My bad - will find an upgrade then, if it is available for=20 FXRuby. :) >The workaround for the old FXDirList is to prefix the drive letter in >front of the path; if you don't, the routines which turn a path into >a normalized absolute path will slap the default drive letter in front >[it will also expand environment variables and simplify the path]. > > =20 > Actually, I did prefix with the drive letter. I realized afterward that=20 there was a bigger problem than it ignoring my path, it probably really=20 should show all drives, which it didn't. OTOH, this is apparently fixed=20 in newer versions, so I'll upgrade. >As for the file types, it is as follows. On Windows, FOX uses the=20 >registry but continues to follow its own bindings-database;=20 > For someone not too familiar with the framework yet, can I find and use=20 this database somewhere, to build upon when starting to build my own=20 list if needed? >it *is*=20 >possible to write a tool which populates this bindings database >from the "normal" Windows associations [the native file- associations >are splattered all over the place, and in some cases the icons have to >be lifted out of executables]. > > =20 > Yeah, true that. Though I thought that there would be some kind of=20 central repository or something, since a *lot* of third party programs,=20 file managers and the like does manage to use the correct icons even if=20 they don't use the built-in Win components. Of course, they might just=20 have been doing a huge amount of hacking. >On Unix, one can simply drop a text file (the FOX registry is = human-readable >text on UNIX) into $HOME/.foxrc/Desktop and have bindings available for = >all applications. > > > =20 > Yeah, I've seen how the system works, and I think I can manage to build=20 my own associations if I have to. The thing I'd really like though was=20 to steal any system associations, if available, at least to provide a=20 start. :) Thanks a lot, that makes things a bit clearer... I'll probably come back = with some more in a moment, though. ;) -- Kristoffer --=20 Sent using: Mozilla Thunderbird 0.2 (20030901) http://www.mozilla.org/projects/thunderbird/ ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Fxruby-users mailing list Fxr...@li... https://lists.sourceforge.net/lists/listinfo/fxruby-users |
|
From: <kun...@ho...> - 2003-09-12 08:43:30
|
First off, Sorry for the double mailing to the list. I had a bit of trouble with my email provider... jeroen wrote: >The FXDirList in FOX 1.0 did have this bug under Windows; the new one in >FOX 1.1.x however shows the list of drives as it was supposed to. > > > Ah, great. My bad - will find an upgrade then, if it is available for FXRuby. :) >The workaround for the old FXDirList is to prefix the drive letter in >front of the path; if you don't, the routines which turn a path into >a normalized absolute path will slap the default drive letter in front >[it will also expand environment variables and simplify the path]. > > > Actually, I did prefix with the drive letter. I realized afterward that there was a bigger problem than it ignoring my path, it probably really should show all drives, which it didn't. OTOH, this is apparently fixed in newer versions, so I'll upgrade. >As for the file types, it is as follows. On Windows, FOX uses the >registry but continues to follow its own bindings-database; > For someone not too familiar with the framework yet, can I find and use this database somewhere, to build upon when starting to build my own list if needed? >it *is* >possible to write a tool which populates this bindings database >from the "normal" Windows associations [the native file- associations >are splattered all over the place, and in some cases the icons have to >be lifted out of executables]. > > > Yeah, true that. Though I thought that there would be some kind of central repository or something, since a *lot* of third party programs, file managers and the like does manage to use the correct icons even if they don't use the built-in Win components. Of course, they might just have been doing a huge amount of hacking. >On Unix, one can simply drop a text file (the FOX registry is human-readable >text on UNIX) into $HOME/.foxrc/Desktop and have bindings available for >all applications. > > > > Yeah, I've seen how the system works, and I think I can manage to build my own associations if I have to. The thing I'd really like though was to steal any system associations, if available, at least to provide a start. :) Thanks a lot, that makes things a bit clearer... I'll probably come back with some more in a moment, though. ;) -- Kristoffer -- Sent using: Mozilla Thunderbird 0.2 (20030901) http://www.mozilla.org/projects/thunderbird/ |
|
From: jeroen <je...@fo...> - 2003-09-12 05:04:03
|
> Message: 1 > Date: Thu, 11 Sep 2003 17:01:17 +0200 > From: =?ISO-8859-1?Q?Kristoffer_Lund=E9n?= <kun...@ho...> > To: fxr...@li... > Subject: [Fxruby-users] Default associations in FXFileList and FXDirList > Reply-To: fxr...@li... > > Hello! > > I am toying a bit with FXFileList and also FXDirList - pretty easy to > get running, but I wonder about the associations to the files, and their > icons. > > I've tried ot google a bit, and I've went through this list and searched > the original FOX documentation - I'm sure it is there somewhere, but I > must be looking in the wrong place then... > > Are there any good way to import the default icons, or has anyone > aldready done the job of creating something that imitates the usual > options? Seems a bit silly to manually tie mp3 to this icon etc when the > system already does that somewhere else - that information is apparently > available as other applications can get at it. Any ideas and tips are > welcome, otherwise I guess I'll have to do that work and share it > instead. ;-) > > Also, I am having a bit of trouble with FXDirList - no matter what I set > directory to, it always starts at 'C:\' - am I doing something wrong? > All I do is create it, then set the directory, which works with FXFileList. > > I am trying this out on an Win XP box, with ruby 1.8.0 and FXRuby 1.0.22 > (I think). Got it all in that package that the Pragmatic Programmers put > together for Windows. However, I will not only be on this platform, so > if there are any Windows specific issues, I'd be thankful if that was > noted. :) > > -- Kristoffer Kristoffer, The FXDirList in FOX 1.0 did have this bug under Windows; the new one in FOX 1.1.x however shows the list of drives as it was supposed to. The workaround for the old FXDirList is to prefix the drive letter in front of the path; if you don't, the routines which turn a path into a normalized absolute path will slap the default drive letter in front [it will also expand environment variables and simplify the path]. As for the file types, it is as follows. On Windows, FOX uses the registry but continues to follow its own bindings-database; it *is* possible to write a tool which populates this bindings database from the "normal" Windows associations [the native file- associations are splattered all over the place, and in some cases the icons have to be lifted out of executables]. On Unix, one can simply drop a text file (the FOX registry is human-readable text on UNIX) into $HOME/.foxrc/Desktop and have bindings available for all applications. - Jeroen +----------------------------------------------------------------------------+ | Copyright (C) 20:20 09/11/2003 Jeroen van der Zijp. All Rights Reserved. | +----------------------------------------------------------------------------+ |
|
From: <kun...@ho...> - 2003-09-11 15:02:35
|
Hello! I am toying a bit with FXFileList and also FXDirList - pretty easy to get running, but I wonder about the associations to the files, and their icons. I've tried ot google a bit, and I've went through this list and searched the original FOX documentation - I'm sure it is there somewhere, but I must be looking in the wrong place then... Are there any good way to import the default icons, or has anyone aldready done the job of creating something that imitates the usual options? Seems a bit silly to manually tie mp3 to this icon etc when the system already does that somewhere else - that information is apparently available as other applications can get at it. Any ideas and tips are welcome, otherwise I guess I'll have to do that work and share it instead. ;-) Also, I am having a bit of trouble with FXDirList - no matter what I set directory to, it always starts at 'C:\' - am I doing something wrong? All I do is create it, then set the directory, which works with FXFileList. I am trying this out on an Win XP box, with ruby 1.8.0 and FXRuby 1.0.22 (I think). Got it all in that package that the Pragmatic Programmers put together for Windows. However, I will not only be on this platform, so if there are any Windows specific issues, I'd be thankful if that was noted. :) -- Kristoffer |
|
From: <kun...@ho...> - 2003-09-11 14:13:53
|
Hello! I am toying a bit with FXFileList and also FXDirList - pretty easy to get running, but I wonder about the associations to the files, and their icons. I've tried ot google a bit, and I've went through this list and searched the original FOX documentation - I'm sure it is there somewhere, but I must be looking in the wrong place then... Are there any good way to import the default icons, or has anyone aldready done the job of creating something that imitates the usual options? Seems a bit silly to manually tie mp3 to this icon etc when the system already does that somewhere else - that information is apparently available as other applications can get at it. Any ideas and tips are welcome, otherwise I guess I'll have to do that work and share it instead. ;-) Also, I am having a bit of trouble with FXDirList - no matter what I set directory to, it always starts at 'C:\' - am I doing something wrong? All I do is create it, then set the directory, which works with FXFileList. I am trying this out on an Win XP box, with ruby 1.8.0 and FXRuby 1.0.22 (I think). Got it all in that package that the Pragmatic Programmers put together for Windows. However, I will not only be on this platform, so if there are any Windows specific issues, I'd be thankful if that was noted. :) -- Kristoffer |
|
From: Lyle J. <jl...@cf...> - 2003-09-10 15:05:19
|
Dalibor Sramek wrote: > I would like to add some icons to my FXRuby application. Unfortunately I am not > very talented when it comes to graphics. So I have two questions: > > 1, Is it possible to add icons used in FXRuby samples to my GPLed application? > (This question is naturally for Lyle but I believe others can be interested in > the answer.) The icons used in the shutter.rb example program were obtained from Gort's Icons (http://www.forrestwalter.com/icons) are used by me with permission from Forrest Walter. They are definitely not free for general purpose use and you'd need to check with him for the conditions. As for the other icons, their origins are pretty shady. I picked them up from FOX, and I suspect that they are a hodgepodge of original icons by Jeroen as well as icons found "here and there" on the web. > 2, Is there any source of GPLed, public domain etc. icons on the web? (Yes, I > have googled for a couple of minutes...) I am interested in the answer to this question too. It has come up before ;) |
|
From: Lyle J. <jl...@cf...> - 2003-09-10 14:31:13
|
Recheis Meinrad wrote:
> the middle mouse button has no specific function in a gui.
> that's why i chose it to select widgets in my dialog editor.
> but the problem is:
>
> MenuTitle, MenuCommand, ComboBox and others#
> dont support this event.
>
> what can i overwrite in menutitle to be able to receive
> SEL_MIDDLEBUTTONPRESS?
You are right, it looks like FXMenuTitle doesn't forward
SEL_MIDDLEBUTTONPRESS (or SEL_MIDDLEBUTTONPRESS, or SEL_RIGHTBUTTONxxx)
to its target. I probably need to check with Jeroen to see why he did
that and if it can be changed for FOX 1.2.
At any rate, the ugly workaround for FOX 1.0 is to subclass FXMenuTitle,
intercept the SEL_MIDDLEBUTTONPRESS message that the event loop (FXApp)
sends directly to the FXMenuTitle, and then do what we would have
expected it to do in the first place (forward the message to the
target). Below is some sample code to get you started:
require 'fox'
include Fox
class MyMenuTitle < FXMenuTitle
include Responder
def initialize(*args)
super
FXMAPFUNC(SEL_MIDDLEBUTTONPRESS, 0, :onMiddleBtnPress)
FXMAPFUNC(SEL_MIDDLEBUTTONRELEASE, 0, :onMiddleBtnRelease)
end
def onMiddleBtnPress(sender, sel, evt)
if enabled?
if (target != nil) &&
(target.handle(self,
MKUINT(selector, SEL_MIDDLEBUTTONPRESS), evt) != 0)
return 1
end
end
return 0
end
def onMiddleBtnRelease(sender, sel, evt)
if enabled?
if (target != nil) &&
(target.handle(self,
MKUINT(selector, SEL_MIDDLEBUTTONRELEASE), evt) != 0)
return 1
end
end
return 0
end
end
class MainWindow < FXMainWindow
def initialize(app)
# Initialize base class
super(app, "Middle Mouse Test", nil, nil, DECOR_ALL, 0, 0, 200, 200)
# Menubar
menubar = FXMenubar.new(self, LAYOUT_SIDE_TOP|LAYOUT_FILL_X)
# File menu
filemenu = FXMenuPane.new(self)
FXMenuCommand.new(filemenu, "New")
FXMenuCommand.new(filemenu, "Open...")
FXMenuCommand.new(filemenu, "Save")
FXMenuCommand.new(filemenu, "Quit", nil, app, FXApp::ID_QUIT)
menuTitle = MyMenuTitle.new(menubar, "&File", nil, filemenu)
menuTitle.connect(SEL_MIDDLEBUTTONPRESS) {
puts "foo"
}
end
# Start
def create
# Create window
super
# Show the main window
show(PLACEMENT_SCREEN)
end
end
if __FILE__ == $0
# Make an application
application = FXApp.new("MiddleMouse", "FXRuby")
# Create main window
window = MainWindow.new(application)
# Create the application
application.create
# Run
application.run
end
Hope this helps,
Lyle
|
|
From: Dalibor S. <da...@in...> - 2003-09-10 09:37:15
|
Hi, folks. I would like to add some icons to my FXRuby application. Unfortunately I am not very talented when it comes to graphics. So I have two questions: 1, Is it possible to add icons used in FXRuby samples to my GPLed application? (This question is naturally for Lyle but I believe others can be interested in the answer.) 2, Is there any source of GPLed, public domain etc. icons on the web? (Yes, I have googled for a couple of minutes...) Thanks Dalibor Sramek -- Dalibor Sramek http://www.insula.cz/dali | In the eyes of cats, dal...@in... | all things belong to cats. |
|
From: Recheis M. <Mei...@av...> - 2003-09-09 20:30:37
|
hi,=20 the middle mouse button has no specific function in a gui. that's why i chose it to select widgets in my dialog editor. but the problem is: MenuTitle, MenuCommand, ComboBox and others# dont support this event. what can i overwrite in menutitle to be able to receive = SEL_MIDDLEBUTTONPRESS?? - Henon |
|
From: Recheis M. <Mei...@av...> - 2003-09-09 12:25:17
|
ok, i found out;
one must specify a size. i generally am not very pleased, that the =
mdichildwindow doesn't resize itself according to the content size.
hi,=20
i am very mad that i can not make this work though i have much fxruby =
experiance allready.=20
now i try to calm down and write a message=20
#-------=20
require 'fox'=20
include Fox=20
app =3D FXApp.new("", "")=20
window =3D FXMainWindow.new(app, '...', nil, nil, DECOR_ALL, 0, 0, 200, =
100)=20
client=3DFXMDIClient.new window, LAYOUT_FILL_X|LAYOUT_FILL_Y=20
child=3DFXMDIChild.new client, 'child' , nil, nil, 0, 0, 50, 50
client.setActiveChild child=20
# child.restore=20
app.create=20
window.show(0)=20
app.run=20
# ----=20
i expect the mdi child to show up now. but is doesn't=20
what s missing?=20
i don't understand the concept of the mdi client fully. what's the mdi =
menu for?=20
it seems to be okay to omit it. is it required? if so i don't understand =
why it is an extra class.=20
how do i get the mdi thing working?=20
- Henon=20
|
|
From: Recheis M. <Mei...@av...> - 2003-09-09 12:08:47
|
hi,=20
i am very mad that i can not make this work though i have much fxruby =
experiance allready.
now i try to calm down and write a message
#-------
require 'fox'
include Fox
app =3D FXApp.new("", "")
window =3D FXMainWindow.new(app, '...', nil, nil, DECOR_ALL, 0, 0, 200, =
100)
client=3DFXMDIClient.new window, LAYOUT_FILL_X|LAYOUT_FILL_Y
child=3DFXMDIChild.new client, 'child'
client.setActiveChild child
child.restore
app.create
window.show(0)
app.run
# ----
i expect the mdi child to show up now. but is doesn't
what s missing?
i don't understand the concept of the mdi client fully. what's the mdi =
menu for?
it seems to be okay to omit it. is it required? if so i don't understand =
why it is an extra class.
how do i get the mdi thing working?
- Henon
|
|
From: Hugh S. S. E. E. <hg...@dm...> - 2003-09-04 18:09:50
|
On Thu, 4 Sep 2003, Lyle Johnson wrote:
> Hugh Sasse Staff Elec Eng wrote:
>
> > OK, then is is worth raising these issues with Jeroen? Bearing in
> > mind comments below, of course.
>
> I'm not sure how to answer the question. While not presuming to speak
Your answer gave me what I wanted. The ideas have some value, and
he is likely to be receptive. (It might have been that he were so
snowed under he wouldn't want ANY suggestions till 2005! :-), so
you've given me useful input here.) Thank you
Hugh
|
|
From: Lyle J. <jl...@cf...> - 2003-09-04 14:59:11
|
Hugh Sasse Staff Elec Eng wrote:
> OK, then is is worth raising these issues with Jeroen? Bearing in
> mind comments below, of course.
I'm not sure how to answer the question. While not presuming to speak
for Jeroen, I think he'd probably agree with you that (for example) a
2-D canvas object would be a nice thing to have. To put things in
perspective, there's a survey running at the FOX Community Wiki site:
http://www.fifthplanet.net/cgi-bin/wiki.pl
that indicates many additional things that people would like to see for
FOX (including, as you mentioned, better documentation).
So I think it's worthwhile to raise these points, if for no other reason
to add your voice to the chorus asking for feature X or Y. At the same
time, it is important to understand that, for the most part, Jeroen is
primarily going to work on things that are interesting to him.
|
|
From: Hugh S. S. E. E. <hg...@dm...> - 2003-09-03 09:52:12
|
On Tue, 2 Sep 2003, Lyle Johnson wrote:
> Hugh Sasse Staff Elec Eng wrote:
>
> > * A simple means to operate controls programmatically, to aid test
> > [...] like FXPseudoMouse and FXPseudoKeyboard [...]
> >
> Sure, this sounds like an interesting approach to the problem.
>
thanks.
> > * More documentation with examples is needed, but this is ongoing
> > anyway, and will happen in due course. I think a map, graphical
[...]
> >
> I think RDoc has an option for generating inheritance diagrams as part
> of its output. Let me investigate that and see how well it works in
> practice...
I don't have graphviz, and don't like the licencing [way off topic]
and would like to re-implement it with SVG, but haven't got my head
around rdoc internals yet...
>
> > * I'm not entirely sure why FXTreeItems are not just FXTreeLists,
> > in the way that Trees are normally defined in computer science.
> >
> Yes, we've discussed this previously on the list. I do not know all of
> the factors that went into this design decision by Jeroen, but it's
> unlikely to change at this point.
I'll maybe ask, because understanding, well, probably "teleology" is
the right word here, can aid in seeing the whole picture.
>
> >Do these comments seem valid, or are they the equivalent of saying
> >["]I can make C code more like the Pascal I've grown to love" :-), (i.e.
> >tactless and rather stupid in the hindsight I don't have yet)?
> >
> Of course your comments are valid! But it's important to note that like
OK, then is is worth raising these issues with Jeroen? Bearing in
mind comments below, of course.
> so many open source software projects, FXRuby is something that I work
> on in my spare time, for free. So, for example, I can get motivated to
Absolutely: there is no obligation for anyone to shape the world to
suit me. I think these things might possibly be worthwhile enough to
help other people, help the uptake of FOX, and thus help bring
"hands to the pump" as far as supporting the code base goes. But
that is hypothesis/speculation!
> write more documentation because I understand that this activity has the
> potential to save me time later. That is, if I answer the question in a
[...]
Yes, also why when I make notes about things I put them on the web.
I probably use them more than other people!
>
> On the other hand, I don't have any personal need for a Canvas-like
> widget. If I did, I probably would have developed one by now. For that
Agreed. And if I knew enough about the internals and had time I
gladly contribute.
> feeling it's a more substantial development effort than that ;) If
Yes, but I suspect that some FOX "black belts" may find this easier
than either of us to do. This is really what my question of
validity is about: is it worth suggesting these features? Sometimes
outsiders can't contribute much that is material, but the fresh
viewpoint alone can throw up something useful. Hence lateral
thinking. Once my mind is shaped by Fox I won't be able to do that,
so this discomfort may be worth something in itself.
> someone were to take this project on themselves, I would do my best to
> support them and, if it were their wish, incorporate it into the
> standard FXRuby library at some point.
>
Thank you,
Hugh
|
|
From: Lyle J. <ly...@kn...> - 2003-09-03 02:14:06
|
Hugh Sasse Staff Elec Eng wrote:
>This seems to be the sort of essential functiaonality that deserves
>encapsulation in some kind of object. Fox has a good set of widgets
>with things like dials that Tk doesn't have, etc, but in trying to
>move from Tk to Fox I have been finding the learning curve very
>steep. It seemed easier to get going with Tk. So how can I change
>this from just a whinge :-) to constructive criticism? Well, I'm
>new to fox so lots of this may be invalid, but I think that Fox
>would benefit from having:
>
> * A 2-d object that holds graphic state, as mentioned above.
>
Agreed.
> * A simple means to operate controls programmatically, to aid test
> driven design. I'd suggest something like FXPseudoMouse and
> FXPseudoKeyboard for starters, which can be pointed at an
> FXObject and will manage the sending of events to it.
>
Sure, this sounds like an interesting approach to the problem.
> * More documentation with examples is needed, but this is ongoing
> anyway, and will happen in due course. I think a map, graphical
> if necessary, of the widget hierarchy would be really useful,
> like Rdoc's middle pane but tree structured...? There are some of
> these on the web, but I can't seem to see the motorways/freeways
> for all the minor roads and cul-de-sacs that show up on the maps.
>
I think RDoc has an option for generating inheritance diagrams as part
of its output. Let me investigate that and see how well it works in
practice...
> * I'm not entirely sure why FXTreeItems are not just FXTreeLists,
> in the way that Trees are normally defined in computer science.
>
Yes, we've discussed this previously on the list. I do not know all of
the factors that went into this design decision by Jeroen, but it's
unlikely to change at this point.
>Do these comments seem valid, or are they the equivalent of saying
>"If I write
>#define { BEGIN
>#define } END
>I can make C code more like the Pascal I've grown to love" :-), (i.e.
>tactless and rather stupid in the hindsight I don't have yet)?
>
Of course your comments are valid! But it's important to note that like
so many open source software projects, FXRuby is something that I work
on in my spare time, for free. So, for example, I can get motivated to
write more documentation because I understand that this activity has the
potential to save me time later. That is, if I answer the question in a
tutorial or in improved API documentation, that's one less question for
someone to ask down the road ;)
On the other hand, I don't have any personal need for a Canvas-like
widget. If I did, I probably would have developed one by now. For that
matter, if it were something I could knock out in an afternoon or two, I
might go ahead and do it out of the kindness of my heart; but I have the
feeling it's a more substantial development effort than that ;) If
someone were to take this project on themselves, I would do my best to
support them and, if it were their wish, incorporate it into the
standard FXRuby library at some point.
|
|
From: jeroen <je...@fo...> - 2003-09-03 02:10:33
|
On Tuesday 02 September 2003 12:05 pm, Lyle Johnson wrote: > Recheis Meinrad wrote: > > lyle wrote: > >> Can you provide a short program which demonstrates this bug? > > > > see, that the separator pads left and right by 50, allthough i did only > > set padLeft > > Thanks, I see the problem now. This is actually a bug in FOX, so I have > submitted a fix to Jeroen for the next release of fox-1.0.x. The problem has been fixed just now in FOX 1.0.46; just dropped on the FTP site; the other problem was that it was using drawLine(). Under Windows, lines drawn with drawLine() are one pixel off w.r.t. X-Windows. Using fillRectangle() this problem is circumvented and the visual results should be exactly the same. Regards, Jeroen -- +----------------------------------------------------------------------------+ | Copyright (C) 19:50 09/ 2/2003 Jeroen van der Zijp. All Rights Reserved. | +----------------------------------------------------------------------------+ |
|
From: Hugh S. S. E. E. <hg...@dm...> - 2003-09-03 00:55:03
|
On Tue, 2 Sep 2003, Hugh Sasse Staff Elec Eng actually wrote:
> Do these comments seem valid, or are they the equivalent of saying
> "If I write
> #define { BEGIN
> #define } END
MY GOODNESS!! I've only been programming in C for...what?...16
years!? How the photon did I write that backwards? Maybe I should
stop trying to get 25 hours out of each day! Or I should learn
FORTH.
> I can make C code more like the Pascal I've grown to love" :-), (i.e.
> tactless and rather stupid in the hindsight I don't have yet)?
Hugh.
|
|
From: Hugh S. S. E. E. <hg...@dm...> - 2003-09-02 21:54:08
|
On Tue, 2 Sep 2003, ly...@kn... wrote: > > > I still seem to be seeing the old one (09-Jun-2003), have refreshed > > my browser (Firebird) twice. > > Very strange. I just went back to check the files page at SourceForge: > > http://sourceforge.net/project/showfiles.php?group_id=20243 Oh, I'm coming in from FXRuby.org/doc/api ... > > and mine is definitely showing the "20030901" snapshot. > > > I notice that FXGLViewer starts with : > > "Canvas, an area drawn by another object" ... > > Obviously, this is an example of cut and paste gone bad. I just checked the > FOX header files and the same comment appears in FXGLViewer.h (the C++ > include file for the FXGLViewer class). > > > ... which would seem to contradict > > http://www.fxruby.org/doc/opengl.html > > which says that FXCanvas must point at an FXGLVisual in order to > > work because the canvas provides no state. > > > > This seems to ba a "false" clue as to how to make the scribble [....] > > this non-orthogonal approach, but it seems disappointing, to me. > > It is true that both FXGLCanvas and its subclass, FXGLViewer, must have a > reference to an FXGLVisual which describes their capabilities (e.g. the [...] > FXGLCanvas widget is very much like the (non-OpenGL) FXCanvas widget in the > sense that it doesn't "remember" what has been drawn into it. Yes. > > Now, FXGLViewer is a different story. You can assign a "scene" to an > FXGLViewer, and whenever the FXGLViewer needs to repaint itself, it uses the > state information in that scene. The scene is a reference to an FXGLObject > (or one its subclasses, almost always an FXGLGroup). That's roughly what I was thinking. Thank you. > > What FOX/FXRuby does *not* have (although it would be nice) is a 2-D > equivalent to the FXGLViewer. That is, there is no 2-D, non-OpenGL type > widget that can automatically redraw itself based on some scene or model That's what I was thinking when I commented about non-orthogonality. > object. Tk's Canvas is such a widget and might be a good model for someone > interested in developing such a widget. > This seems to be the sort of essential functiaonality that deserves encapsulation in some kind of object. Fox has a good set of widgets with things like dials that Tk doesn't have, etc, but in trying to move from Tk to Fox I have been finding the learning curve very steep. It seemed easier to get going with Tk. So how can I change this from just a whinge :-) to constructive criticism? Well, I'm new to fox so lots of this may be invalid, but I think that Fox would benefit from having: * A 2-d object that holds graphic state, as mentioned above. * A simple means to operate controls programmatically, to aid test driven design. I'd suggest something like FXPseudoMouse and FXPseudoKeyboard for starters, which can be pointed at an FXObject and will manage the sending of events to it. * More documentation with examples is needed, but this is ongoing anyway, and will happen in due course. I think a map, graphical if necessary, of the widget hierarchy would be really useful, like Rdoc's middle pane but tree structured...? There are some of these on the web, but I can't seem to see the motorways/freeways for all the minor roads and cul-de-sacs that show up on the maps. * I'm not entirely sure why FXTreeItems are not just FXTreeLists, in the way that Trees are normally defined in computer science. Do these comments seem valid, or are they the equivalent of saying "If I write #define { BEGIN #define } END I can make C code more like the Pascal I've grown to love" :-), (i.e. tactless and rather stupid in the hindsight I don't have yet)? Thank you for your continued help on this path, Hugh |
|
From: Lyle J. <jl...@cf...> - 2003-09-02 16:51:32
|
Recheis Meinrad wrote: > lyle wrote: >> Can you provide a short program which demonstrates this bug? > > see, that the separator pads left and right by 50, allthough i did only > set padLeft Thanks, I see the problem now. This is actually a bug in FOX, so I have submitted a fix to Jeroen for the next release of fox-1.0.x. |
|
From: Lyle J. <ly...@kn...> - 2003-09-01 22:26:23
|
Fredrik Jagenheim wrote: >Where can I get the latest API documentation? > >The download on sourceforge from 20030602 doesn't have documentation >for lots of classes; FXScrollbar for example. > Thanks for pointing this out to me, I didn't realize it had been so long since the last "snapshot". I've just uploaded a new one, based on the latest CVS versions (from 2003/09/01). |
|
From: Fredrik J. <fr...@po...> - 2003-09-01 18:46:25
|
Hi, Where can I get the latest API documentation? The download on sourceforge from 20030602 doesn't have documentation for lots of classes; FXScrollbar for example. I'm not always online so I can't rely on the fxruby.org website all the time. ;) //F |
|
From: Lyle J. <ly...@kn...> - 2003-09-01 14:20:48
|
Brett S Hallett wrote: > I recently upgraded to Ruby 1.8 , installed OK, however I have now > 'lost' contact with FXRuby !! > Anybody else have this problem & how to recove my FOX access ?? You need to recompile (and reinstall) FXRuby against Ruby 1.8. This is going to be true for any "third-party" (i.e. not in the standard library) C/C++ Ruby extension modules that you may have been using. |
3 messages has been excluded from this view by a project administrator.
