Thank you for the reply, Alex. >Do you mean the mx UI widgets like mx:TextInput? Can you provide a list >of which mx classes you are currently using?
The app I am tasked with converting essentially uses a large amount of classes from mx.binding, mx.collections, and mx.controls. So yes, classes like mx:TextInput, but also a wide range of other classes: the app is so large that I'd say a majority of the MX library is used. Here is the workaround I've proposed: - Create an ActionScript library project that contains all of the mx classes from the mx library, and behaves just as the mx library does in the original FlexSDK - Include this ActionScript library project in the app's dependencies, so that when I try to compile it with FlexJS, the missing MX class errors are resolved because this ActionScript library has the definitions for all the mx classes that were previously missing - Because FlexJS essentially converts AS->JS, the code should convert and produce some usable level of output Of course, MX tags in .mxml files will have to be dealt with, but am I off track in thinking this is a possible workaround? Thanks, ~ Luke -- View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Using-MX-functions-in-a-FlexJS-project-tp49669p49705.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
