It is possible to take the generated ActionScript, do some editing, rename
some files and build an AS-only application from it. But you'd better be in
maintenance mode because you will be giving up lots of things the MXML
compiler does for your convenience such as:
-compiling {} databindings
-setting up RSLs (I think)
-figuring out which CSS type-selectors go in the SWF
-dealing with [MIXIN] classes
-dealing with [REMOTECLASS] metadata
-etc.
Justin's example below won't actually work because UIComponent expects a
SystemManager as the root of the SWF. You need to add [FactoryClass]
metadata, and even then, the CSS for the Label and other components won't
get included as AS-only projects don't process CSS.
If you build from the generated AS, then any change you want to make to
binding or CSS needs to happen in the output code which is pretty hairy,
instead of the much more easy to read source MXML or CSS.
Yes, we all want faster compiling. Eventually Falcon will replace MXMLC as
the Flex compiler and then you will get most of the speed benefits from
ASC2.0 (if any) and still be able to work with MXML. Be patient, we will
get there.
FWIW, making AS-only apps easier to write is somewhere on the list for the
new FlexJS framework.
On 4/12/13 4:59 AM, "Justin Mclean" <jus...@classsoftware.com> wrote:
> Hi,
>
>> =>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
>
> Something like this perhaps?
>
> package
> {
> import spark.components.Application;
> import spark.components.Label;
>
> public class ASApplication extends Application
> {
> var label:Label = new Label();
>
> public function ASOnly()
> {
> label.text = "Hello";
> addChild(label);
> }
> }
> }
>
>
>> => It's not features that are missing my problem, I have really big project,
>> so to compile faster is interesting me, and future features.
> Do you know that ASC 2 will be faster? For instance Spark was a lot slower
> than mx when initially released.
>
> Have you actually tested it's faster? I've not done any tests so have no idea
> if it is or isn't.
>
>> => 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.
> It's up to Apache Flex to maintain MXML I think it's fairly clear that Adobe
> will put minimal effort in MXML going forward. That being said they have
> publicly stated that they will do better with the 3.8 AIR release and support
> Apache Flex in the 3.8 release candidates.
>
>> => Today, I'm have some choices (we create only mobile applications)
> Not knowing your application(s) I can't offer any advice there, but moving to
> another development platform is going to be a large amount of work.
>
> Thanks,
> Justin
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
