Hi folks,
*Context :*
I just coded some new widget for my company app, and for the first time I
used the _createChildControlImpl method to create UI children. But to create
the children in the right order, I have a method, _create, that calls
several times the getChildControl method. So I don't totally delegate the
children instanciations, though I spare myself the manual handling of
references (which is really an improvement ^^).
*What I do :*
- override _createChildControlImpl and code whatever instanciations I need
(buttons and stuff)
- for each component in this method, if one needs another one, I make sure
the needed one is created by calling getChildControl("my_need_comp_id")
*Question :*
What would be the typical workflow to achieve this ? I'm pretty sure there a
cleaner way to delegate the children creation to Qooxdoo, a bit like the
Flex _updateDisplayList deferred calls.
*TL; DR*
Can anybody show how a big UI widget handles its children ? Is it totally
delegated to the framework ?
Thanks a lot for this wonderful framework :-)
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/What-is-a-classical-qooxdoo-widget-lifecycle-implementation-tp7581892.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
