Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <50840DB2.9020701@gmail.com>
References: 
 <CAAd0WrYwRtzCUDADnq2NDD49Ea6J=dRLcrhS081Uu_DNH=4Nag@mail.gmail.com>
	<5082A9C6.6010704@gmail.com>
	<CAAd0WrYb5sXfoe1kOVYXHs4YXYNbhNd-EO72O5TERRz5jO138g@mail.gmail.com>
	<50840DB2.9020701@gmail.com>
Date: Sun, 21 Oct 2012 19:03:40 +0200
Message-ID: 
 <CAJs+wW2-PCMEQimCBq-SC5iF4ADNxuC-gqFR9nD5tCisHgUuoQ@mail.gmail.com>
Subject: Re: Starling + Flex
From: Erik de Bruin <erik@ixsoftware.nl>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Content-Type: multipart/alternative; boundary=e89a8f503838fade9504cc94b715

--e89a8f503838fade9504cc94b715
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Things worth doing are hardly ever easy. Does that mean we shouldn't do
them at all? You seem to have a clear idea how a future-proof framework
should be architected. Maybe you can share those insights with the project,
or maybe even start working toward the goal you seek. I'm sure there will
be others that are interested in such a project and will be willing to
invest (considerable) time in it!

Stop blaming Adobe for decisions made in the past and work with us to
prepare Apache Flex for the future.

TL;DR: in Open Source you have to "put your code where your words are."

EdB


On Sunday, October 21, 2012, s=E9bastien Paturel wrote:

> Thanks for the update,
> but why would it require a "fairly massive rewrite" exactly?
> when you say "I would look at that" about feathersui, you mean as an
> alternative to flex?
>
> its quite a bad news IMO. if flex can't "easely" target a new rendering
> layer like starling, which stay in an Adobe runtime,
> what is the future of flex as a multi platform framework, and especially
> as a mobile SDK?
>
>
>  After discussing with Thibault and spending time working on this I've
>> determined that a fairly massive rewrite would be required. Shortly afte=
r
>> they released http://feathersui.com/ and I will say that it is a nice bi=
t
>> of work. I would look at that.
>>
>> On Sat, Oct 20, 2012 at 8:40 AM, s=E9bastien Paturel
>> <sebpatu.flex@gmail.com>wrote:
>>
>>  Hi jonathan,
>>> What is the state of this very promising project?
>>>
>>> Le 14/06/2012 18:46, Jonathan Campos a =E9crit :
>>>
>>>   Recently I've been getting aquatinted with Starling to see if it coul=
d
>>>
>>>> work
>>>> with Flex. After a few days of playing I think that it is possible but=
 I
>>>> do
>>>> see the issues now and there is plenty of work that is necessary to ma=
ke
>>>> it
>>>> happen.
>>>>
>>>> To get things going I basically cut down the UIComponent (to the parts
>>>> that
>>>> I cared about), made a copy of the entire Flex framework (as many
>>>> interfaces rely on DisplayObject, etc), replaced them with Starling
>>>> classes, rebuilt some of the Spark primitives, and "adjusted" some of
>>>> the
>>>> starling classes to fit some of the Flash interfaces.
>>>>
>>>> At this point I'm definitely going to wait to get the 4.8 release out
>>>> before giving this more time but I think it is possible. I'm sure othe=
r
>>>> developers are already aware of it but if we could make some new
>>>> interfaces
>>>> such as an IDisplayObject it would be much easier switching out
>>>> DisplayObject for a Starling DisplayObject.
>>>>
>>>> Just thinking out loud at this point.
>>>>
>>>>
>>>>
>>
>

--=20
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

--e89a8f503838fade9504cc94b715--