Kessler CTR Mark J wrote > the ability to compile it using our existing spark based projects without > having to having to create hundreds of JS beads / customizations. > Understandably heavier, but compatibility is more important.
An effort is underway to create a component set that bakes in more beads and reduces code verbosity. I don't think you can expect complete backwards compatibility anytime soon though. When migrating, one thing you can do that will help you reduce customization is to create your own app specific component set that bakes in the beads you actually use. Then you can replace Spark components with your own components and the code ends up looking quite similar to what it was. Kessler CTR Mark J wrote > The only selling point to me for converting to FlexJS would be that I > could cross compile Adobe Air apps and FlexJS. Out of curiosity, do you mean cross compiling specifically to Adobe AIR, as opposed to, for example, Cordova? -- View this message in context: http://apache-flex-development.2333347.n4.nabble.com/FlexJS-Some-things-still-missing-ni-FlexJS-tp57985p58395.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
