[fxruby-users] Moving On

Ralph Shnelvar ralphs at dos32.com
Wed Aug 4 11:14:09 EDT 2010


I'm sorry to see you go ...

There is one additional piece of information that I would like from you:  Given that many developers (me included) have spent considerable resources learning FXRuby, buying your book, searching for documentation, etc., ...

What graphical platform would you recommend porting to?


Wednesday, August 4, 2010, 8:20:54 AM, you wrote:

LJ> Cross-posted to the blog (at
LJ> http://lylejohnson.name/blog/2010/08/04/moving-on/):

LJ> When Jamis Buck wrote last year about ceasing development on
LJ> Capistrano, his post really struck a chord with me. If this post
LJ> reminds you of that one, it's because I re-read it before sitting down
LJ> to compose this one. It was the next best thing to having Jamis on
LJ> hand to give me a pep talk before I had to stand up and say something
LJ> that I've been putting off saying for too long. As a bonus, I could
LJ> visualize him calmly and quietly making one of those neat little
LJ> string figures while I tried decide exactly what it was I wanted to
LJ> say.

LJ> It is with mixed feelings that I announce that I'm stepping away from
LJ> FXRuby development, effective immediately. I will no longer be
LJ> accepting bug reports, support requests, feature requests, or general
LJ> emails related to FXRuby. I will continue to follow the mailing list,
LJ> but I am no longer the maintainer of this project.

LJ> When I started developing FXRuby back in late 2000, it was a lot of
LJ> fun for me. I was still new to Ruby (most of us were, back then) and
LJ> Ruby was in need of a good GUI toolkit, so working on FXRuby provided
LJ> me with not only a good way to learn the ins and outs of the language,
LJ> but also to get really plugged into the community. In recent years,
LJ> however, working on FXRuby has become a chore. I'm a decade older, at
LJ> a different place in my life and career, and there are frankly just
LJ> too many other things that I'd rather be working on at this point.
LJ> These feelings are compounded by the fact that FOX development has, as
LJ> best I can tell, stalled out, and without anything new to look forward
LJ> to on the FOX front there's little motivation for me to continue
LJ> working on FXRuby. So it's time to make a clean break and call it
LJ> quits.

LJ> I would like to take this opportunity to thank everyone who did
LJ> participate in the FXRuby community over the years. Knowing that you
LJ> found my work of some value means a lot to me, and I appreciate the
LJ> encouragement that I received from you along the way. I was never
LJ> successful at organizing a development team around FXRuby, something
LJ> which I regret, but a number of people contributed patches or
LJ> third-party tools and extensions to FXRuby. If I tried to name all of
LJ> those contributors, I would invariably leave someone off the list by
LJ> accident, so let me just say: Thanks, you guys; you know who you are.
LJ> A special thanks as well to those of you who bought the book. And of
LJ> course, I owe an immense debt of gratitude to Jeroen van der Zijp,
LJ> without whom there would be no FOX toolkit, and thus no FXRuby.

LJ> Someone on the mailing list asked whether FOX and FXRuby are "pretty
LJ> much dead." I can't speak for Jeroen or the FOX project. As for
LJ> FXRuby, however, that's up to you. FXRuby is, and always has been, an
LJ> open source project. If you are interested in hacking on FXRuby, or
LJ> even taking over maintenance of the project, please feel free to fork
LJ> the project on GitHub (http://github.com/lylejohnson/fxruby) and
LJ> release updates as you see fit. The Wiki
LJ> (http://wiki.github.com/lylejohnson/fxruby/) has a lot of information
LJ> about setting up a development and build environment on Windows, Linux
LJ> and Mac OS X, and if you have specific questions about the build chain
LJ> I'll do my best to help you get set up.

LJ> If no one steps forward to maintain FXRuby, that’s fine too. The code
LJ> has been pretty stable, if not bug-free, for quite awhile now, and it
LJ> may the case that the code's "done" anyways. If you feel that way and
LJ> want to continue using FXRuby, it's not going anywhere. If on the
LJ> other hand, you have some fresh new ideas about how to move ahead, go
LJ> for it! I will be cheering you on from the sidelines.

LJ> In closing, thanks again for all of your support over the last ten
LJ> years. I'm certainly not done with Ruby, and I'm looking forward to
LJ> exploring other ways in which I can participate in the Ruby community
LJ> in the future.
LJ> _______________________________________________
LJ> fxruby-users mailing list
LJ> fxruby-users at rubyforge.org
LJ> http://rubyforge.org/mailman/listinfo/fxruby-users

Best regards,
 Ralph                            mailto:ralphs at dos32.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/fxruby-users/attachments/20100804/820bbf41/attachment-0001.html>

More information about the fxruby-users mailing list