Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: pass (athena.apache.org: domain of aharui@adobe.com designates
 64.18.1.187 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "dev@flex.apache.org" <dev@flex.apache.org>
Date: Fri, 25 Jan 2013 10:30:04 -0800
Subject: Re: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher and
 the VanillaSDK JS framework.
Thread-Topic: [ASJS] AS to HTML5 in action: announcing the ASJS Publisher
 and the VanillaSDK JS framework.
Thread-Index: Ac37J3mXFEl1tSHwQuuSJnvb4vdFqAAAoSTc
Message-ID: <CD280F2C.4C460%aharui@adobe.com>
In-Reply-To: <DUB117-DS5AF1FBF26916310803358A31B0@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.13.0.120411
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


On 1/25/13 10:11 AM, "Frank Pepermans" <frankprms@hotmail.com> wrote:

> I concur, this is huge news for the future of Flex! Congrats to making th=
is
> possible!
>=20
> About the vanilla sdk, I have some Jangaroo experience, there you can bui=
ld
> a full AS Button component,
> which compiles to JS without the need of a vanilla SDK.
>=20
> I assume technically you can do the same, if the basic Flash API stuff is
> 'emulated' for JS and included with the compilation?
Yes, it is great to see other approaches being investigated.  I think there
three approaches right now.

1) Jangaroo: Actually a product.  Uses Flash API emulation
2) Eriks' VanillaSDK: Still a proof of concept.  My main concerns are that
it will be a lot of work to finish, and that it will drag with it all of th=
e
unused code the Flex SDK does with its intertwined dependencies.
3) My approach: Still a proof of concept.  Brand new SDK designed to be
optimally implemented in both JS and AS.

--=20
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui