On 08/15/2012 01:30 PM, Robert Nimax wrote:
Hi,
thanks a lot ! I think, to add a the require-configuration is the way
to go. I will try this solution later.
I guess, I expressed myself not correct. Of course, I did not change
the boot part per se. JI just moved code to other classes to minimize
dependencies so that the part, that will be loaded after the boot part
(the first view of the application) will be much smaller. So I still
don´t understand, why the dependency between qx.ui.core.EventHandler
and qx.ui.core.Widget is not established. The generator should analyse
qx.ui.core.EventHandler and "see" the dependency to qx.ui.core.Widget,
because of the method canHandleEvent, shouldn´t it ?
Which version of qooxdoo are you using?
Yes, the generator should see the dependency, and I'm quite confident it
does. But defining parts is a tricky business, and you can define parts
in a way that they cannot be built consistently [1]. But in that case
you should at least get a generator warning. If not then that's a bug,
and we would basically need your entire code and config (or at least a
subset that reproduces the issue), in order to analyse it.
T.
[1]
http://manual.qooxdoo.org/2.0.x/pages/development/parts_using.html#in-depth-configuring-the-include-key-of-your-parts
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
