A beginner question - in regard to Terry's point about the layering of the SDKs over the last available Flex SDK from Adobe, I'm not quite clear how additional capabilities in flash player are added to the apache flex development environment. For instance, the Worker class is included in flash player 11.4, and Adobe Flex 4.7 has full support of flash player 11.4. As the Apache Flex SDK is overlaid on 4.7, how does a future flash player update, such as an addition of a Worker1 class, become accessible to an apache flex developer?
To Terry's other point, it seems that he is implying that there isn't complete accountability in testing for features. Is anyone working on test reports, or requirement driven verification? Third, do you guys recommend we go with 4.7 for a production update, or do you feel confident in the latest releases? Is there a quantitative measure of confidence, ie code coverage, 97% passing, etc. Thanks, looking forward to getting more involved. On Feb 18, 2013, at 6:38 PM, Justin Mclean wrote: Hi, > In the time since, I, like I presume most, have been waiting to see whether > or not we can get back to that state of affairs using the Apache Flex SDK > with the most current AIR SDK layered from Adobe. Our current understanding > is that yes, we can 'sort of try it', but because the new AAC2 Compiler > cannot handle our Spark Componentry when injected via MXML, we really are not > yet back to square one. As far as I can tell, the same ambiguity now exists > with regards to Workers. As far as I'm aware the new compiler is not required to use AS workers. AIR 3.4 and 3.5 work well with Apache Flex and I tried out AIR 3.6 the other day (nothing complex however). What exactly is your problem with AIR 3.6 and ApacheFlex? Thanks, Justin
