Interesting. But that would require a SWC that stubs the browser APIs? On 12/16/13 6:27 AM, "Frank Wienberg" <fr...@jangaroo.net> wrote:
>Hi Alex, > >sorry for the late response. >I didn't mean to use the same code base for the SWF and the HTML >components, but only the same programming language: ActionScript! >Of course you would still have to learn different low-level APIs >(DisplayList versus browser DOM/BOM), but at least you could use the same >language and the higher level constructs from AS3 like packages, classes, >interfaces and the superior IDE support that exists for ActionScript. > > >On Tue, Dec 10, 2013 at 7:10 PM, Alex Harui <aha...@adobe.com> wrote: > >> The implementation of some low-level components will be vastly different >> for SWF than for JS. I'm not clear how you could generate the JS from >>the >> AS version. >> >> -Alex >> >> On 12/10/13 12:13 AM, "Frank Wienberg" <fr...@jangaroo.net> wrote: >> >> >Hi, >> > >> >great to hear of this new approach! >> >I never understood why you guys implement Flex components for HTML5 in >>JS, >> >not in ActionScript. Once you have AS3 API "stubs" of the browser APIs >> >(DOM, BOM, remember my suggestions about a [Native] annotation some >>time >> >ago?), you would not be limited to building compound components like >>this, >> >but you could implement *any* component in AS3, in other words, port >>your >> >JS code to AS3! Or is there any show stopper for that with the FalconJx >> >compiler that I am not aware of? (Maybe the missing [Native] support?) >> > >>