On 6/3/16, 11:39 AM, "Peter Ent" <p...@adobe.com> wrote:
>Thanks for checking out the article. Alex Harui is working on such a >thing. Perhaps when he has a moment he can fill us in on the details. Well, I'm trying to see if we can run MX and Spark on top of FlexJS, but it is going to be fat and slow because Flex is, compared to raw HTMLElements, fat and slow. I'm not sure it will compare well with ReactJS. The goal of that effort is to reduce migration pain for existing Flex code bases. The ReactJS experiment is more about whether we can capture fans who are developing new apps with ReactJS and running into any pain points along the way. I'm interested in what Carlos and others would expect from FlexJS in order to be a "better way" of developing web apps. That's the approach we have taken with CreateJS and Cordova: the wiki pages Peter wrote try to illustrate how Apache Flex makes CreateJS and Cordova app development even more productive. We are not trying to take customers away from their platforms, just be seen as a productivity enhancement. It looks to me that ReactJS is also an attempt at productivity enhancement. It doesn't appear to have a component set of its own. You can just use raw HTML tags or use Jquery and Bootstrap and other frameworks. I think we have a pretty good first approximation of raw HTML tags already in the Basic component set for FlexJS. If folks know of good "Getting Started" examples for ReactJS, we can see if we have the equivalent widgets in FlexJS. IMO, what MXML and AS provide over JSX is better productivity through better strong-typing at edit/compile time. And we have states and data binding to do the "react"-ing. Or are we missing what such an "integration" with ReactJS would look like? -Alex
