Instead of creating all new AS and JS components (basically doing mirror images for each component), I'm thinking of using the Flex SDK 'vanilla' (with maybe wrapper classes to hide unsupported class members) and create "only" the JS equivalents. This would greatly simplify development, and there is no learning curve for Flex developers, as they use the SDK they know and love.
I did some preliminary testing of this concept, and it has potential. Especially if you have control over the cross compiler ;-) I'm not worried about applications being too heavy with framework JS code, as the Closure Compiler simply discards all code that is not used/referenced. Like I said, I'm committed to getting FlexJS up and running first, as I have a lot invested in it and I think it's the way forward. But I think I'm addicted to playing with this whole cross compilation thing and hope I'll eventually get round to trying it "the other way around" :-) EdB On Thu, Jan 30, 2014 at 8:22 PM, Kessler CTR Mark J < mark.kessler....@usmc.mil> wrote: > Would that be along the lines of a Vanilla AS sdk that is setup to be more > in-line with the JS version? So they work the same upfront? > > -Mark > > -----Original Message----- > From: Erik de Bruin [mailto:e...@ixsoftware.nl] > Sent: Thursday, January 30, 2014 1:23 PM > To: dev@flex.apache.org > Subject: Re: Wrapped flash packages and FalconJX > > I haven't given up on my VanillaSDK idea, but as I don't even have time to > help finish FlexJS now, it'll be a while before I get to work on that again > ;-) > > EdB > > -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
