--- In [email protected], "Peter Farland" <[EMAIL PROTECTED]> wrote: > > Sorry, that is, this will NOT make it into Flex Builder 3 :) > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of Peter Farland > Sent: Tuesday, December 18, 2007 11:26 AM > To: [email protected] > Subject: RE: [flexcoders] Re: Debugging RemoteClass serialization > [SOLVED] > > > Unfortunately that would involve the compiler scanning all of the > classes (source or swcs) in the project to find [RemoteClass] metadata, > so this will make it in Flex Builder 3. >
Uhm.. I'm a little off topic, but I don't see your point. The compiler, right now, already has to scan *all the other* classes to verify that a particular one is not used, in order to choose to remove it from the SWF if it isn't needed. Mxmlc should simply not perform this additional step when compiling ActionScript classes that has a [RemoteClass] metadata applied. From my point of view, there can only be a performance gain from this behaviour.. This is true unless the compiler actually works starting with the application (and the defined modules) and then compiling all the dependencies it find.. in such case, the "unused" [RemoteClass] classes would never be reached, right. In this scenario, Mxmlc should at least allow to force inclusion of entire packages using its command line switches, instead of single classes only. A sheet in the project properties dialog to allow this configuration, a bit like the modules dialog one, would also be fine ;) It is really ugly to put fake references in my code only to turn off this optimization.. and anyway, it is better to have the compiler scanning all the sources, instead of having me doing the same job manually and writing code to workaround this, isn't it? :) Cosma
