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 209.85.160.175 as permitted sender)
Received-SPF: pass (google.com: domain of carlos.rovira@gmail.com designates
 10.236.189.42 as permitted sender) client-ip=10.236.189.42;
MIME-Version: 1.0
Sender: carlos.rovira@gmail.com
In-Reply-To: <4F44D30C.7010101@leichtgewicht.at>
References: <4F44C4BF.4020904@motion-twin.com>
	<4F44D30C.7010101@leichtgewicht.at>
Date: Wed, 22 Feb 2012 13:09:31 +0100
Message-ID: 
 <CAMFKFRjckRn4Z0E5zrA7FPD5SfXwhU8Th4ng0JCaMuMTkMFRmw@mail.gmail.com>
Subject: Re: Flex adopting haXe ?
From: Carlos Rovira <carlos.rovira@codeoscopic.com>
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=20cf30434aa069053004b98c6670

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

Hi Nicolas,

I think the proposal to port Apache Flex to haXe sounds very good since
many of us know you, your talent and what you did with MTASC and later with
haXe. Your quality writing compilers and getting the right solution is
superb.

Many of still remember the open source flash era back in 2005 when a
vibrant community was making the osflash movement successful. Then Adobe
comes with brutal changes that broke the community : Flash 9, AS3, Flex 2,
FDS, and so on. You decided to create haXe as well.

Now haXe has evolved great and Apache Flex could go the haXe way to be a
real open source framework that does not depend only in Adobe's runtime.

The problems behind : This way is hard, but feasible, and take into account
that principal actors using Flex nowadays are IT departments of huge
organizations and enterprise customers that need a viable migration path to
all applications deployed until now.

We must to take into account, that Flex is MXML and AS3 right now. People
that wants to move from adobe flex sdk latest sdk (4.6) to apache flex,
need a migration path that could be done with more or less pain. If we
chage in a radical manner and adobe sdk and apache flex sdks is radicaly
different, we could loose in the process lots of users.

I, as many others, would love to see haXe and you  (Nicolas) contributing
to the effort, but I think we should have a feasible plan in order to see
this as a viable option.

Is strange, but seems things are turning to the state we left in 2005-6  ;)

Great to see you here Nicolas! :)

Carlos Rovira


2012/2/22 Martin Heidegger <mh@leichtgewicht.at>

> Hello Nicolas,
>
> Thank you, I can only speak on my behalf but I think its a very nice post=
.
> I have tried to get into haXe in the beginning and was thrilled but I was
> never able to get the companies I worked in to use haXe. I know that haXe
> has a lot of features that AS3 doesn't have. Particularly "using" is just
> plain awesome. Others are debatable like typedef+interfaces or the notati=
on
> for properties.
>
> However I used ActionScript a lot in the past years and found ways to wor=
k
> with it that are unlike the work with haXe because when I recently tried
> out haXe again I was bothered by a few language features that I use heavi=
ly
> in ActionScript and have not found a good equivalent in haXe (in other
> words: they are missing in haXe - aren't they?):
>
>  *) Standalone variables/constants/function files outside of a class
> context. I found them very liberating and as far as I can tell: haXe only
> allows class/ENum/ alike.
>  *) e4x: Its such a pleasure to use in AS3.
>  *) Default initialized properties:
>     class ABC {
>         public var x: int =3D 1;
>     }
>  *) Working "this" in function references: Using function references has
> become such a normal thing in AS3 that I wouldn't know how to implement a
> similar design with without them.
> *) Namespaces: While I don't "like" namespaces particularly, porting Flex
> to haXe might be difficult without it.
>
> There are other features in the compiler that are worth talking about tha=
t
> I am sure would be reasonable to continue having in Flex.
>
>  *) Compiling the "asdoc" to different locales
>  *) Documentation on Meta-tags
>  *) Binding
>  *) Assets (Fonts!) loaded compiled through meta-data
>
> Have there been discussions about this points in the haXe community?
>
> yours
> Martin.
>
>
>
>


--=20
Carlos Rovira
Director de Tecnolog=EDa
M: +34 607 22 60 05
F:  +34 912 35 57 77
<http://www.codeoscopic.com>
CODEOSCOPIC S.A. <http://www.codeoscopic.com>
Avd. del General Per=F3n, 32
Planta 10, Puertas P-Q
28020 Madrid

--20cf30434aa069053004b98c6670--