On Fri, 2009-06-12 at 10:04 +0200, Alexander Back wrote:
> Hi Gene,
>
> I've just re-read the article "Custom Widgets" to check it if it's holding
> the
> necessary information. From my point of view everything is explained
> sufficiently, especially the "Styling" section [0] does mention the
> connection
> between the child controls and the appearance system.
>
> But since I'm a core developer I may overlook some points which are not
> properly explained and simply presuppose them as known.
>
> It would be great if you can re-read the page/section and tell me what can be
> improved or what can lead to misunderstandings.
Alex,
I'm not exactly sure which improvements might speed up understanding,
but I think this topic is a bit more complicated than can be adequately
explained with a single chapter and a couple of short snippets. I
didn't grasp the significance between overriding the
_createChildControlImpl method and then later referencing the method by
ID value. An example that references the control to change a value or
disable the control might have be clearer to me.
I'm also not sure how _createChildControl compares to
_createChildControlImpl, which is never mentioned. I overrode the
second one as in the qx.ui.window.Window class, so what would have
happened if I had overridden the first one instead. Are there instances
where you should override one versus the other?
I think typical usage may be more complex than outlined in the existing
chapter content, and maybe that's where my understanding met with
difficulty. I think the chapter assumes that I'm writing a new widget
with a couple of added components. Instead, I'm trying to create a new
class that creates and controls a window object within a desktop object.
My layout structure is multiple objects deep, with Composite containers
to manage the window layout? Maybe I'm trying to bite it off as too
large of a chunk. When I'm creating child controls within a large
window class like this, should I create the entire page of controls in
one custom widget class, or is this going to cause problems?
Are there certain classes of Qooxdoo objects that don't work well or
correctly within this child control system? The documentation doesn't
really touch on any limitations of this subject.
Are there certain issues to consider when I try to access the child
object in a listener on one of the other child objects? Do all created
controls appear as children of the extended class, even when they are
added as a child of one of the existing child controls in terms of the
layout structure? If so, then I should always reference them through a
simple "this.getChildControl("mycontrol") call. Or, do I need to
reference them by the layout structure through chained getChildControl
methods?
An example that implements a few custom controls, sets up a layout of
them, and then accesses them for reading or setting properties might go
a long way towards helping the reader grasp the big picture. Maybe this
is best done in a secondary chapter rather than extending this general
chapter. I just know I didn't get the whole picture by reading this
chapter.
Just some ideas, but we can exchange further ideas if it will help sort
out where my understanding failed.
What do you think?
Gene
> cheers,
> Alex
>
> [0] http://qooxdoo.org/documentation/0.8/ui_develop#styling
>
------------------------------------------------------------------------------
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
