Hello Alex, To be honest, your approach sounds like the proper way to move forward (at least to me), but I still think that using what we already have in the AS side is going to take less time and as you have already said in some emails, this year will be a crucial one for Flex.
Anyway, having choices is always good. Time will show which one will be adopted by the community. Regarding the VanillaSDK, I can't understand how it's possible without some kind of Flash API emulation (like in Jangaroo) but I haven't looked at the code yet so I think I'll get it when I do. On Fri, Jan 25, 2013 at 8:30 PM, Alex Harui <aha...@adobe.com> wrote: > > > > On 1/25/13 10:11 AM, "Frank Pepermans" <frankp...@hotmail.com> wrote: > > > I concur, this is huge news for the future of Flex! Congrats to making > this > > possible! > > > > About the vanilla sdk, I have some Jangaroo experience, there you can > build > > a full AS Button component, > > which compiles to JS without the need of a vanilla SDK. > > > > 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 > the > 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. > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > > -- Nick Tsitlakidis, CEO and Software Architect at Perfect Edge LTD. www.perfectedz.com
