Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 david@davidarno.org does not designate 74.125.82.43 as permitted sender)
From: "David Arno" <david@davidarno.org>
To: <flex-dev@incubator.apache.org>
References: 
 <CALFuuO0+pxBM7HXoTSs-0rpXhRLPJsvU3ofU4KVEdqhXY-dLdQ@mail.gmail.com>
In-Reply-To: 
 <CALFuuO0+pxBM7HXoTSs-0rpXhRLPJsvU3ofU4KVEdqhXY-dLdQ@mail.gmail.com>
Subject: RE: Flex 5 should be divided to desktop project and mobile project
Date: Thu, 26 Jan 2012 12:14:09 -0000
Message-ID: <074001ccdc24$021a1960$064e4c20$@davidarno.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AQJjjKhnzikinh2Qhk3DnWcYdsqu9pTxLDQA
Content-Language: en-gb

> From: Pepe [mailto:pepe.fxug@gmail.com] 
> Sent: 26 January 2012 07:45
>
> Please do not try to make a hybrid architecture. I believe it will
failure.
> I hope Flex 5 will have two versions which are desktop version and mobile
version.

The key here is to use composition, rather than inheritance, for the Flex 5
components. This then allows the mobile and desktop components to be
composed differently (no mouse handler for mobile for example.)

Of course since composition involves lots of interfaces and small classes,
it may not happen for performance reasons. In which case we have to keep the
monster class style of Flex 3 and 4 and it will need people like you Pepe to
help write two versions of each component class :)

David.