Hi Bogdan, In your post you refer to this implementation as useful from an accessibility point of view, can you clarify what do you mean exactly and which are the benefits you see in this field? You don't thing the pattern you described is very similar to traits?
Giorgio On 1/23/12 9:32 AM, "Bogdan DINU" <flex.programm...@gmail.com> wrote: >Hi everybody, > >I have a suggestion regarding how Flex 5 UIComponent class should work. >Please read this <http://www.badu.ro/?p=202> and >this<http://www.badu.ro/?p=204>in order to understand what I mean. > >I think that this approach will solve not only the compatibility issues >that we might encounter, but also automation (besides many many other >things), create lightweight and powerful components with less memory usage >and add a very flexible way to create new components. > >I've seen this technique is often used in games. Saw it implemented in Ben >Stucki's Reflex framework <https://github.com/reflex/reflex-framework> and >in Michael's Schmalle >tkarchitecture<http://code.google.com/p/tkarchitecture/> >. > >Please let me know if you know any drawbacks that you can foresee. > >Best regards to you all, >Bogdan > >-- >http://www.badu.ro
