Just curious: What is that status of ruby bindings for WxWindows?
Phil
Things are progressing great. Kevin Smith has taken the development
lead and made significant progress in the creation of a functional
Ruby-WxWindows library using a templating approach w/out SWIG. An
Alpha release is being finalized after a discussion on the best naming
convention when wrapping the underlying Wx classes/methods/constants.
By consensus we decided to adopt a Rubyesque (underscore_methods)
convention, and generate documentation accordingly. Kevin is now busy
finalizing that name change, and updating the samples. Once the code
is ready, Kevin will produce a binary for Linux, and Curt Hibbs will
build a binary for Win32. I am going to try and build one for OS X.
The WxRuby project is using Savannah so the code, et al is in CVS at:
And there is a Wiki located here (although not updated too often right
now…busy coding!):
http://www.wxruby.org/cgi-bin/wiki.pl
There is some old code in the CVS repository that will be removed soon.
The two directories under CVS that contain the active code are ‘src’
and ‘samples’. Once cleaned up, these and a few others (doc, etc) will
be left. If you check out the CVS tree, just ignore the other
directories for now.
Once the files are released (for Alpha) they will be located on the
Savannah project page and we will make an announcement here (and on
RAA).
Best,
-Rich
···
On Friday, June 20, 2003, at 04:37 PM, Phil Tomson wrote:
Just curious: What is that status of ruby bindings for WxWindows?
Phil
Cool!
I look forward to seeing WxRuby. Can’t wait. 
···
On Thu, Jun 26, 2003 at 10:09:35PM +0900, Richard Kilmer wrote:
Things are progressing great. Kevin Smith has taken the development
lead and made significant progress in the creation of a functional
Ruby-WxWindows library using a templating approach w/out SWIG. An
Alpha release is being finalized after a discussion on the best naming
convention when wrapping the underlying Wx classes/methods/constants.
By consensus we decided to adopt a Rubyesque (underscore_methods)
convention, and generate documentation accordingly. Kevin is now busy
finalizing that name change, and updating the samples. Once the code
is ready, Kevin will produce a binary for Linux, and Curt Hibbs will
build a binary for Win32. I am going to try and build one for OS X.The WxRuby project is using Savannah so the code, et al is in CVS at:
wxRuby GUI Framework - Summary [Savannah]
And there is a Wiki located here (although not updated too often right
now…busy coding!):http://www.wxruby.org/cgi-bin/wiki.pl
There is some old code in the CVS repository that will be removed soon.
The two directories under CVS that contain the active code are ‘src’
and ‘samples’. Once cleaned up, these and a few others (doc, etc) will
be left. If you check out the CVS tree, just ignore the other
directories for now.Once the files are released (for Alpha) they will be located on the
Savannah project page and we will make an announcement here (and on
RAA).Best,
-Rich
On Friday, June 20, 2003, at 04:37 PM, Phil Tomson wrote:
Just curious: What is that status of ruby bindings for WxWindows?
Phil
Daniel Carrera | OpenPGP fingerprint:
Graduate TA, Math Dept | 6643 8C8B 3522 66CB D16C D779 2FDD 7DAC 9AF7 7A88
UMD (301) 405-5137 | http://www.math.umd.edu/~dcarrera/pgp.html
Fantastic. I’m glad to hear that things are progressing so quickly, and
I’m looking forward to the first alpha release!
- Brian Wisti
http://coolnamehere.com/
···
At 10:09 PM 6/26/2003 +0900, you wrote:
Things are progressing great. Kevin Smith has taken the development lead
and made significant progress in the creation of a functional
Ruby-WxWindows library using a templating approach w/out SWIG. An Alpha
release is being finalized after a discussion on the best naming
convention when wrapping the underlying Wx classes/methods/constants.
By consensus we decided to adopt a Rubyesque (underscore_methods)
convention, and generate documentation accordingly. Kevin is now busy
finalizing that name change, and updating the samples. Once the code is
ready, Kevin will produce a binary for Linux, and Curt Hibbs will build a
binary for Win32. I am going to try and build one for OS X.The WxRuby project is using Savannah so the code, et al is in CVS at:
wxRuby GUI Framework - Summary [Savannah]
And there is a Wiki located here (although not updated too often right
now…busy coding!):http://www.wxruby.org/cgi-bin/wiki.pl
There is some old code in the CVS repository that will be removed
soon. The two directories under CVS that contain the active code are
‘src’ and ‘samples’. Once cleaned up, these and a few others (doc, etc)
will be left. If you check out the CVS tree, just ignore the other
directories for now.Once the files are released (for Alpha) they will be located on the
Savannah project page and we will make an announcement here (and on RAA).Best,
-Rich
On Friday, June 20, 2003, at 04:37 PM, Phil Tomson wrote:
Just curious: What is that status of ruby bindings for WxWindows?
Phil
Brian Wisti
brian@coolnamehere.com
http://coolnamehere.com/
Hi evreyone.
I am experimenting with ruby /gtk and so far it looks so nice & easy
(In spite of the lack of Documantation, i am thinking to leave tk…)
After one hour trying …
How can I register the key press event on an Entry ?
On tk I do…
entry .filter
bind .filter “puts ouch!!”
gtk ???
filter=Gtk::Entry.new
filter.signal_connect(Gtk::Entry::SIGNAL_????????) {
puts "ouch!!"
}
BTW: Any gtk/ruby reading recommendations ?
thanks.
How would you compare it with Ruby-GNOME?
Sincerely,
Gour
···
Daniel Carrera (dcarrera@math.umd.edu) wrote:
Cool!
I look forward to seeing WxRuby. Can’t wait.
–
Gour
gour@mail.inet.hr
Registered Linux User #278493
and the mental power of this list gave me the answer …
Gtk::Entry::SIGNAL_KEY_PRESS_EVENT
I like to answer myself …
Thanks any way …
Bermejo, Rodrigo wrote:
···
Hi evreyone.
I am experimenting with ruby /gtk and so far it looks so nice & easy
(In spite of the lack of Documantation, i am thinking to leave tk…)After one hour trying …
How can I register the key press event on an Entry ?
On tk I do…
entry .filter
bind .filter “puts ouch!!”gtk ???
filter=Gtk::Entry.new
filter.signal_connect(Gtk::Entry::SIGNAL_???) {
puts “ouch!!”
}BTW: Any gtk/ruby reading recommendations ?
thanks.
–
CIAT - General Electric
Rodrigo Bermejo
Information Technologies.
Dial comm:8*879-0644
mailto:rodrigo.bermejo@ps.ge.com
Well, I guess I’d have to wait for WxRuby to be finished before I can
compare the implementation.
Now, as for how I would compare WxWindows with Gnome:
I like Gnome very much, but it is still a very Linux-centric (or at
least Unix-centric) toolkit. WxWindows is multiplantform, but the neat
thing about it is that it uses the native toolkit in each platform. So,
under Linux it uses Gnome, and under Windows it uses the Win32 API.
So, in a sense, by using WxWindows I’m not really giving up Gnome, but I
am getting platform independence.
Daniel Carrera | OpenPGP fingerprint:
Graduate TA, Math Dept | 6643 8C8B 3522 66CB D16C D779 2FDD 7DAC 9AF7 7A88
UMD (301) 405-5137 | http://www.math.umd.edu/~dcarrera/pgp.html
···
On Fri, Jun 27, 2003 at 01:28:00AM +0900, Gour wrote:
Daniel Carrera (dcarrera@math.umd.edu) wrote:
Cool!
I look forward to seeing WxRuby. Can’t wait.How would you compare it with Ruby-GNOME?
Yes, wx provides a much greater level of platform independence. Since it
relies on native toolkits, it is just about the only toolkit that I can use
unmodified on OS X, Linux, and Windows. That’s a big deal to me
- Brian w
Brian Wisti
brian@coolnamehere.com
http://coolnamehere.com/
···
At 01:42 AM 6/27/2003 +0900, you wrote:
Now, as for how I would compare WxWindows with Gnome:
I like Gnome very much, but it is still a very Linux-centric (or at
least Unix-centric) toolkit. WxWindows is multiplantform, but the neat
thing about it is that it uses the native toolkit in each platform. So,
under Linux it uses Gnome, and under Windows it uses the Win32 API.So, in a sense, by using WxWindows I’m not really giving up Gnome, but I
am getting platform independence.
Thank you for Your replies.
It looks like we’ll soon need to start taking look at WxWindows documentation
Sincerely,
Gour
···
Brian Wisti (brian@coolnamehere.com) wrote:
At 01:42 AM 6/27/2003 +0900, you wrote:
Now, as for how I would compare WxWindows with Gnome:
I like Gnome very much, but it is still a very Linux-centric (or at
least Unix-centric) toolkit. WxWindows is multiplantform, but the neat
thing about it is that it uses the native toolkit in each platform. So,
under Linux it uses Gnome, and under Windows it uses the Win32 API.So, in a sense, by using WxWindows I’m not really giving up Gnome, but I
am getting platform independence.Yes, wx provides a much greater level of platform independence. Since it
relies on native toolkits, it is just about the only toolkit that I can use
unmodified on OS X, Linux, and Windows. That’s a big deal to me
–
Gour
gour@mail.inet.hr
Registered Linux User #278493
Yes, wx provides a much greater level of platform independence. Since it
relies on native toolkits, it is just about the only toolkit that I can use
unmodified on OS X, Linux, and Windows. That's a big deal to me
It seems that people are getting too lazy. For a non trivial
application it is not possible and will be possible to have a write
once, compile everywhere GUI. Of course you can reduce the dependent
plattform code to a small amount of 5-10% but thats all.
The biggest problem is the different event sequences that you get from
the window system. So if you do some non standart tricks thats it. Not
to mention all other nice little things like tray icons etc.
We will be translating the documentation into a more Rubyesque flavor
based on the requirement to change the method and constant names in the
Ruby port.
-rich
···
On Thursday, June 26, 2003, at 02:11 PM, Gour wrote:
It looks like we’ll soon need to start taking look at WxWindows
documentationSincerely,
Gour
Lothar Scholz wrote:
It seems that people are getting too lazy. For a non trivial
application it is not possible and will be possible to have a write
once, compile everywhere GUI. Of course you can reduce the dependent
plattform code to a small amount of 5-10% but thats all.The biggest problem is the different event sequences that you get from
the window system. So if you do some non standart tricks thats it. Not
to mention all other nice little things like tray icons etc.
That’s okay. Most of my GUIs are pretty trivial. 
If I were
concerned about nonstandard tricks or highly platform-specific elements,
I’d be using the frameworks that were appropriate to those needs.
- Brian W
http://coolnamehere.com/
“Richard Kilmer” rich@infoether.com wrote in message
news:23F6461E-A806-11D7-9F05-000A95765742@infoether.com…
We will be translating the documentation into a more Rubyesque flavor
based on the requirement to change the method and constant names in the
Ruby port.
Please do! One of the annoying things about wxPython and wxPerl is the
documentation. Basically it is just the C++ docs with a few 'isms. I don’t
know C++ nor do I want to learn it. But using Python or Perl I would have to
learn to at least READ it. Blech!
Bob