>I'm going to leave the code in the spark branch for now and not merge it
>into develop until we see what kind of response we get on this thread.
The main reason why I'm stick with Flex is because of its productivity.
We're able to create simple and complex apps in a very fast way cause of the
co
On 9/22/16, 11:41 AM, "PKumar" wrote:
>Great News Alex, now FlexJS will be backward-compatible and great
>milestone
>in converting existing Flex application to FlexJS.
Hi Prashant.
To be clear, FlexJS may not ever be fully backward-compatible. FlexJS is
relatively backward-compatible today
Great News Alex, now FlexJS will be backward-compatible and great milestone
in converting existing Flex application to FlexJS.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FLEXJS-FALCONJX-News-on-the-Spark-like-component-set-tp52004p55267.html
Sent from
An update:
After 9 months of fiddling, I finally got a "Hello World" up and running
using MX components. The app is essentially:
http://ns.adobe.com/mxml/2009";
xmlns:mx="library://ns.apache.org/flexjs/mx"
xmlns:js="library://ns.apa
Amazing. When FlexJS started, the key mantra was always go for a new
framework without looking back.
I continue thinking that trying to compile old Flex applications with
FlexJS is science-fictions...but now, with the progress
that Alex report...maybe it could be possible in part.
Great work Alex!
Sounds like great progress.
-Mark
On Mon, Mar 28, 2016 at 5:37 PM, Alex Harui wrote:
> Hi,
>
> As you may know, I've been exploring what it would take to create a set of
> components for FlexJS that more closely match the Spark (and MX) APIs from
> the regular Flex SDK.
>
> Today, I reached an
Man, I would have never guessed my little tissy about FalconJS and just
starting FalconJX would have got to this point that FlexJS is with all the
different outputs and things being compiled with it and how you guys are
not even writing js anymore, giving you time to do stuff like this. :)
I will
