Hi George, welcome to qooxdoo! :-)
> Yes, I can see that my first question, on a technical level, does not make > much sense now. However, as I am entirely new to the issues of the "client > side" it seems like a good idea to check out hosting companies before rather > than after :) starting development. I'd just feel more comfortable if I > can find a hosting service that has other Qooxdoo developers as customers > than if I can not. I can second what others already said: you can use whatever hosting service you like, i.e. at least regarding the client-side part of your qooxdoo application. As the logic of a typical qooxdoo app is provided by one or many JavaScript files (along with other static resources like the initial html file, images, etc.), any simple webserver would do. Typically you'd also want to have some backend which your frontend asks for some data (using standard http requests, provided by qooxdoo via AJAX (i.e. low-level calls) or RPC (more sophisticated)). For the latter one (RPC) there are several optional (!) RPC servers provided by the qooxdoo community. Pick one of those that matches your preferred backend language (Java, PHP, Perl, ...), or use any other HTTP-aware service for answering AJAX calls. Once you tell the people here about your favorite languages for the backend part, I'm sure you'll get many helpful hints. Must reads: http://manual.qooxdoo.org/current/pages/getting_started/requirements.html http://manual.qooxdoo.org/current/pages/getting_started/helloworld.html > I'm still very curious about the book: > > http:// > http://www.amazon.com/QOOXDOO-LAMBERT-TENNOE-HENSSONOW-SURHONE/dp/6131904790/ref=sr_1_2?s=books&ie=UTF8&qid=1296681090&sr=1-2 > > > and whether it has new / different / useful examples or if it is (somewhat) > a rehash of what is on-line. > > Any hints on this book appreciated, perhaps the one of the authors hangs > around here. There are no reviews on the book at Amazon. The core developers focus on improving and maintaining the manual (can be downloaded as a 400 page PDF). We keep having contact to publishers. But the manual (or a slightly modified version of it) typically isn't enough for them as they look out for "unique" content. If anybody out there is interested in authoring a book about qooxdoo (possibly a beginner's guide), please get in touch with me. Regarding the book you mentioned above: never heard about it. Also don't recall any of the editors to be present on the qooxdoo-devel mailing list. > I have not seen any explicit mention yet of if the Widgets used by Qooxdoo > have been implemented by Qooxdoo - or if there is any history of a fork from > Dojo or whatever package. Perhaps it is most like one or another set of > widgets? Yes, qooxdoo has its own genuine widget set (as most of the other JS (GUI) frameworks also do). One strength of qooxdoo is a common layer in the GUI toolkit, which isn't only the base for all the widgets, layouts and themes that ship with qoxodoo, but you can easily create custom widgets, custom layouts and custom themes. They are consistent and interoperable, something you often don't get when required to download various independent plugins in some other libraries. HTH, Andreas -- Andreas Ecker Project Lead http://qooxdoo.org ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
