Cross-posted to the blog (at http://lylejohnson.name/blog/2010/08/04/moving-on/): When Jamis Buck wrote last year about ceasing development on Capistrano, his post really struck a chord with me. If this post reminds you of that one, it''s because I re-read it before sitting down to compose this one. It was the next best thing to having Jamis on hand to give me a pep talk before I had to stand up and say something that I''ve been putting off saying for too long. As a bonus, I could visualize him calmly and quietly making one of those neat little string figures while I tried decide exactly what it was I wanted to say. It is with mixed feelings that I announce that I''m stepping away from FXRuby development, effective immediately. I will no longer be accepting bug reports, support requests, feature requests, or general emails related to FXRuby. I will continue to follow the mailing list, but I am no longer the maintainer of this project. When I started developing FXRuby back in late 2000, it was a lot of fun for me. I was still new to Ruby (most of us were, back then) and Ruby was in need of a good GUI toolkit, so working on FXRuby provided me with not only a good way to learn the ins and outs of the language, but also to get really plugged into the community. In recent years, however, working on FXRuby has become a chore. I''m a decade older, at a different place in my life and career, and there are frankly just too many other things that I''d rather be working on at this point. These feelings are compounded by the fact that FOX development has, as best I can tell, stalled out, and without anything new to look forward to on the FOX front there''s little motivation for me to continue working on FXRuby. So it''s time to make a clean break and call it quits. I would like to take this opportunity to thank everyone who did participate in the FXRuby community over the years. Knowing that you found my work of some value means a lot to me, and I appreciate the encouragement that I received from you along the way. I was never successful at organizing a development team around FXRuby, something which I regret, but a number of people contributed patches or third-party tools and extensions to FXRuby. If I tried to name all of those contributors, I would invariably leave someone off the list by accident, so let me just say: Thanks, you guys; you know who you are. A special thanks as well to those of you who bought the book. And of course, I owe an immense debt of gratitude to Jeroen van der Zijp, without whom there would be no FOX toolkit, and thus no FXRuby. Someone on the mailing list asked whether FOX and FXRuby are "pretty much dead." I can''t speak for Jeroen or the FOX project. As for FXRuby, however, that''s up to you. FXRuby is, and always has been, an open source project. If you are interested in hacking on FXRuby, or even taking over maintenance of the project, please feel free to fork the project on GitHub (http://github.com/lylejohnson/fxruby) and release updates as you see fit. The Wiki (http://wiki.github.com/lylejohnson/fxruby/) has a lot of information about setting up a development and build environment on Windows, Linux and Mac OS X, and if you have specific questions about the build chain I''ll do my best to help you get set up. If no one steps forward to maintain FXRuby, that?s fine too. The code has been pretty stable, if not bug-free, for quite awhile now, and it may the case that the code''s "done" anyways. If you feel that way and want to continue using FXRuby, it''s not going anywhere. If on the other hand, you have some fresh new ideas about how to move ahead, go for it! I will be cheering you on from the sidelines. In closing, thanks again for all of your support over the last ten years. I''m certainly not done with Ruby, and I''m looking forward to exploring other ways in which I can participate in the Ruby community in the future.
Lyle, 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? Ralph 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>
> What graphical platform would you recommend porting to? >Hey now. I definitely understand why you''re asking, but isn''t that a bit like asking your ex-girlfriend who you should go out with right after she breaks up with you? Thanks for all the hard work, Lyle! I''ll be watching to see what you''re up to. FXRuby has been gold for me, so I''m sure anything else you share will be worthy of attention. Kind Regards, Brian Wisti http://coolnamehere.com
On Wed, Aug 4, 2010 at 10:14 AM, Ralph Shnelvar <ralphs at dos32.com> wrote:> What graphical platform would you recommend porting to?I don''t have a recommendation as I don''t really do any desktop GUI development with Ruby anymore.
> What graphical platform would you recommend porting to? > > RalphHey Ralph, I actually have an answer now that I''ve recovered from Lyle''s announcement :-) For cross-platform GUI, FXRuby was always the best bet. Other libraries tend to work best on Unix+X11 systems. Still, there are a couple of options. Korundum''s Qt4-Ruby bindings might work. Qt4 is an excellent library, although it might feel a little heavyweight after working with FXRuby. I mention Korundum because they pushed out a fresh release of the qt4-ruby gem a few days ago. There is also a great tutorial available. * http://rubyforge.org/projects/korundum/ * http://www.darshancomputing.com/qt4-qtruby-tutorial/ WxRuby is a set of bindings for the WxWidgets tookit. Not bad, although I had issues getting it to work on Windows sometimes. Also, the most recent release appears to be from September 2009. * http://wxruby.rubyforge.org/wiki/wiki.pl If you are not worried about Windows and don''t like QT, you could check out Ruby-GNOME2. I think it is a useful set of bindings, as long as you are only concerned about writing GTK/Gnome apps. Unfortunately, Gnome development has never held my interest for long. * http://ruby-gnome2.sourceforge.jp/ Then of course, there''s the standard Tk bindings. Your applications may not be pretty to look at, but the library itself is easy to work with and it is cross-platform. Plus, ruby-tk works on most systems you happen to have Ruby and a pointy-clicky GUI desktop. Okay, it works best on OS X if you are willing to fiddle a little bit. * http://rubylearning.com/satishtalim/ruby_tk_tutorial.html Which do I prefer on the rare occasions that I write GUI projects in Ruby? Well, FXRuby. But other than that, my personal preference leans towards qt4-ruby for the shininess factor, or ruby-tk for the "getting-stuff-done-everywhere" factor. Hope this helps. Kind Regards, Brian Wisti http://coolnamehere.com
Hi everyone, First of all, I''ve been using FXRuby for the past 4 years on a large (60000 SLOC) Ruby application for my company, and it has worked nicely. Thanks are definitely owned to Lyle and Jeroen for the easy to use toolkit. However, it''s been showing its age, and the writing on the wall has been there for a while that FOX wasn''t really being developed anymore. I''m in the process of taking the KDE Bindings to the Qt GUI Toolkit for Ruby "QtRuby" and making it easier to install (which is its main drawback right now). The official qtruby4 only has a windows gem that works with the old Ruby Installer for Windows and a very hard to compile tarball for other platforms. I''m repackaging it into a gem that should be easy to install on Windows, Mac OSX, or Linux. (Hopefully... Feedback will be appreciated) You can get the code now on github at http://github.com/ryanmelt/qtbindings I''ll have a gem ready in a couple days. For those who haven''t heard of Qt... Its extremely nice, and relative similar to FOX. The learning curve to switching is not that high. There isn''t nice RDoc documentation like Lyle put together for FxRuby, but the mapping from the C documentation to ruby is very easy. Best of all, its supported by a major company, Nokia, and isn''t going anywhere. http://qt.nokia.com Ryan -----Original Message----- From: fxruby-users-bounces at rubyforge.org [mailto:fxruby-users-bounces at rubyforge.org] On Behalf Of Lyle Johnson Sent: Wednesday, August 04, 2010 10:15 AM To: fxruby-users at rubyforge.org Subject: Re: [fxruby-users] Moving On On Wed, Aug 4, 2010 at 10:14 AM, Ralph Shnelvar <ralphs at dos32.com> wrote:> What graphical platform would you recommend porting to?I don''t have a recommendation as I don''t really do any desktop GUI development with Ruby anymore. _______________________________________________ fxruby-users mailing list fxruby-users at rubyforge.org http://rubyforge.org/mailman/listinfo/fxruby-users This message and any enclosures are intended only for the addressee. Please notify the sender by email if you are not the intended recipient. If you are not the intended recipient, you may not use, copy, disclose, or distribute this message or its contents or enclosures to any other person and any such actions may be unlawful. Ball reserves the right to monitor and review all messages and enclosures sent to or from this email address.
On Wed, Aug 4, 2010 at 11:50 AM, Melton, Ryan <rmelton at ball.com> wrote:> I''m in the process of taking the KDE Bindings to the Qt GUI Toolkit for Ruby "QtRuby" and making it easier to install... >?I''m repackaging it into a gem that should be easy to install on Windows, Mac OSX, or Linux.Wow. That has to be tough work, but there are going to be a lot of people who will appreciate the end result. Good for you for stepping up to the plate on that one!
Lyle, Thanks a lot for You work. I am new guy here, but I have start looking for some GUI for our project in ruby ... I tested lot of them the best was FxRuby. And I hope that, it will be even better :) We have plan to develop this project, in this situation I hope that we can count on Your help if we will stuck on some problem. Good job. And thanks again.. Greetings from Poland :) Regards 2010/8/4 Lyle Johnson <lyle at lylejohnson.name>:> On Wed, Aug 4, 2010 at 11:50 AM, Melton, Ryan <rmelton at ball.com> wrote: > >> I''m in the process of taking the KDE Bindings to the Qt GUI Toolkit for Ruby "QtRuby" and making it easier to install... >>?I''m repackaging it into a gem that should be easy to install on Windows, Mac OSX, or Linux. > > Wow. That has to be tough work, but there are going to be a lot of > people who will appreciate the end result. Good for you for stepping > up to the plate on that one! > _______________________________________________ > fxruby-users mailing list > fxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/fxruby-users >-- Robert Mitwicki Kontakt: ? ?? jid: mitfik at jabber.org ? ?? e-mail: mitfik at gmail.com ------------------------------------------ www.partiapiratow.org.pl
Thanks for all the hard work Lyle! It has definitely helped me a great deal. Leslie
I came to fxruby via foxGUIb. With the help and kindness of Henon I learnt how to use his GUI generator. It may have been a bonus or a hinderance (depending on you''re view point) but for me I got up and running very fast using it and appreciate his efforts and yours Lyle. I know I''m not a programmer but more of a wannabe and reading my posts you''ll know it. I''m not delusional about my skills. So to you and the other more abled programmers on this list and others within the ruby community at large thanks for you''re time and efforts. All best for the future. Dave. --- On Thu, 5/8/10, Lyle Johnson <lyle at lylejohnson.name> wrote:> From: Lyle Johnson <lyle at lylejohnson.name> > Subject: [fxruby-users] Moving On > To: fxruby-users at rubyforge.org, fxruby-announce at rubyforge.org > Received: Thursday, 5 August, 2010, 2:20 AM > Cross-posted to the blog (at > http://lylejohnson.name/blog/2010/08/04/moving-on/): > > When Jamis Buck wrote last year about ceasing development > on > Capistrano, his post really struck a chord with me. If this > post > reminds you of that one, it''s because I re-read it before > sitting down > to compose this one. It was the next best thing to having > Jamis on > hand to give me a pep talk before I had to stand up and say > something > that I''ve been putting off saying for too long. As a bonus, > I could > visualize him calmly and quietly making one of those neat > little > string figures while I tried decide exactly what it was I > wanted to > say. > > It is with mixed feelings that I announce that I''m stepping > away from > FXRuby development, effective immediately. I will no longer > be > accepting bug reports, support requests, feature requests, > or general > emails related to FXRuby. I will continue to follow the > mailing list, > but I am no longer the maintainer of this project. > > When I started developing FXRuby back in late 2000, it was > a lot of > fun for me. I was still new to Ruby (most of us were, back > then) and > Ruby was in need of a good GUI toolkit, so working on > FXRuby provided > me with not only a good way to learn the ins and outs of > the language, > but also to get really plugged into the community. In > recent years, > however, working on FXRuby has become a chore. I''m a decade > older, at > a different place in my life and career, and there are > frankly just > too many other things that I''d rather be working on at this > point. > These feelings are compounded by the fact that FOX > development has, as > best I can tell, stalled out, and without anything new to > look forward > to on the FOX front there''s little motivation for me to > continue > working on FXRuby. So it''s time to make a clean break and > call it > quits. > > I would like to take this opportunity to thank everyone who > did > participate in the FXRuby community over the years. Knowing > that you > found my work of some value means a lot to me, and I > appreciate the > encouragement that I received from you along the way. I was > never > successful at organizing a development team around FXRuby, > something > which I regret, but a number of people contributed patches > or > third-party tools and extensions to FXRuby. If I tried to > name all of > those contributors, I would invariably leave someone off > the list by > accident, so let me just say: Thanks, you guys; you know > who you are. > A special thanks as well to those of you who bought the > book. And of > course, I owe an immense debt of gratitude to Jeroen van > der Zijp, > without whom there would be no FOX toolkit, and thus no > FXRuby. > > Someone on the mailing list asked whether FOX and FXRuby > are "pretty > much dead." I can''t speak for Jeroen or the FOX project. As > for > FXRuby, however, that''s up to you. FXRuby is, and always > has been, an > open source project. If you are interested in hacking on > FXRuby, or > even taking over maintenance of the project, please feel > free to fork > the project on GitHub (http://github.com/lylejohnson/fxruby) and > release updates as you see fit. The Wiki > (http://wiki.github.com/lylejohnson/fxruby/) has a lot > of information > about setting up a development and build environment on > Windows, Linux > and Mac OS X, and if you have specific questions about the > build chain > I''ll do my best to help you get set up. > > If no one steps forward to maintain FXRuby, that?s fine > too. The code > has been pretty stable, if not bug-free, for quite awhile > now, and it > may the case that the code''s "done" anyways. If you feel > that way and > want to continue using FXRuby, it''s not going anywhere. If > on the > other hand, you have some fresh new ideas about how to move > ahead, go > for it! I will be cheering you on from the sidelines. > > In closing, thanks again for all of your support over the > last ten > years. I''m certainly not done with Ruby, and I''m looking > forward to > exploring other ways in which I can participate in the Ruby > community > in the future. > _______________________________________________ > fxruby-users mailing list > fxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/fxruby-users >
may I add to the list the program Shoes. I used it before settling on fxruby. Shoes by _whytheluckystiff has been taken over by a community of programmers who loved it''d creator and the program so much. I don''t know why _why shutdown shoes but the community has recovered. I have had the intention of revisiting it. rgds, Dave. --- On Thu, 5/8/10, Brian Wisti <brian.wisti at gmail.com> wrote:> From: Brian Wisti <brian.wisti at gmail.com> > Subject: Re: [fxruby-users] Moving On > To: "Ralph Shnelvar" <ralphs at dos32.com>, fxruby-users at rubyforge.org > Received: Thursday, 5 August, 2010, 4:38 AM > > What graphical platform would > you recommend porting to? > > > > Ralph > > Hey Ralph, I actually have an answer now that I''ve > recovered from > Lyle''s announcement :-) > > For cross-platform GUI, FXRuby was always the best bet. > Other > libraries tend to work best on Unix+X11 systems. Still, > there are a > couple of options. > > Korundum''s Qt4-Ruby bindings might work. Qt4 is an > excellent library, > although it might feel a little heavyweight after working > with FXRuby. > I mention Korundum because they pushed out a fresh release > of the > qt4-ruby gem a few days ago. There is also a great tutorial > available. > > * http://rubyforge.org/projects/korundum/ > * http://www.darshancomputing.com/qt4-qtruby-tutorial/ > > WxRuby is a set of bindings for the WxWidgets tookit. Not > bad, > although I had issues getting it to work on Windows > sometimes. Also, > the most recent release appears to be from September 2009. > > * http://wxruby.rubyforge.org/wiki/wiki.pl > > If you are not worried about Windows and don''t like QT, you > could > check out Ruby-GNOME2. I think it is a useful set of > bindings, as long > as you are only concerned about writing GTK/Gnome apps. > Unfortunately, > Gnome development has never held my interest for long. > > * http://ruby-gnome2.sourceforge.jp/ > > Then of course, there''s the standard Tk bindings. Your > applications > may not be pretty to look at, but the library itself is > easy to work > with and it is cross-platform. Plus, ruby-tk works on most > systems you > happen to have Ruby and a pointy-clicky GUI desktop. Okay, > it works > best on OS X if you are willing to fiddle a little bit. > > * http://rubylearning.com/satishtalim/ruby_tk_tutorial.html > > Which do I prefer on the rare occasions that I write GUI > projects in > Ruby? Well, FXRuby. But other than that, my personal > preference leans > towards qt4-ruby for the shininess factor, or ruby-tk for > the > "getting-stuff-done-everywhere" factor. > > Hope this helps. > > Kind Regards, > > Brian Wisti > http://coolnamehere.com > _______________________________________________ > fxruby-users mailing list > fxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/fxruby-users >
Yeah, I''d like to mention Shoes too, but although it''s a very nice and simple toolkit, I don''t think it''s quite powerful or even ready. It''s perfect for your own tiny freetime projects, but I won''t recommend it for anything bigger. And really, why look for anything else? As Lyle said, FXRuby isn''t going anywhere, it''s going to work just as it worked for years, it just will not be developed (and it wasn''t, anyway). -- Matma Rex - http://matma-rex.prv.pl/
Lyle, Thanks for all the support (years ago) ... and I wish you good luck and much fun with whatever you are going to take on ;) Cheers, -- henon On Wed, Aug 4, 2010 at 4:20 PM, Lyle Johnson <lyle at lylejohnson.name> wrote:> Cross-posted to the blog (at > http://lylejohnson.name/blog/2010/08/04/moving-on/): > > When Jamis Buck wrote last year about ceasing development on > Capistrano, his post really struck a chord with me. If this post > reminds you of that one, it''s because I re-read it before sitting down > to compose this one. It was the next best thing to having Jamis on > hand to give me a pep talk before I had to stand up and say something > that I''ve been putting off saying for too long. As a bonus, I could > visualize him calmly and quietly making one of those neat little > string figures while I tried decide exactly what it was I wanted to > say. > > It is with mixed feelings that I announce that I''m stepping away from > FXRuby development, effective immediately. I will no longer be > accepting bug reports, support requests, feature requests, or general > emails related to FXRuby. I will continue to follow the mailing list, > but I am no longer the maintainer of this project. > > When I started developing FXRuby back in late 2000, it was a lot of > fun for me. I was still new to Ruby (most of us were, back then) and > Ruby was in need of a good GUI toolkit, so working on FXRuby provided > me with not only a good way to learn the ins and outs of the language, > but also to get really plugged into the community. In recent years, > however, working on FXRuby has become a chore. I''m a decade older, at > a different place in my life and career, and there are frankly just > too many other things that I''d rather be working on at this point. > These feelings are compounded by the fact that FOX development has, as > best I can tell, stalled out, and without anything new to look forward > to on the FOX front there''s little motivation for me to continue > working on FXRuby. So it''s time to make a clean break and call it > quits. > > I would like to take this opportunity to thank everyone who did > participate in the FXRuby community over the years. Knowing that you > found my work of some value means a lot to me, and I appreciate the > encouragement that I received from you along the way. I was never > successful at organizing a development team around FXRuby, something > which I regret, but a number of people contributed patches or > third-party tools and extensions to FXRuby. If I tried to name all of > those contributors, I would invariably leave someone off the list by > accident, so let me just say: Thanks, you guys; you know who you are. > A special thanks as well to those of you who bought the book. And of > course, I owe an immense debt of gratitude to Jeroen van der Zijp, > without whom there would be no FOX toolkit, and thus no FXRuby. > > Someone on the mailing list asked whether FOX and FXRuby are "pretty > much dead." I can''t speak for Jeroen or the FOX project. As for > FXRuby, however, that''s up to you. FXRuby is, and always has been, an > open source project. If you are interested in hacking on FXRuby, or > even taking over maintenance of the project, please feel free to fork > the project on GitHub (http://github.com/lylejohnson/fxruby) and > release updates as you see fit. The Wiki > (http://wiki.github.com/lylejohnson/fxruby/) has a lot of information > about setting up a development and build environment on Windows, Linux > and Mac OS X, and if you have specific questions about the build chain > I''ll do my best to help you get set up. > > If no one steps forward to maintain FXRuby, that?s fine too. The code > has been pretty stable, if not bug-free, for quite awhile now, and it > may the case that the code''s "done" anyways. If you feel that way and > want to continue using FXRuby, it''s not going anywhere. If on the > other hand, you have some fresh new ideas about how to move ahead, go > for it! I will be cheering you on from the sidelines. > > In closing, thanks again for all of your support over the last ten > years. I''m certainly not done with Ruby, and I''m looking forward to > exploring other ways in which I can participate in the Ruby community > in the future. > _______________________________________________ > fxruby-users mailing list > fxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/fxruby-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/fxruby-users/attachments/20100805/914d73b5/attachment.html>
Hi Lyle All good things eventually come to an end. Feeling sad for fxruby. My acquaintence with fx-ruby became when I was facing a rather critical situation for me as well the company I am working for. A big project was coming in on Arm9 based handheld , kinda embedded arm-linux, and we had very less time for making a good show of our competence. I was keen on freepascal for Arm and betting on it when the company wanted an immediate demo and proto-type of the application on the Arm-linux board. I did shelve freepascal and jumped into ruby /fox/fxruby cross compilation and lo! I could whip up a decent App with mysql connectivity to a remote server , almost within a week. We got the plum order and I get to retain my job! Well after the initial euphoria, the management decided to go the QT way, since Nokia was backing it now. So, despite my objections, ruby and fx are under the wraps since and there are the C++ cats working on Qt-embedded-opensource-linux-4.5.2. Meanwhile I was still trying to duplicate what the Qt guys were trying, but my handycap being that Qt-embedded runs on frame buffer without X. Eventually I believe some one might embark on Foxlib with xserver functionality over frame buffer and get fxruby to work on the same. Thanks to you Lyle once again. Warm regards Nataraj On Wed, Aug 4, 2010 at 10:08 PM, Brian Wisti <brian.wisti at gmail.com> wrote:> > What graphical platform would you recommend porting to? > > > > Ralph > > Hey Ralph, I actually have an answer now that I''ve recovered from > Lyle''s announcement :-) > > For cross-platform GUI, FXRuby was always the best bet. Other > libraries tend to work best on Unix+X11 systems. Still, there are a > couple of options. > > Korundum''s Qt4-Ruby bindings might work. Qt4 is an excellent library, > although it might feel a little heavyweight after working with FXRuby. > I mention Korundum because they pushed out a fresh release of the > qt4-ruby gem a few days ago. There is also a great tutorial available. > > * http://rubyforge.org/projects/korundum/ > * http://www.darshancomputing.com/qt4-qtruby-tutorial/ > > WxRuby is a set of bindings for the WxWidgets tookit. Not bad, > although I had issues getting it to work on Windows sometimes. Also, > the most recent release appears to be from September 2009. > > * http://wxruby.rubyforge.org/wiki/wiki.pl > > If you are not worried about Windows and don''t like QT, you could > check out Ruby-GNOME2. I think it is a useful set of bindings, as long > as you are only concerned about writing GTK/Gnome apps. Unfortunately, > Gnome development has never held my interest for long. > > * http://ruby-gnome2.sourceforge.jp/ > > Then of course, there''s the standard Tk bindings. Your applications > may not be pretty to look at, but the library itself is easy to work > with and it is cross-platform. Plus, ruby-tk works on most systems you > happen to have Ruby and a pointy-clicky GUI desktop. Okay, it works > best on OS X if you are willing to fiddle a little bit. > > * http://rubylearning.com/satishtalim/ruby_tk_tutorial.html > > Which do I prefer on the rare occasions that I write GUI projects in > Ruby? Well, FXRuby. But other than that, my personal preference leans > towards qt4-ruby for the shininess factor, or ruby-tk for the > "getting-stuff-done-everywhere" factor. > > Hope this helps. > > Kind Regards, > > Brian Wisti > http://coolnamehere.com > _______________________________________________ > fxruby-users mailing list > fxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/fxruby-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/fxruby-users/attachments/20100805/03e2853f/attachment-0001.html>
The qtbindings gem is now available: gem install qtbindings Should be easy to install on windows with the binary windows gem. Please see the README on http://github.com/ryanmelt/qtbindings before attempting to install on Linux / Mac OSX. It is still easy, but you have to have all the prereqs. Enjoy! Ryan -----Original Message----- From: fxruby-users-bounces at rubyforge.org [mailto:fxruby-users-bounces at rubyforge.org] On Behalf Of Melton, Ryan Sent: Wednesday, August 04, 2010 10:51 AM To: fxruby-users at rubyforge.org Subject: Re: [fxruby-users] Moving On Hi everyone, First of all, I''ve been using FXRuby for the past 4 years on a large (60000 SLOC) Ruby application for my company, and it has worked nicely. Thanks are definitely owned to Lyle and Jeroen for the easy to use toolkit. However, it''s been showing its age, and the writing on the wall has been there for a while that FOX wasn''t really being developed anymore. I''m in the process of taking the KDE Bindings to the Qt GUI Toolkit for Ruby "QtRuby" and making it easier to install (which is its main drawback right now). The official qtruby4 only has a windows gem that works with the old Ruby Installer for Windows and a very hard to compile tarball for other platforms. I''m repackaging it into a gem that should be easy to install on Windows, Mac OSX, or Linux. (Hopefully... Feedback will be appreciated) You can get the code now on github at http://github.com/ryanmelt/qtbindings I''ll have a gem ready in a couple days. For those who haven''t heard of Qt... Its extremely nice, and relative similar to FOX. The learning curve to switching is not that high. There isn''t nice RDoc documentation like Lyle put together for FxRuby, but the mapping from the C documentation to ruby is very easy. Best of all, its supported by a major company, Nokia, and isn''t going anywhere. http://qt.nokia.com Ryan -----Original Message----- From: fxruby-users-bounces at rubyforge.org [mailto:fxruby-users-bounces at rubyforge.org] On Behalf Of Lyle Johnson Sent: Wednesday, August 04, 2010 10:15 AM To: fxruby-users at rubyforge.org Subject: Re: [fxruby-users] Moving On On Wed, Aug 4, 2010 at 10:14 AM, Ralph Shnelvar <ralphs at dos32.com> wrote:> What graphical platform would you recommend porting to?I don''t have a recommendation as I don''t really do any desktop GUI development with Ruby anymore. _______________________________________________ fxruby-users mailing list fxruby-users at rubyforge.org http://rubyforge.org/mailman/listinfo/fxruby-users This message and any enclosures are intended only for the addressee. Please notify the sender by email if you are not the intended recipient. If you are not the intended recipient, you may not use, copy, disclose, or distribute this message or its contents or enclosures to any other person and any such actions may be unlawful. Ball reserves the right to monitor and review all messages and enclosures sent to or from this email address. _______________________________________________ fxruby-users mailing list fxruby-users at rubyforge.org http://rubyforge.org/mailman/listinfo/fxruby-users This message and any enclosures are intended only for the addressee. Please notify the sender by email if you are not the intended recipient. If you are not the intended recipient, you may not use, copy, disclose, or distribute this message or its contents or enclosures to any other person and any such actions may be unlawful. Ball reserves the right to monitor and review all messages and enclosures sent to or from this email address.
Yeah! And then replace all occurrences of FX with QT in your ruby sources and you are done :-) (och and include "qt" instead include "fox16"...) Bj?rn 2010/8/6 Melton, Ryan <rmelton at ball.com>> The qtbindings gem is now available: > > gem install qtbindings > > Should be easy to install on windows with the binary windows gem. > > Please see the README on http://github.com/ryanmelt/qtbindings before > attempting to install on Linux / Mac OSX. It is still easy, but you have to > have all the prereqs. > > Enjoy! > Ryan > > > -----Original Message----- > From: fxruby-users-bounces at rubyforge.org [mailto: > fxruby-users-bounces at rubyforge.org] On Behalf Of Melton, Ryan > Sent: Wednesday, August 04, 2010 10:51 AM > To: fxruby-users at rubyforge.org > Subject: Re: [fxruby-users] Moving On > > Hi everyone, > > First of all, I''ve been using FXRuby for the past 4 years on a large (60000 > SLOC) Ruby application for my company, and it has worked nicely. Thanks are > definitely owned to Lyle and Jeroen for the easy to use toolkit. > > However, it''s been showing its age, and the writing on the wall has been > there for a while that FOX wasn''t really being developed anymore. > > I''m in the process of taking the KDE Bindings to the Qt GUI Toolkit for > Ruby "QtRuby" and making it easier to install (which is its main drawback > right now). The official qtruby4 only has a windows gem that works with the > old Ruby Installer for Windows and a very hard to compile tarball for other > platforms. I''m repackaging it into a gem that should be easy to install on > Windows, Mac OSX, or Linux. (Hopefully... Feedback will be appreciated) > > You can get the code now on github at > http://github.com/ryanmelt/qtbindings > > I''ll have a gem ready in a couple days. > > For those who haven''t heard of Qt... Its extremely nice, and relative > similar to FOX. The learning curve to switching is not that high. There > isn''t nice RDoc documentation like Lyle put together for FxRuby, but the > mapping from the C documentation to ruby is very easy. Best of all, its > supported by a major company, Nokia, and isn''t going anywhere. > http://qt.nokia.com > > Ryan > > -----Original Message----- > From: fxruby-users-bounces at rubyforge.org [mailto: > fxruby-users-bounces at rubyforge.org] On Behalf Of Lyle Johnson > Sent: Wednesday, August 04, 2010 10:15 AM > To: fxruby-users at rubyforge.org > Subject: Re: [fxruby-users] Moving On > > On Wed, Aug 4, 2010 at 10:14 AM, Ralph Shnelvar <ralphs at dos32.com> wrote: > > > What graphical platform would you recommend porting to? > > I don''t have a recommendation as I don''t really do any desktop GUI > development with Ruby anymore. > _______________________________________________ > fxruby-users mailing list > fxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/fxruby-users > > > > This message and any enclosures are intended only for the addressee. > Please > notify the sender by email if you are not the intended recipient. If you > are > not the intended recipient, you may not use, copy, disclose, or distribute > this > message or its contents or enclosures to any other person and any such > actions > may be unlawful. Ball reserves the right to monitor and review all > messages > and enclosures sent to or from this email address. > _______________________________________________ > fxruby-users mailing list > fxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/fxruby-users > > > > This message and any enclosures are intended only for the addressee. > Please > notify the sender by email if you are not the intended recipient. If you > are > not the intended recipient, you may not use, copy, disclose, or distribute > this > message or its contents or enclosures to any other person and any such > actions > may be unlawful. Ball reserves the right to monitor and review all > messages > and enclosures sent to or from this email address. > _______________________________________________ > fxruby-users mailing list > fxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/fxruby-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/fxruby-users/attachments/20100807/462c109a/attachment.html>
Hi Ryan,Bj?rn I am on qt-embedded-linux-opensource-4.6.2, working on linux framebuffer. My toolchain is arm-linux-uclibcgnueabi-. Working on a Arm9 CPU based handheld with OS linux + uclibc for Arm. I used Buildroot ( http://buildroot.org/) for building the filesystem with Qt-embedded and ruby. regards Nataraj 2010/8/7 Bj?rn Bergqvist <bjorn.bergqvist at gmail.com>> Yeah! > And then replace all occurrences of FX with QT in your ruby sources and you > are done :-) > (och and include "qt" instead include "fox16"...) > > Bj?rn > > 2010/8/6 Melton, Ryan <rmelton at ball.com> > > The qtbindings gem is now available: >> >> gem install qtbindings >> >> Should be easy to install on windows with the binary windows gem. >> >> Please see the README on http://github.com/ryanmelt/qtbindings before >> attempting to install on Linux / Mac OSX. It is still easy, but you have to >> have all the prereqs. >> >> Enjoy! >> Ryan >> >> >> -----Original Message----- >> From: fxruby-users-bounces at rubyforge.org [mailto: >> fxruby-users-bounces at rubyforge.org] On Behalf Of Melton, Ryan >> Sent: Wednesday, August 04, 2010 10:51 AM >> To: fxruby-users at rubyforge.org >> Subject: Re: [fxruby-users] Moving On >> >> Hi everyone, >> >> First of all, I''ve been using FXRuby for the past 4 years on a large >> (60000 SLOC) Ruby application for my company, and it has worked nicely. >> Thanks are definitely owned to Lyle and Jeroen for the easy to use toolkit. >> >> However, it''s been showing its age, and the writing on the wall has been >> there for a while that FOX wasn''t really being developed anymore. >> >> I''m in the process of taking the KDE Bindings to the Qt GUI Toolkit for >> Ruby "QtRuby" and making it easier to install (which is its main drawback >> right now). The official qtruby4 only has a windows gem that works with the >> old Ruby Installer for Windows and a very hard to compile tarball for other >> platforms. I''m repackaging it into a gem that should be easy to install on >> Windows, Mac OSX, or Linux. (Hopefully... Feedback will be appreciated) >> >> You can get the code now on github at >> http://github.com/ryanmelt/qtbindings >> >> I''ll have a gem ready in a couple days. >> >> For those who haven''t heard of Qt... Its extremely nice, and relative >> similar to FOX. The learning curve to switching is not that high. There >> isn''t nice RDoc documentation like Lyle put together for FxRuby, but the >> mapping from the C documentation to ruby is very easy. Best of all, its >> supported by a major company, Nokia, and isn''t going anywhere. >> http://qt.nokia.com >> >> Ryan >> >> -----Original Message----- >> From: fxruby-users-bounces at rubyforge.org [mailto: >> fxruby-users-bounces at rubyforge.org] On Behalf Of Lyle Johnson >> Sent: Wednesday, August 04, 2010 10:15 AM >> To: fxruby-users at rubyforge.org >> Subject: Re: [fxruby-users] Moving On >> >> On Wed, Aug 4, 2010 at 10:14 AM, Ralph Shnelvar <ralphs at dos32.com> wrote: >> >> > What graphical platform would you recommend porting to? >> >> I don''t have a recommendation as I don''t really do any desktop GUI >> development with Ruby anymore. >> _______________________________________________ >> fxruby-users mailing list >> fxruby-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/fxruby-users >> >> >> >> This message and any enclosures are intended only for the addressee. >> Please >> notify the sender by email if you are not the intended recipient. If you >> are >> not the intended recipient, you may not use, copy, disclose, or distribute >> this >> message or its contents or enclosures to any other person and any such >> actions >> may be unlawful. Ball reserves the right to monitor and review all >> messages >> and enclosures sent to or from this email address. >> _______________________________________________ >> fxruby-users mailing list >> fxruby-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/fxruby-users >> >> >> >> This message and any enclosures are intended only for the addressee. >> Please >> notify the sender by email if you are not the intended recipient. If you >> are >> not the intended recipient, you may not use, copy, disclose, or distribute >> this >> message or its contents or enclosures to any other person and any such >> actions >> may be unlawful. Ball reserves the right to monitor and review all >> messages >> and enclosures sent to or from this email address. >> _______________________________________________ >> fxruby-users mailing list >> fxruby-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/fxruby-users >> > > > _______________________________________________ > fxruby-users mailing list > fxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/fxruby-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/fxruby-users/attachments/20100809/7cc2e505/attachment-0001.html>