Hi guys,
I would take the opportunity to discuss a bit about the new "website"
functionalities.
On one hand, I like the concept and the idea very much. First of all, it's
very simple for newbie and the way it was conceived is rather good: it can
help popularize a lot the entire framework because of the "jquery approach"
(maybe jquery users would be interested in giving a try to qooxdoo and
furthermore it opens the door to jquery's modules conversion).
On the other hand, I must say I fell a bit lost with this whole new "facet"
:
* the qx.bom package seems to be doomed to "internal usage only" in the
future or to simply disappear when "q shortcuts" won't be shortcuts anymore.
I mean that the whole design architecture/hierarchy has changed. It's not
anymore qx.bom+qx.oo > qx.html > qx.ui.{mobile}. It's rather qx.bom ~ q AND
qx.bom+qx.oo > qx.html > qx.ui.{mobile}.
* I have the impression developing qooxdoo Native applications makes not
"direct" sense anymore. I like the OO approach but I wonder now if it
wouldn't be better to have "q module wrappers" to custom qx classes
developed in a OO way.
Actually I doesn't mean that I don't like the approach but now I really
wonder how the whole framework will evolve in the future at bom level...
Regards,
Benoît.
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/Discussion-about-Qooxdoo-Website-new-feature-tp7482249p7482249.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
