Ok, that is inline with what I was thinking. Let me know if you get the JS.swc, then I know I am not just hallucinating all this. ;-)
OT; Now that you got the asdoc tokenizer working what are your thoughts about me adding that code I have had for 3+ years to the project? If so, where would it go? I created a front end compiler but I see you had stubbed something, I could hook into that with the main application code. Like I said it generates the same asdoc using Velocity templates, so we would need a velocity.jar and whatever else dependencies. There are bugs I am sure in some of the templates but... you know. Mike On Wed, Jun 10, 2015 at 12:32 PM, Alex Harui <aha...@adobe.com> wrote: > > > On 6/10/15, 9:19 AM, "Michael Schmalle" <teotigraphix...@gmail.com> wrote: > > >Alex, excuse my ignorance but "what" are your plans for integrating this, > >are you getting the JS.wsc to be built? > > I’m just about to pull your change and see if I get a JS.swc. > > I haven’t really thought through “what”. I may need to play with it a bit > first. My early thoughts are: > > 1) put JS.swc in the Falcon nightly build > 2) Have the FlexJS Installer add JS.swc to what gets installed. > 3) Create new .bat and shell scripts to run with any different compiler > options > 4) Create a new FB Launch Configuration as well. > > Then I think folks can use the Flex SDK Installer to install the FlexJS > Nightly and try this stuff. > > -Alex > >
