I'm working to
streamline our application and am currently trying to reuse as many modules as
possible at runtime. For instance rather than instantiating dozens of
datepickers I'm instantiating one on the canvas and moving it around as needed.
However in a more complex app this create issues. For instance a group of
windows or a tab slider may be made invisible. While visually the datepicker was
made to look contained by the window or datepicker it's visibility is not
changed along with the view it is sitting on top of. To really complete
the illusion is there any known way to change the parent of a
view.
Couple of things
I've tried that didn't bring much success...
1) Adding the module
to the subviews & subnodes arrays it's being overlaid on. Hoping there was
some sort of internal mechanism in the view class that loops through these
arrays to change visibility of their children when their visibility is
updated.
2) Created a large
number of delegates to try and trap all the possible ways the module would need
to be made invisible
I can imagine as
more teams build larger apps this may be a way to significantly reduce
resources. Any hints as to the inner workings of the view visibility and node
structure would be greatly appreciated!
-Jeff
Shood
_______________________________________________ Laszlo-user mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-user
