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 omarg.developer@gmail.com
 designates 74.125.82.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <7B57D62E-629A-4427-97C5-49F2849550A0@classsoftware.com>
References: <03f401cce37e$de63d210$9b2b7630$@davidarno.org>
	<CAH12+xPU+hinkhJeEfxZZmBo9y_p_SCAzfA_wmk3Ux4FZ-1FrQ@mail.gmail.com>
	<1328395619.2089.6.camel@lapsang>
	<CAEFz_vsO9CKF_tycJTvdsQHSf8jkaU6O2EfTWKn1CeCrQudcuA@mail.gmail.com>
	<1328399252.2089.17.camel@lapsang>
	<7B57D62E-629A-4427-97C5-49F2849550A0@classsoftware.com>
Date: Sat, 4 Feb 2012 17:26:50 -0800
Message-ID: 
 <CAEFz_vuFuZcsUHw_=3jzxyMjdDRHaEH5aJ-_SthRnhXAMCsMPw@mail.gmail.com>
Subject: Re: [Discussion] Flex 5 and non-SWF targets: Skinning
From: Omar Gonzalez <omarg.developer@gmail.com>
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=90e6ba211f1bac27ba04b82d7048

--90e6ba211f1bac27ba04b82d7048
Content-Type: text/plain; charset=ISO-8859-1

You should check out ext.js if you haven't, they have most of the
components Flex has and then some.

As far as performance, I don't know how they compare, but that wouldn't be
the point to writing such a port. The point is that many applications will
not use Flex because targetting AVM limits their ability to be on tablets
and mobile devices as a web application. Compiling to JavaScript would
solve that while providing a more robust application framework with type
safety to develop in.

-omar

--90e6ba211f1bac27ba04b82d7048--