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 carlos.rovira@gmail.com
 designates 74.125.82.43 as permitted sender)
MIME-Version: 1.0
Sender: carlos.rovira@gmail.com
In-Reply-To: <5085188F.7090505@gmail.com>
References: <CCA9803E.4776C%aharui@adobe.com>
	<5084548C.3000604@gmail.com>
	<CAJs+wW3GSNE8YpMU4MGTer4EhFYRnHA75zHH5fv1+gV5EODFEQ@mail.gmail.com>
	<5085188F.7090505@gmail.com>
Date: Mon, 22 Oct 2012 12:17:09 +0200
Message-ID: 
 <CAMFKFRgbL4gDi=U7nS3mJ5knH5qKQ9+pf1TX9J-nXL1YeL2bEQ@mail.gmail.com>
Subject: Re: Starling + Flex
From: Carlos Rovira <carlos.rovira@codeoscopic.com>
To: flex-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I'm with Alex that Flex actual codebase is very old. It relys on
things set up on Flash Professional 2004 (maybe even Flash MX). Then
Flex 1.x get that legacy, and then, again Flex 2.x to 4.x

Many of us would want to see changes inside the actual code base to
let our systems, applications and products evolve and not get
obsolete, but maybe that road is very painful since involves many
man/hours that maybe we don't have.

So as I put in other thread, we could think in start some refactor but
that would be mainly "maintenance mode" and not get all the
possibilities that we could get going a *new from scratch route".

Maintenance is needed, and the I assume we continue having AVM2 in
Flash Player as we continue to have AVM1 nowadays. So our legacy apps
will continue to live there. But we should start to think in the
future and that requires apply all what we know to a new framework.


2012/10/22 s=E9bastien Paturel <sebpatu.flex@gmail.com>:
> Sorry for sharing my frustration, but i'm really trying to be constructiv=
e
> in the sens that i'm trying to get clear informations of the state of the
> framework, regarding, a multi target future.
> I was not talking about Adobe here, i was saying that, in the context of
> Alex talking about starting a new framework from scratch.
> I am not complaining about how the things are today, but about the lack o=
f
> visibility of what is possible, and what is not for the future, about wha=
t
> is the state of discusison among commiters about such a subject etc.
>
>
> "discussing (on various threads and other media, like conferences) that b=
est
> approach to do that."
> I'm happy to know that there are active discussions about it. But i'm sor=
ry,
> i try to follow the ML since a few month, and i did not saw much about su=
ch
> deep discussions regarding a mutli target future.
> If it was the case, i would not be frustated (even if no definitive answe=
r
> has been found yet)
> Instead i see other frustrated readers talking about "Apache model killin=
g
> the project", "ghost town", "need of a roadmap"...
>
> Can you please give us a feedback of those conferences? Can you just give=
 a
> quick update of the state of discussions and thoughts? and do you have an=
y
> advise to help us keep track of those discussions, if the ML is not the
> right place?
>
> For now, to be constructive, i'm trying to understand:
> - What is the current vision of commiters regarding the future of flex, a=
nd
> the multi target possibilities? Thanks a lot to Alex to have shared a
> detailed explaination of his current toughts. I'd also love to see commit=
ers
> answer to the thread "What is the essence of Flex".
> - What does it imply for flex as a mobile multi target SDK if it does not
> run on next Adobe runtime in the short term? (it depends on Adobe's plan
> regarding AIR runtime in fact)
> - What is the amount of work required to get flex run on starling? Is it
> manageable task (for major update) or does it imply big rewrite of SDK?
> - What is the list of dependancies that tie the SDk to flash platform?
> - Is there a realistic future for actual flex in middle term to be still
> multi target, or is it such a mess that starting from scratch is the only
> realistic way?
> ...
>
>
>
> Le 22/10/2012 08:46, Erik de Bruin a =E9crit :
>
>>> I feel that everything is going back in time. We're not talking about
>>> abandoning an old technology, to get new modern and better one, we're
>>> talking about abandoning a very efficient technology, with no alternati=
ve
>>> with the same level of possibilities.
>>
>> I can understand your frustration, but you're not talking to Adobe on
>> this list, you're talking to the contributors to Apache Flex. We
>> trying to find a way to take the framework forward and are discussing
>> (on various threads and other media, like conferences) that best
>> approach to do that.
>>
>> Being constructive helps. Complaining that things are the way they are
>> doesn't. Please be constructive.
>>
>> EdB
>>
>>
>>
>


--=20
Carlos Rovira
Director de Tecnolog=EDa
M: +34 607 22 60 05
F:  +34 912 35 57 77
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es