On Mon, 2009-06-15 at 10:27 +0200, Andreas Junghans wrote:
> Hi Alex,
>
> Am 15.06.2009 um 10:10 schrieb Alexander Back:
>
> > Andreas Junghans schrieb:
> >> I might be wrong (depending on the actual implementation of the child
> >> control handling, which I haven't looked at), but we're not talking
> >> about a relevant amount of memory anyway here. An additional
> >> reference
> >> for a widget is completely dwarfed by the resources occupied by the
> >> widget itself. I'd say don't fall into the "premature optimization"
> >> trap :-) Plus the implementation gets a lot easier by using instance
> >> variables.
> > The best way to develop custom widgets in qooxdoo is to use the child
> > control handling. It does a bit more than only setting an ID.
> > The appearance system is connected with it, you can forward states to
> > child controls to update the appeearance or you can let the parent
> > widget take control over the event handling to just name a few
> > advantages.
> > I don't say using instance variables is wrong, I just wanted to point
> > out that the child control handling handles a lot more. And it's
> > considered as the best way to develop custom widgets :-)
>
> I don't doubt what you're saying :-) However, Gene's question was
> about creating a user interface, not custom widgets (which was not
> clear at the beginning, but I think it is now).
Thanks for pointing that out Andreas, as that may very well be the
dividing point of the two methods.
To that point, I wonder if the documentation should draw out that
difference somehow for confused developers like myself. From what I'm
reading in these responses, a custom widget that is added to other
objects in various applications might benefit more from the child
handling than a single complex user interface window that includes a lot
of added child objects.
To be honest, I didn't expect this discussion thread to breed any
conflict, so maybe there IS something to be learned from this message
thread. Of course, it points out that there is more than one way to
skin this cat. :-)
I appreciate everyone's contributions to the discussion, and I think my
specific situation calls for the use of member variables rather than the
child handling interface.
Thanks,
Gene
>
> Regards,
>
> Andreas J.
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
