Hi Carlos,
I've said this before: I feel bad sometimes that Flex taught folks some
questionable programming practices.
The short answer:
-Don't reference concrete classes
-Choose composition patterns over inheritance
The long answer:
Yishay and Andrew are headed in the right direction. A
Hi Yishay,
El mar., 30 abr. 2019 a las 13:27, Yishay Weiss ()
escribió:
> It seems to me this is more an AS3 issue than a Royale issue. It would be
> cool to enhance AS to include features such as Mixins, but as long as we
> have a simple single inheritance model the solution you implemented is
It seems to me this is more an AS3 issue than a Royale issue. It would be cool
to enhance AS to include features such as Mixins, but as long as we have a
simple single inheritance model the solution you implemented is probably
optimal.
I personally wouldn’t worry too much about code
Hi Andrew,
thanks for your thoughts. One of the main problems here that I didn't put
on my email is that you loose the opportunity to ask if the components is a
"StyledUIBase", since we are "bifurcating" the code when implement in Group
and DataContainerBase and others the interface
Hi Carlos
Isn't this similar to the challenge that Adobe had with EventDispatcher? which
I think is why there are two possibilities:
a) derive from EventDispatcher
b) implement IEventDispatcher
In the second case, you have to create an instance of EventDispatcher within
your class, and then
