[EMAIL PROTECTED] wrote: > Thanks for the reply. > > If, as you said, "You can literally write an full > application in a few hours", why wouldn't it be the > "official" way qooxdoo does things? Or ask in a > different way, when would you *not* use qxtransformer > and stay with pure qooxdoo then? > > > Well, this is on the level of guess-work about other people's preferences, but here you go ... just a few ideas:
* when you have an existing web app you want to revamp and need a more gradual transition (we're on the way to provide better support for this in qooxdoo) * when your staff are all versed JavaScript programmers * when you need more control over or higher dynamics within your GUI (which might be harder in a pure declarative approach - Christian?) * when you are in an entirely different environment where your code gets 'compiled' to qooxdoo (like Eclipse/RAP or QWT) * when you like programming better than 'declaring' (e.g. because you are a die-hard Java programmer who is forced by his boss to do a Web front end :) * when you don't like XML (if that is possible ;) In essence, I think it is a very good situation that there is quite a bunch of "programming models" for qooxdoo (http://qooxdoo.org/about/framework#alternative_programming_models), for people to choose from. T. ------------------------------------------------------------------------- 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
