On Thu, Sep 16, 2010 at 1:35 AM, Mohammed Rashad <mohammedrashadkm at gmail.com> wrote:> I am going to start a project in C++ or Ruby (not yet decided). First > I choose Qt for gui but latter I am impressed with FOX and also FXRuby. > I had contributed to some opensource projects like GRASS GIS and created two > projects on sourceforge. > From you blog I heard that you signed off from FOX and FXRuby and also FOX > is dead. I would like to maintain FXRuby and FXpy bindings.Great!> What should I do to be the maintainer and coordinator of FOX bindings for > python and Ruby.? Can you give me spark or start for becoming the maintainer > of FOX bindings?The first thing I''d do is reach out to the community (via the foxgui-users and fxruby-users mailing lists) to see if anyone else wanted to help. This was a mistake I made with FXRuby, not doing more to involve other potential contributors. Maintaining a library like FXRuby is a lot of work for one person to do on their own. Around the same time, though, I''d start by getting to know how the code works. I would set up my build and development environment, and make sure that I could build FXRuby from source code. After that I''d need to become pretty intimately familiar with FOX, C++, Ruby (and its extension API), and SWIG, if I wasn''t already. After I''d done those things, or maybe even sooner, I''d fork the project on FXRuby and start looking for little bugs to fix, or features to add. I would continue to reach out to the community, to see if anyone else wanted to pitch in and help. Eventually, I''d work my way up to making a new release of the code. Community involvement can be especially helpful here, in terms of getting the ports done. For example, if I worked primarily on Linux, I''d see if someone else was willing to make sure it''s working properly on Windows or OS X. Over time, if I was successful, the world would come to recognize my fork of FXRuby as the "good" one, and that''s the one that they''d all use.> Is FOX c++ gui better than Qt gui. ?I have never used Qt and am therefore unqualified to answer this question. Hope this helps, Lyle
On Thu, Sep 16, 2010 at 6:49 AM, Lyle Johnson <lyle at lylejohnson.name> wrote:> After I''d done those things, or maybe even sooner, I''d fork the > project on FXRuby and start looking for little bugs to fix, or > features to add.Ah, a typo. That of course should read, "I''d fork the project on GitHub...".
Great news! Bj?rn 2010/9/16 Lyle Johnson <lyle at lylejohnson.name>> On Thu, Sep 16, 2010 at 1:35 AM, Mohammed Rashad > <mohammedrashadkm at gmail.com> wrote: > > > I am going to start a project in C++ or Ruby (not yet decided). First > > I choose Qt for gui but latter I am impressed with FOX and also FXRuby. > > I had contributed to some opensource projects like GRASS GIS and created > two > > projects on sourceforge. > > From you blog I heard that you signed off from FOX and FXRuby and also > FOX > > is dead. I would like to maintain FXRuby and FXpy bindings. > > Great! > > > What should I do to be the maintainer and coordinator of FOX bindings for > > python and Ruby.? Can you give me spark or start for becoming the > maintainer > > of FOX bindings? > > The first thing I''d do is reach out to the community (via the > foxgui-users and fxruby-users mailing lists) to see if anyone else > wanted to help. This was a mistake I made with FXRuby, not doing more > to involve other potential contributors. Maintaining a library like > FXRuby is a lot of work for one person to do on their own. > > Around the same time, though, I''d start by getting to know how the > code works. I would set up my build and development environment, and > make sure that I could build FXRuby from source code. After that I''d > need to become pretty intimately familiar with FOX, C++, Ruby (and its > extension API), and SWIG, if I wasn''t already. > > After I''d done those things, or maybe even sooner, I''d fork the > project on FXRuby and start looking for little bugs to fix, or > features to add. I would continue to reach out to the community, to > see if anyone else wanted to pitch in and help. Eventually, I''d work > my way up to making a new release of the code. Community involvement > can be especially helpful here, in terms of getting the ports done. > For example, if I worked primarily on Linux, I''d see if someone else > was willing to make sure it''s working properly on Windows or OS X. > > Over time, if I was successful, the world would come to recognize my > fork of FXRuby as the "good" one, and that''s the one that they''d all > use. > > > Is FOX c++ gui better than Qt gui. ? > > I have never used Qt and am therefore unqualified to answer this question. > > Hope this helps, > > Lyle > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > Foxgui-users mailing list > Foxgui-users at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/foxgui-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/fxruby-users/attachments/20100916/8331cea6/attachment.html>
On Sep 16, 2010, at 7:05 AM, Mohammed Rashad wrote:> Okand Thanks for your valuable reply. From where can I get right access? > I am ready to maintain ruby and python bindings i am good with swig too :)If you let me know your SourceForge user name, I''ll be glad to add you as a developer on FXPy. And of course, since you''re going to be forking FXRuby on GitHub, you don''t need anything from me on that.
On Sep 16, 2010, at 8:06 AM, Mohammed Rashad wrote:> my sourceforge id is rashadkmOK, I''ve just added you as a developer on the FXPy project at SourceForge.> Why id not needed for FXRuby? Dont know that what I am asking.. :)FXRuby is hosted on GitHub (http://github.com/), not SourceForge. You will need a GitHub account when you get ready to create your fork of FXRuby, but you do not need my permission or assistance to do that. If you are unfamiliar with how Git and GitHub work, you should start at this page: http://help.github.com/ and then when you''re ready to fork FXRuby, to start working on your fork, check the info on this page: http://help.github.com/forking/ Hope this helps, Lyle
>> The first thing I''d do is reach out to the community (via the >> foxgui-users and fxruby-users mailing lists) to see if anyone else >> wanted to help.I want to help :) and I am also intresting in developing FXRuby especial that our company will use it in our main application.>> > Is FOX c++ gui better than Qt gui. ?of course is better ;)>> "I''d fork the project on GitHub...".http://github.com/mitfik/fxruby this is my fork Regards. - Robert Mitwicki Kontakt: ? ?? jid: mitfik at jabber.org ? ?? e-mail: mitfik at gmail.com ------------------------------------------ www.partiapiratow.blog.pl
On Sep 16, 2010, at 8:24 AM, Mohammed Rashad wrote:> thanks a lot for you great help. Bunch of thanks :) > Expecting a long lasting relationship from you...Mohammed, I''m glad that you are enthusiastic about these project(s), but in the interest of setting expectations appropriately, let me remind you that as I said on my blog [1], and on the mailing lists, I personally will no longer be accepting bug reports, support requests, feature requests, or general emails related to FXRuby. I have made an exception in this case, but I''m not going to be answering any more personal emails on the subject. I *will* continue to follow the mailing lists for FOX and FXRuby, and if you post questions there I might respond---or I might not. Cheers, and best of luck, Lyle [1] http://lylejohnson.name/blog/2010/08/04/moving-on/
On Sep 16, 2010, at 8:30 AM, Robert Mitwicki wrote:>>> "I''d fork the project on GitHub...". > > http://github.com/mitfik/fxruby this is my forkThis is great! I''m looking forward to seeing how things go for you guys.
Thursday, September 16, 2010, 8:30:43 AM, you wrote: LJ> On Sep 16, 2010, at 8:30 AM, Robert Mitwicki wrote:>>>> "I''d fork the project on GitHub...".>> http://github.com/mitfik/fxruby this is my forkLJ> This is great! I''m looking forward to seeing how things go for you guys. LJ> _______________________________________________ Lyle and all: I am interested in helping but I am very much of a novice when it comes to many of the tools that are used. I am, though, a really good C++ programmer. I am clueless, for instance, on the weltanschauung of gitHub, forking, etc. I am clueless, at this time, of how to build FXRuby on a Windows platform. Would you guys be willing to bring me up to speed on these tools? - - - - - Nonetheless, I''m a bit confused about the "age" of FXRuby (which seems to be remarkably stable). Isn''t it the case that FXRuby is "old technology"? Is this the way to go? Let me be clear. I don''t have an opinion about this, I simply want to hear other people''s opinions. Ralph -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/fxruby-users/attachments/20100916/4426875f/attachment.html>
On Sep 16, 2010, at 1:13 PM, Ralph Shnelvar wrote:> I am interested in helping but I am very much of a novice when it comes to many of the tools that are used. I am, though, a really good C++ programmer. > > I am clueless, for instance, on the weltanschauung of gitHub, forking, etc.Start here: http://help.github.com/ and then ask questions on the mailing list (or in the #github IRC channel, or whatever). Lots of folks in the Ruby community are using Git and GitHub.> I am clueless, at this time, of how to build FXRuby on a Windows platform.Start here: http://github.com/lylejohnson/fxruby/wiki/Setting-Up-a-Windows-Build-Environment and then ask questions. ;)> Nonetheless, I''m a bit confused about the "age" of FXRuby (which seems to be remarkably stable). > > Isn''t it the case that FXRuby is "old technology"? Is this the way to go?I''m not 100% sure that I understand the question, but I''ll try to answer the question I think you''re asking. ;) FOX''s underlying architecture, in terms of how widgets communicate via message passing, is an incredibly elegant way of doing things. Jeroen''s design for this drew in part from his experiences with the NeXT operating system, and its NeXTStep UI. And of course, NeXT was also the basis for Apple''s Cocoa framework, so there''s a lot of similarity there. So in that sense, FOX is very much current. Likewise for the GUI update mechanism, data targets, and other neat things. I''ve learned a lot about software design by reading through the FOX source code, and it can be an elegant platform for building GUI applications. On the other hand... you have issues like look and feel. FOX looks vaguely like a Windows 95-era user interface, which is to say, pretty darned aged. There is a discussion taking place on the FOX mailing list as we speak, about whether FOX should incorporate theming so that FOX-based GUI applications could be made to look more like platform-native apps (especially on OS X). I can tell you as a FOX "veteran" that if you''re waiting for theming in FOX, you ought not hold your breath. So if having a native "look and feel" for your application is an issue, you should be looking elsewhere. Likewise for things like strong i18n support, or whatever. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/fxruby-users/attachments/20100916/450e9eed/attachment-0001.html>
Lyle, You answered the question I intended to ask. Thanks! In terms of i18n support, I thought Ruby''s/Rails i18n support was pretty good. I just don''t remember if i18n is a rails thing or a "native" ruby thing. Ralph Thursday, September 16, 2010, 1:48:10 PM, you wrote: On Sep 16, 2010, at 1:13 PM, Ralph Shnelvar wrote: I am interested in helping but I am very much of a novice when it comes to many of the tools that are used. I am, though, a really good C++ programmer. I am clueless, for instance, on the weltanschauung of gitHub, forking, etc. Start here: http://help.github.com/ and then ask questions on the mailing list (or in the #github IRC channel, or whatever). Lots of folks in the Ruby community are using Git and GitHub. I am clueless, at this time, of how to build FXRuby on a Windows platform. Start here: http://github.com/lylejohnson/fxruby/wiki/Setting-Up-a-Windows-Build-Environment and then ask questions. ;) Nonetheless, I''m a bit confused about the "age" of FXRuby (which seems to be remarkably stable). Isn''t it the case that FXRuby is "old technology"? Is this the way to go? I''m not 100% sure that I understand the question, but I''ll try to answer the question I think you''re asking. ;) FOX''s underlying architecture, in terms of how widgets communicate via message passing, is an incredibly elegant way of doing things. Jeroen''s design for this drew in part from his experiences with the NeXT operating system, and its NeXTStep UI. And of course, NeXT was also the basis for Apple''s Cocoa framework, so there''s a lot of similarity there. So in that sense, FOX is very much current. Likewise for the GUI update mechanism, data targets, and other neat things. I''ve learned a lot about software design by reading through the FOX source code, and it can be an elegant platform for building GUI applications. On the other hand... you have issues like look and feel. FOX looks vaguely like a Windows 95-era user interface, which is to say, pretty darned aged. There is a discussion taking place on the FOX mailing list as we speak, about whether FOX should incorporate theming so that FOX-based GUI applications could be made to look more like platform-native apps (especially on OS X). I can tell you as a FOX "veteran" that if you''re waiting for theming in FOX, you ought not hold your breath. So if having a native "look and feel" for your application is an issue, you should be looking elsewhere. Likewise for things like strong i18n support, or whatever. -- Best regards, Ralph mailto:ralphs at dos32.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/fxruby-users/attachments/20100916/7dbf2fe8/attachment.html>
Hi Robert Could you substantiate that? I mean Fox being better than Qt-4.6.x? Is it the design? Since Qt is with Nokia ,lots of takers for Qt. Even my own boss made me switch to Qt for the Nokia patronage. Warm regards Nataraj On Thu, Sep 16, 2010 at 7:00 PM, Robert Mitwicki <mitfik at gmail.com> wrote:> >> The first thing I''d do is reach out to the community (via the > >> foxgui-users and fxruby-users mailing lists) to see if anyone else > >> wanted to help. > > I want to help :) and I am also intresting in developing FXRuby > especial that our company will use it in our main application. > > > >> > Is FOX c++ gui better than Qt gui. ? > > of course is better ;) > > >> "I''d fork the project on GitHub...". > > http://github.com/mitfik/fxruby this is my fork > > Regards. > > - > Robert Mitwicki > Kontakt: > jid: mitfik at jabber.org > e-mail: mitfik at gmail.com > ------------------------------------------ > > www.partiapiratow.blog.pl > _______________________________________________ > 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/20100917/6f133d64/attachment.html>
Hi Lyle I have mentioned this already a few times :-- I need to get Fox and fxruby to work on Framebuffer devices without X, just as Qt-4.6.3 does for me. That is, on my Arm9 based handheld based on Linux and uclibc. I am sure I can also get into a bit of coding myself if somebody can give me a few pointers in this direction. I was in love with Ruby and fxruby. The romance was stifled by the prevailing bias towards established tools. regards Nataraj On Fri, Sep 17, 2010 at 1:18 AM, Lyle Johnson <lyle at lylejohnson.name> wrote:> > On Sep 16, 2010, at 1:13 PM, Ralph Shnelvar wrote: > > I am interested in helping but I am very much of a novice when it comes to > many of the tools that are used. I am, though, a really good C++ > programmer. > > I am clueless, for instance, on the weltanschauung of gitHub, forking, etc. > > > Start here: > > http://help.github.com/ > > and then ask questions on the mailing list (or in the #github IRC channel, > or whatever). Lots of folks in the Ruby community are using Git and GitHub. > > I am clueless, at this time, of how to build FXRuby on a Windows platform. > > > Start here: > > > http://github.com/lylejohnson/fxruby/wiki/Setting-Up-a-Windows-Build-Environment > > and then ask questions. ;) > > Nonetheless, I''m a bit confused about the "age" of FXRuby (which seems to > be remarkably stable). > > Isn''t it the case that FXRuby is "old technology"? Is this the way to go? > > > I''m not 100% sure that I understand the question, but I''ll try to answer > the question I think you''re asking. ;) > > FOX''s underlying architecture, in terms of how widgets communicate via > message passing, is an incredibly elegant way of doing things. Jeroen''s > design for this drew in part from his experiences with the NeXT operating > system, and its NeXTStep UI. And of course, NeXT was also the basis for > Apple''s Cocoa framework, so there''s a lot of similarity there. So in that > sense, FOX is very much current. Likewise for the GUI update mechanism, data > targets, and other neat things. I''ve learned a lot about software design by > reading through the FOX source code, and it can be an elegant platform for > building GUI applications. > > On the other hand... you have issues like look and feel. FOX looks vaguely > like a Windows 95-era user interface, which is to say, pretty darned aged. > There is a discussion taking place on the FOX mailing list as we speak, > about whether FOX should incorporate theming so that FOX-based GUI > applications could be made to look more like platform-native apps > (especially on OS X). I can tell you as a FOX "veteran" that if you''re > waiting for theming in FOX, you ought not hold your breath. So if having a > native "look and feel" for your application is an issue, you should be > looking elsewhere. Likewise for things like strong i18n support, or > whatever. > > _______________________________________________ > 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/20100917/24af776b/attachment.html>
2010/9/17 Nataraj S Narayan <natarajsn at gmail.com>:> Hi Robert > > Could you substantiate that? I mean Fox being better than Qt-4.6.x? Is it > the design? Since Qt is with Nokia ,lots of takers for Qt. Even my own boss > made me switch to Qt for the Nokia patronage.for me there is few reason why I think that fxruby is better then qt 1) implementation of qt in ruby is very poor 2) qt is too big (there is a lot of features but if someone want very simple design qt is not for him) also if You want to pack it on some very smapl devices it can be problem with all qt lib which are sometime very big. 3) fxruby is much more easier to learn then qt 4) I don''t like if project is developed by huge company it''s hard to communicate with developers :P -- Robert Mitwicki Kontakt: ? ?? jid: mitfik at jabber.org ? ?? e-mail: mitfik at gmail.com ------------------------------------------ www.partiapiratow.blog.pl