Hi,
>>> The biggest problem would be to re write parts of the Flex framework that
>>> we used in "Pure AS3".
>>Which part of the framework do you mean? Which the exception of some sample
>>themes and skins all of the Flex SDK is written in AS3.
=>It's not a part, the only thing I want is to create a "AS3 Project"
and use Flex components (Spark, MX, ...) and libraries, that is my request
>>>> This could allow people to use in projects "Pure AS3" with ASC 2.0 and
>>>> Scout easily.
>>JFYI - I've just checked in a change that enables advanced telemetry with the
>>existing ASC compiler.
>>What other features of the ASC 2 compiler do you require that are not
>>currently in old ACS compiler?
=> It's not features that are missing my problem, I have really big
project, so to compile faster is interesting me, and future features.
=> the problem is not Flex, I love the Flex FrameWork, the problem is
Adobe, I think maintain MXML depending to Adobe decisions is a risk for me.
=> Today, I'm have some choices (we create only mobile applications):
- continue like today with MXML and Flex, with high risk of
being abandoned by Adobe and so, don't be compatible with new devices
- use (if possible) the Flex FrameWork in "Pure AS3" mode and
migrate our project to "Pure AS3"
- to abandon Flex and go with Feather UI
- re write everything in HTML5 or Qt project
=> The problem is I don't want to investigate so much time anymore with Flex if
I have not a sustainable vision.
Thanks,
Justin
