I'm curious to see your work Alex. Were you able to do some performance and memory tests with your prototype?
Haykel On 24 January 2012 19:17, Alex Harui <aha...@adobe.com> wrote: > > > > On 1/24/12 10:09 AM, "Haykel BEN JEMIA" <hayke...@gmail.com> wrote: > > > Just looking at the interfaces UIComponent implements I can see some > > candidates for implementation as behaviors (besides the ones suggested by > > Tink): > > > > public class UIComponent extends FlexSprite > > implements IAutomationObject, IChildList, IConstraintClient, > > IDeferredInstantiationUIComponent, IFlexDisplayObject, IFlexModule, > > IInvalidating, ILayoutManagerClient, IPropertyChangeNotifier, > > IRepeaterClient, IStateClient, IAdvancedStyleClient, > > IToolTipManagerClient, > > IUIComponent, IValidatorListener, IVisualElement > > > > > > - Automation: required only for testing and in special cases > > - Deferred instantiation: not sure about this, but perhaps this could > be > > attached by containers that support deferred instantiation of children > > - Repeater client: I personally never use repeaters > > > My prototype chopped UIComponent into over 20 pieces. > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
