> they expect > qooxdoo to be a web application platform, which, in a round about way it > is, > but I would rather view it as an application framework for applications > that > run inside a browser.
Very nicely put :). > That said, there is only one thing I would improve, (although I'm not > certain how yet.) The application creation and build processes have > proven > difficult when embedding into a source controlled (subversion,) MVC > project. Could you be a bit more specific about that? Have you realized you can tweak the paths to class code, resources etc. in the Manifest.json?! > The one thing that ExtJS and Dojo have over qooxdoo is actual printed > material. If you stumble across E or D online, a quick search at amazon > gives you numerous options of books on the subject. A search for qooxdoo > results in books that merely mention qooxdoo in footnotes and appendices. This is an interesting thought. But I really have no clue how this could happen. I'm still surprised how some technical writer can bang out hundreds of book pages in only a few months about a technical topic. > Anyway, sorry for the lengthly muse. Appreciate your detailed feedback. T. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
