incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bogdan DINU <flex.programm...@gmail.com>
Subject Re: Flex 5 UIComponent - Behavior Pattern
Date Mon, 23 Jan 2012 10:15:06 GMT
This is not only about accessibility. It's about everything : behavior
classes would be specialized in one and one only. I'm writing a new blog
post right now, expanding the benefits that I've presented to you.

On Mon, Jan 23, 2012 at 12:12 PM, Giorgio Natili <g.natili@gnstudio.com>wrote:

> >Benefits :
> >
> >1) maintaining inheritance with older versions of SDK while writing an
> >entirely new framework;
> >2) lightweight components based on UIComponent;
> >3) lightweight jobs for sdk managers;
> >4) smaller memory foot print compared to previous versions;
> >5) high customization of components for advanced developers while
> >benefiting of inheritance in order for new comers to use existing
> >tutorials
> >(of course, until new documentation will be created);
> >6) much more clear logic and understanding of components lifecycle;
> >7) provides a powerful new way of including other frameworks to the sdk
> >(example : let's say that you totally override a behavior class, in order
> >to make use of injections in the entire framework).
>
> I don't see how this affect accessibility...
>
> >
> >Regarding trains, I think there is no resemblance. But if you have an idea
> >on how to achieve that with traits, I'm interested!
>
> If I found a free slot this week I'll try to elaborate, glad you are
> interested!
>
> :)
>
>
>


-- 
http://www.badu.ro

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message