Hi Alexander,
> Can you explain why do you need this? The child controls are internal
> parts of a widget and are for good reasons private class members.
Well, actually no objective reasons, but the overall approach looks
really neat due to following abilities it provides:
- it allows to separa
Hi Oleksiy,
Oleksiy Golovko wrote:
> Alexander,
>
> Thank you, but I was looking for a simpler method of storing child
> widgets (I mean simpler then private class members).
Can you explain why do you need this? The child controls are internal
parts of a widget and are for good reasons private
Alexander,
Thank you, but I was looking for a simpler method of storing child
widgets (I mean simpler then private class members). But now I have to
patch the Modern theme (using qx.Theme.patch) or instantiate it just to
define the aliases... (since those cotrols I'm refering using ID are
simp
Hi Oleksiy,
Oleksiy Golovko wrote:
> Hi
>
> While researching qooxdoo source code I found quite nice approach of
> creating widgets and easy access to them without creating ton of private
> class members. I mean _getChildControl & _createChildControlImpl methods
> , the approach really rocks!
Hi
While researching qooxdoo source code I found quite nice approach of
creating widgets and easy access to them without creating ton of private
class members. I mean _getChildControl & _createChildControlImpl methods
, the approach really rocks! Although I faced some strange behavior when
sta
