> -----Original Message----- > [mailto:[EMAIL PROTECTED] On > Behalf Of Hugh Gibson <snip> > > Very interesting. We did all of our wxPython work without a > GUI designer > [fx: spit] >
Wow! If I had to do that, I would be so broke financially that I would be on the unemplyment line. Just think about having to come up with over a hundred screens within the contrain of a week or two. > Unfortunately it seems that Pythoncard is almost moribund. > There's been no development work on it for quite a while. > Last blocks of check in of source code was in July and > November 2007 - see > http://sourceforge.net/project/stats/detail.php?group_id=19015 &ugn=pythonc ard&type=cvs&mode=12months&year=2008 That's not the issue with Pythoncard. The issue is that it is so addictive that it's *very* hard to try to get off it once you're hooked - because everything else are so complicated and unproductive. That's why I am working on my poor man GUI designer. If I am successful, I can have the same set of code whether it's web based, or client-server based. In addition, I already have lots of code that are Pythoncard, I am hoping that this would minimize the amount of work I have to do in porting my application over to web based. >However there are lots of downloads - over 1000 each month. Does this mean >>that it's working really well and doesn't need any more development? The Python community has a long history of wanting to reinvent the wheel. While the Ruby folks focuses on one web framework, we have no less then 3, 4, or even more (with new ones showing up weekly - so it seems). Pythoncard started out way back in the early 2000's and enjoyed several years of intense support by the Python community. Then, they moved on to the next new thing. The lone original author of the package is still around to answer questions but it's true that it hasn't been updated to include new widgets that came along in the last year or two. On the other hand, it's very stable, mature, and reasonably full featured to get most jobs done - and can be done *fast*. But then it's all open-source - and comes with it *lots* of meaningful examples. If the need arises, I am sure things can be done to it. I added the ability for my code to create widgets on the fly via a WidgetFactory routine - which means my GUI resources can be table driven and can change dynamically. Now, I am tickering with the layout designer to create qxtransformer code. >Something which works well and integrates with qooxdoo would be great. Yes. >Hugh ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- John Henry ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
