IMO, it depends on how complex. We are looking for folks who are willing to put up with the rough edges and help us make FlexJS strong enough to support your application. It won't be like working with Flex 4.x. There will be lots of bugs and other issues, but we need real world applications in order to find and fix those bugs and issues.
So if you or anyone else reading this is interested, let's find out more about what your app does and requires. Fair enought: 1. Support communication with server-side thru AMF3 (for legacy purpose because change client-side and server-side at once is too much); 2. Support communication with server-side thru REST; 3. Easy to build components like MXML; 4. Easy to install on IDEA IDE like Flex SDK (run 30 scripts and change system variables it's not nice as Flex SDK); 5. Binding and two-way binding easier as Flex. I could mention many other things that is a requirement, however OMHO without a good setup (point 4), many developers will not haven consider give a try. I know that seems lazy but it the true. -- View this message in context: http://apache-flex-development.2333347.n4.nabble.com/The-state-of-FlexJS-tp59948p59955.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
