Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of wael@rsnewmedia.co.uk
 designates 88.208.233.177 as permitted sender)
User-Agent: Microsoft-MacOutlook/14.0.0.100825
Date: Mon, 23 Jan 2012 11:36:04 +0000
Subject: Re: Flex 5 UIComponent - Behavior Pattern
From: Wael Jammal <wael@rsnewmedia.co.uk>
To: <flex-dev@incubator.apache.org>
Message-ID: <CB42F679.15D6D%wael@rsnewmedia.co.uk>
Thread-Topic: Flex 5 UIComponent - Behavior Pattern
In-Reply-To: 
 <CAOD3zvmQ19d5c7Uf8xGuPbPQHhi8ha82UK=s6wHtfGGV77maWw@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

+1 to this as well, would open up many new doors for those like me who
enjoy working on their frameworks :)

Wael

On 23/01/2012 11:01, "Bogdan DINU" <flex.programming@gmail.com> wrote:

>Thank you for your input Haykel! I'm very pleased to hear that it worked
>well for you and you're happy with the results.
>
>On Mon, Jan 23, 2012 at 12:55 PM, Haykel BEN JEMIA
><haykelbj@gmail.com>wrote:
>
>> I also find that the Behavior pattern is a powerful way of making
>> components much lighter, more configurable and easier to extend and
>> customize. I have used this pattern in one of my last Flex projects to
>> create different versions of the same application with different
>>features
>> (features are implemented as behaviors). Configuring an applications
>> features was only a matter of attaching the required behaviors an
>>adding a
>> new feature was only a matter of implementing a new behavior. I can also
>> see new extensions or plugins implemented as behaviors in the future,
>>which
>> can be easily attached to your own custom components.
>>
>>
>>
>> On 23 January 2012 11:15, Bogdan DINU <flex.programming@gmail.com>
>>wrote:
>>
>> > 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
>> >
>>
>
>
>
>-- 
>http://www.badu.ro