Tom
On Wed, 2004-05-12 at 06:13, Glenn wrote:
Well in the interest of learning Ruby and keeping up the momentum of
using it (it really is a nice language IMO), I’ve decided to write a
suite of retro-games in Ruby, using RUDL.First one will be pacman, followed by something like space invaders
etc. Just a bit of meaningless fun and a good way to learn.
Glenn wrote:
I’m interested in Jamey’s comment that he uses Ruby with FXRuby,
instead of Delphi. I’ll take a look at FXRuby, but wonder why you
prefer to (or so it appears) hand code a GUI instead of draw it. That
would seem a backward step for me? (no offense meant, I’m interested)
You should look at fox-tool.rubyforge.org. It is just a preview, but for
~ most of my FXRuby projects it has worked a charm.
kaspar
semantics & semiotics
code manufacture
www.tua.ch/ruby
In article 59364f29.0405040023.234bb283@posting.google.com,
I’m interested in Jamey’s comment that he uses Ruby with FXRuby,
instead of Delphi. I’ll take a look at FXRuby, but wonder why you
prefer to (or so it appears) hand code a GUI instead of draw it. That
would seem a backward step for me? (no offense meant, I’m interested)
I’m not Jamey, but I’ll offer my comments…
I’m using Ruby FLTK (Fast Light ToolKit) for developing a cross-platform
GUI. I started out using a modified version of FLUID (FLTK’s GUI builder)
that spits out Ruby code instead of C++. I must say that FLUID is a very
nice GUI-building tool, however, after a while I started ‘hand-coding’ the
GUI instead. Why would I do that? Because I prefer the I can hand-craft
over the code that gets generated by the GUI builder. Actually, it might
be more accurate to say I prefer the style of hand-coded GUI code over
thee style that tends to be imposed by the GUI builder. I find that my
code tends to be much more reusable than the generated code because when
I’m coding I tend to think more in terms of aggregating various widgets
into classes that represent some component of the GUI. The GUI builder
basically put everything into one big class.
So for me, I found that I prefer not to use the GUI builder because I’ve
got more control over the design of the code. YMMV
Phil
Glenn glenn_m_smith@hotmail.com wrote:
What’s changed is that I’m using actively trying to use Ruby as much
as possible, which means that I’m starting to see more possibilities
for it!
:o)
“Robert Klemme” bob.news@gmx.net wrote in message news:2gedh1F1r73jU1@uni-berlin.de…
“Glenn” glenn_m_smith@hotmail.com schrieb im Newsbeitrag
news:59364f29.0405120213.5123e73@posting.google.com…Well in the interest of learning Ruby and keeping up the momentum of
using it (it really is a nice language IMO), I’ve decided to write a
suite of retro-games in Ruby, using RUDL.First one will be pacman, followed by something like space invaders
etc. Just a bit of meaningless fun and a good way to learn.I’ll wait for space invaders. g
I’ve also ordered the Pragmatic Programmer’s book (I know it’s
on-line, but I wanted an old-fashioned printed copy!).You share that passion with a lot others in here.
At work I’m using Ruby for this and that, usual file-processing and
other scripting requirements.What has changed? I thought you said you have no use for a scripting
language. Or did I misread something there?Regards
robert
Phil Tomson wrote:
I’m not Jamey, but I’ll offer my comments…
So for me, I found that I prefer not to use the GUI builder because I’ve
got more control over the design of the code. YMMVPhil
Phil, I couldn’t have said it any better myself. 
Jamey
Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information. If you are not the intended recipient(s), you are hereby notified that any dissemination, unauthorized review, use, disclosure or distribution of this email and any materials contained in any attachments is prohibited. If you receive this message in error, or are not the intended recipient(s), please immediately notify the sender by email and destroy all copies of the original message, including attachments.