Yeah, sounds great, we can start that way and get a quick lift-off, but in
the long term, I would certainly also like contribute code to FalconJx.
So as agreed above, I'll continue on "my" Wiki page.

Concerning the tool chain / IDE, here is how we work with ActionScript /
Jangaroo at CoreMedia:

   - Use Maven 3 for the build process: Jangaroo provides a Maven plugin to
   invoke the compiler and build library modules and complete applications
   - Use IntelliJ IDEA Ultimate (Community does not support AS) as IDE: We
   also wrote an IDEA plugin that plugs into IDEA's Maven import process, so
   when you import the Jangaroo Maven project, you can start right off. Our
   IDEA plugin also allows incremental compile and thus fast turn-around.
   - From Maven, you can easily fire up Jetty or Tomcat to serve and test
   the resulting web application.
   - We run unit tests through old FlexUnit 0.9, either in browser (using
   Selenium) or in PhantomJS.

So besides PhantomJS, it is a pure Java solution, all you need installed is
Maven and IDEA with Jangaroo plugin, and Maven takes care of downloading
everything else (Jangaroo Maven plugin, Jangaroo compiler, Jangaroo
libraries, ...). Because everything is deployed to Maven Central, you do
not even need any special setup to use Jangaroo from Maven, and can start
with very light-weight POMs.
More about this in our "quickstart" example project:
https://github.com/CoreMedia/jangaroo-quickstart

With Apache Flex/FalconJx ready, I hope that IDEA will do all this out of
the box. You would just choose a new "Flash build configuration". Where
currently you have "target platforms" Web (FlashPlayer plugin), mobile and
desktop (both AIR flavors), there should be a new target "Web
(JavaScript/HTML5)" (or the like). Flexmojos should take over the role of
the Jangaroo Maven plugin.

Hope this helps,
-Frank- J8)


On Mon, Jan 21, 2013 at 3:14 PM, Michael Schmalle
<apa...@teotigraphix.com>wrote:

>
> Great!
>
> Here is my thought Frank, I see no reason for you to even have to write
> the AMD part. It dosn't make sense from a standpoint of time, when I get
> some other things out of the way, if I have a good spec it would take me
> less than a week with tests.
>
> This will allow you to focus on other things.
>
> BTW I wanted to ask, how does this now from your view fit into the "tool
> chain" IE IDEs, how do you "work".
>
> Use IntelliJ for example. I'm curious because I have a WebAudio project I
> am going to be starting and I want to know how I would hook the compiler up
> to it's build system. Ideas?
>
>
> Mike
>
>
> Quoting Frank Wienberg <fr...@jangaroo.net>:
>
>  On Mon, Jan 21, 2013 at 1:55 PM, Michael Schmalle
>> <apa...@teotigraphix.com>**wrote:
>>
>>  Frank,
>>>
>>> Let me be direct, do you want to start working on AMD output?
>>>
>>>
>> Not necessarily right now. Still seems like a steep learning curve for me.
>>
>>
>>  IMO you should definitely finish up the Wiki stuff so it clear what needs
>>> to be done with AMD output.
>>>
>>>
>> I was straightly asking what helps you most, so if you say let's get the
>> specification finished first, I'll continue with that ASAP!
>>
>> Cheers
>> -Frank- J8)
>>
>>
> --
> Michael Schmalle - Teoti Graphix, LLC
> http://www.teotigraphix.com
> http://blog.teotigraphix.com
>
>

Reply via email to