Status of wxRuby?

Hi,

I’m considering developing a larger app with windows GUI. I’ve used FxRuby
for previous similar efforts and would probably do it again if MDI
windows in Fox looked more like native windows widgets (I might have
missed something though but last time I checked Lyle’s examples they
didn’t look alike imho, sorry to Lyle if I missed) and I havne’t heard
about wxWindows.

In Python world and elsewhere it seems people are very satisfied with
wxWindows, both the API as such and the look and feel of resulting apps.

Having been away from this list for some time I’m not sure what is the
current status of wxRuby efforts. Could someone enlighten me? Is there
something of a time plan for it? (;))

If anyone has examples of MDI windows apps in wxWindows I’d also like to
hear about it (links)?

Thanks,

Robert Feldt

Ps. Yes I have read the now 7 weeks old Changelog available on
http://savannah.nongnu.org/cgi-bin/viewcvs/wxruby/wxruby/ but would like
some comments from people working on it. What? When? and why? basically…
:wink: and thanks…

Robert Feldt feldt@ce.chalmers.se writes:

Having been away from this list for some time I’m not sure what is
the current status of wxRuby efforts. Could someone enlighten me? Is
there something of a time plan for it? (;))

This is a RAQ (i just made that up: recently asked question). A
groups.google.com search of comp.lang.ruby sorted by date should bring
up some threads.

My summary from memory:

- The FreeRIDE folks started a port but it is way too raw to
  release.
- The FreeRIDE folks aren't working on it, may in the future but
  don't hold breath.
- Others are welcome to pick it up.

Matt Armstrong wrote:

Robert Feldt feldt@ce.chalmers.se writes:

Having been away from this list for some time I’m not sure what is
the current status of wxRuby efforts. Could someone enlighten me? Is
there something of a time plan for it? (;))

This is a RAQ (i just made that up: recently asked question). A
groups.google.com search of comp.lang.ruby sorted by date should bring
up some threads.

My summary from memory:

- The FreeRIDE folks started a port but it is way too raw to
  release.
- The FreeRIDE folks aren't working on it, may in the future but
  don't hold breath.
- Others are welcome to pick it up.

You mostly got it right.

I plan to get back to wxRuby as soon as I can pick up a little extra
bandwidth – FreeRIDE, family, moving, and job-hunting have me currently
snowed under. If FXRuby were to shortly pick a few missing key parts, I
might consider passing the reigns to someone else so that I can devote more
time to FreeRIDE. Barring that I’ll be back on wxRuby in a few weeks.

As always, anyone who wants to pitch in and help is very welcome to do so –
just drop me an email.

Curt

I’d be interested in knowing what the “few missing key parts” of FXRuby
consists of, and how wxWindows solves/overcomes them.

Thanks,

Robert Feldt

···

On Fri, 24 Jan 2003, Curt Hibbs wrote:

My summary from memory:

- The FreeRIDE folks started a port but it is way too raw to
  release.
- The FreeRIDE folks aren't working on it, may in the future but
  don't hold breath.
- Others are welcome to pick it up.

You mostly got it right.

I plan to get back to wxRuby as soon as I can pick up a little extra
bandwidth – FreeRIDE, family, moving, and job-hunting have me currently
snowed under. If FXRuby were to shortly pick a few missing key parts, I
might consider passing the reigns to someone else so that I can devote more
time to FreeRIDE. Barring that I’ll be back on wxRuby in a few weeks.

Robert Feldt wrote:

My summary from memory:

- The FreeRIDE folks started a port but it is way too raw to
  release.
- The FreeRIDE folks aren't working on it, may in the future but
  don't hold breath.
- Others are welcome to pick it up.

You mostly got it right.

I plan to get back to wxRuby as soon as I can pick up a little extra
bandwidth – FreeRIDE, family, moving, and job-hunting have me currently
snowed under. If FXRuby were to shortly pick a few missing key parts, I
might consider passing the reigns to someone else so that I can
devote more
time to FreeRIDE. Barring that I’ll be back on wxRuby in a few weeks.

I’d be interested in knowing what the “few missing key parts” of FXRuby
consists of, and how wxWindows solves/overcomes them.

Thanks,

Robert Feldt

I was internationalization and Mac support, but now we’ve got FreeRIDE
running on the Mac under FXRuby (available in the upcoming release Candidate
#2). So the only real issue left is I18N.

Curt

···

On Fri, 24 Jan 2003, Curt Hibbs wrote:

Also the issue of native look-n-feel (LNF) is a big deal to many. For
many applications it is important to have a platform native LNF and
WxWindows gives you that. To me that’s not as big a deal for an IDE,
but other apps may have issues. i18n is the bigger issue for us.

-rich

···

On Friday, January 24, 2003, at 08:13 AM, Curt Hibbs wrote:

Robert Feldt wrote:

On Fri, 24 Jan 2003, Curt Hibbs wrote:

My summary from memory:

- The FreeRIDE folks started a port but it is way too raw to
  release.
- The FreeRIDE folks aren't working on it, may in the future but
  don't hold breath.
- Others are welcome to pick it up.

You mostly got it right.

I plan to get back to wxRuby as soon as I can pick up a little extra
bandwidth – FreeRIDE, family, moving, and job-hunting have me
currently
snowed under. If FXRuby were to shortly pick a few missing key
parts, I
might consider passing the reigns to someone else so that I can
devote more
time to FreeRIDE. Barring that I’ll be back on wxRuby in a few weeks.

I’d be interested in knowing what the “few missing key parts” of
FXRuby
consists of, and how wxWindows solves/overcomes them.

Thanks,

Robert Feldt

I was internationalization and Mac support, but now we’ve got
FreeRIDE
running on the Mac under FXRuby (available in the upcoming release
Candidate
#2). So the only real issue left is I18N.

Curt

Sorry for being lazy here but can you elaborate on how wxWindows supports
i18n?

/Robert

···

On Fri, 24 Jan 2003, Richard Kilmer wrote:

Also the issue of native look-n-feel (LNF) is a big deal to many. For
many applications it is important to have a platform native LNF and
WxWindows gives you that. To me that’s not as big a deal for an IDE,
but other apps may have issues. i18n is the bigger issue for us.

Robert Feldt wrote:

Sorry for being lazy here but can you elaborate on how wxWindows supports
i18n?

I think he’s referring to wxWindows’ support for localization of text
messages in the GUI and its support for Unicode strings (on some platforms).