After thinking back and forth we have tried to find out about how to make the UI components independent of the core of the framework.
It would be fantastic if it would be possible to uncouple dependencies other than the core ones. Imagine to have a UI component library, which is not decided by the qooxdoo team and not a compulsory unit coupled unconditionally to the core... If that would be possible to do, then the core team can focus on core development, while anyone can contribute with UI components. The current so called core UI components would be available separately and loadable on demand but uncoupled from the core. What do you say about that? Any ideas? Pros and cons? Stefan ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
