I'm trying to create a number of objects and form fields within a Window
object, and I'm struggling to find documentation that describes the
right way to create and access specific child objects within the parent
object. I'll need to have events on certain objects in the Window be
able to adjust or alter other objects within the same Window (but
possibly in a different container). Creating the child objects is
pretty straightforward, but using them within other methods of the
parent object are not so obvious. I'm not sure of the right way to
create and reference child widgets and objects within a parent object in
order to make my development most efficient and avoid other potential
pitfalls along the way.
I've looked at the code within the qx.ui.window.Window class, and I see
that the children are created within a method named
"_createChildControlImpl". I see that the children are created by
referencing their Appearance ID, but I don't see anything that actually
associates the ID with the child control when it is created. I see a
method for GetChildControl that uses the ID value to locate the child
object. So, if I create several child objects of the same type, I'd
need them to have unique ID values, right? I think default ID values
exist for each object class (but it's not obvious in the API docs) based
on theme functionality. What might happen to appearance and decoration
defaults if I define a special ID value for a child control? I think
the appearance Alias value might be involved somehow. How complicated
is it going to get to specify unique ID values for each object in the
Window?
I think I should model my creation and reference of child objects from
how the qx.ui.window.Window class does it, but it would be helpful if
there were some tutorial within the documentation that talks about this
specific issue, particularly how to set and use ID values for child
controls. I can't seem to find anything on it in my searching, so I
wonder if I'm just missing it or it's not there yet. Maybe I'm making
it more complicated than necessary.
Can someone suggest the best way to begin learning how to manage this
particular part of the development process? I wonder if there needs to
be a chapter in the documentation dedicated to Parent-Child object
access to help developers get started the right way, or maybe it's there
but buried too deeply in the current documentation.
Thanks,
Gene
------------------------------------------------------------------------------
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
