flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: [FlexJS] Doing some refactoring
Date Tue, 16 Jul 2013 23:52:54 GMT

On 7/16/13 4:29 PM, "OmPrakash Muppirala" <bigosmallm@gmail.com> wrote:

>> About folks rewriting code...well, I certainly does not see people
>> migrating old applications from Flex 4.x to FlexJS, Since there will be
>> huge diferences that will make the task utopic. I expect flex developers
>> start working in FlexJS right from the first day for new projects due to
>> lots of similarities. But a global app rewrite...that's another
>> least for huge codebases (maye tiny apps could be reach this scenary in
>> time, money and developer effort).
>Not necessarily.  I try my best to keep the (application) Model and
>Controller separate from my View classes as much as possible.  The use of
>frameworks like Parsley, Swiz etc. helps to keep this kind of separation.
>In projects where this is true, it will be an easier migration path from
>Flex 4.x to FlexJS since we will be resusing the Model and Controller code
>almost a 100%
>At least, this is what I am hoping for.  Any reason to believe I am
After I finish up this addElement experiment and check it in or abandon
it, I'm going back to getting the Falcon compiler to generate a SWF using
the new MXML codegen, then getting FalconJX to output JS for the same
code.  And this is in an attempt to migrate a production application built
by Adobe.  I've already seen FalconJX port one of their backend SWCs, and
Falcon compiled their core UI SWC

If you have an existing app with 10K lines of MXML and 100K lines of AS,
and you need to get it to run without Flash, the gpal is that FlexJS and
FalconJX will allow you reuse as much of that MXML and AS as possible but
not 100%.  First versions of FlexJS and FalconJX may be put that % at 50
but if we get more folks involved, we can probably get that number up past
80 in some cases.  Your mileage will vary based on what you are starting

And for the pieces you have to hand-migrate, I ask folks "would you have
had to hand migrate it anyway?"  If your app uses XML and E4X, even
without FlexJS/FalconJX you would have had to hand migrate all of the XML
handling since there is no E4X in the browser.  And if you are going to do
that, you should consider going to JSON.

But if your app was already using JSON via Flex HTTPService in Flash, that
should cross-compile pretty cleanly.  It did for the backend library in
that Adobe app.

The UI that is being migrated is pretty lightweight: no charts or
datagrids, lots of Panels, Buttons, TextInputs, Spinners, Sliders.  Peter
is working on Slider, we have versions of everything else checked in.

But there is lots of work ahead.  We can use all the help we can get.


View raw message