[mtasc] Has anyone fixed the MM componentssothey cancompileinMTASC?

[Carl-Alexandre Malartre]

I too would really like to compile the framework natively.

The thing is, if I'm doing that job, how can I share it?

Any tool available to share diffs?

Carl

-----Message d'origine-----
De : mtasc-bounces at lists.motion-twin.com
[mailto:mtasc-bounces at lists.motion-twin.com] De la part de Nicolas Cannasse
Envoyé : 10 août 2005 03:44
À : MotionTwin ActionScript2 Compiler List
Objet : Re: [mtasc] Has anyone fixed the MM componentssothey
cancompileinMTASC?

> > When -mx is turned on, components code are not typed but they're still
> > parsed.
> > You shouldn't get any error when using -mx, but there will still be type
> > checks about how you're using the components (calling unexisting
> > methods,...). That's why -cp is needed.
>
> I have extended a few of the components to add some simple functionality
> so I have a class mx.controls.MyList.  When I add the -mx all the MM
> errors do go away, but does that mean my extended class won't be
> compiled?

Yes. Since it's part of the mx.* package, it will be skipped as well as
other components.

> For me, in the end it doesn't really matter because I have
> all the components loading via runtime shared loading so I will never
> lose any functionality (assets file is compiled with MMC).
>
> The bottom line for me though is that (IMHO) the MM classes *should* be
> able to be compiled normally with mtasc so that you wouldn't even have a
> need for the -mx flag.  At the end of the day the -mx flag does its job,
> but for me it's just a matter of style.  I have fixed a number of errors
> in the MM classes but I'm not even sure if they are correct since some
> of them are quite strange.  So I'm just wondering if someone has already
> gone through the process and fixed all the errors.

I tried a few months ago and stopped when the Flash Player was *crashing*
and I couldn't find how the code generated by MTASC was different from the
code generated by Flash IDE. Since then, there's been several bugfixes in
MTASC, so it might be possible to compile mx components "natively". However
before it is needed to fix several problems in components sources. It's
pretty easy to do if you have time.

Nicolas


--
MTASC : no more coffee break while compiling