Hello Walter, >> From my limited understanding of both RAP and qooxdoo it appears to me that >> qooxdoo is a natural choice for a solution like RAP, which leads to my first >> question: how many of the features of RAP are really features of qooxdoo? >> e.g. I know the RAP team are working on improving themeing support, but will >> this simply be implemented by upgrading to qooxdoo 0.8 and providing the >> themeing features of qooxdoo? >> >> > > This is something I can't tell. The cut point between RAP and qooxdoo > might vary from feature to feature. I'm not sure about the > implementation of the themeing support. > With qooxdoo 0.8 we extended the the way widgets can be styled dramatically. This should give RAP much more possibilities to style the widgets. How and if these new styling features are exposed by the RAP API is out of my knowledge.
>> I've also noticed that RAP applications appear to use absolute positioning >> for every element and define some possibly redundant inline styles (e.g. >> border-color and/or border-style when border-width is 0). Is this because of >> qooxdoo or a choice made by the RAP developers (the more complex qooxdoo >> demos seem to use absolute positioning and inline styles)? >> >> > > I believe the main reason for this is the fact that in RAP layout is > managed on the server, so they use absolute positioning on the client. > I'm not sure about the inline styles. > RAP uses the original SWT layout managers on the server side and thus positions all qooxdoo widgets using absolute coordinates. In qooxdoo applications we usually avoid this and use dynamic layouts instead. Custom RAP widgets will use dynamic layouts as well. >> Finally, if we were to adopt RAP we have a number of widgets we have >> developed in house based on YUI (and possibly some based on Prototype) that >> we would want to adapt for use in RAP. Are there any recommended approaches >> for using qooxdoo to wrap widgets written using another framework? >> >> > > I'm afraid I'm lost on this one. Anybody else?! > We usually don't recommend mixing UI code from different libraries. It would be hard to create a consistent application when mixing widgets from different toolkits. Features like theming, event handling, focus handling, drag and drop depend on a single consistent widget system. You would further increase the amount of required JavaScript by the size of the other framework. I would suggest rewriting those widgets - its not too hard to write custom widgets in qooxdoo. If you want to have these widgets in RAP you would have to write the bindings anyway. Best Fabian -- Fabian Jakobs JavaScript Framework Developer 1&1 Internet AG Brauerstraße 48 76135 Karlsruhe Amtsgericht Montabaur HRB 6484 Vorstand: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Matthias Greve, Robert Hoffmann, Markus Huhn, Oliver Mauss, Achim Weiss Aufsichtsratsvorsitzender: Michael Scheeren ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
