incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frédéric THOMAS <webdoubl...@hotmail.com>
Subject Re: New Spark components
Date Sun, 16 Dec 2012 02:31:45 GMT
I still get the problem but I've been able to use the compile-config.xml to 
simply the build.xml, it was enough to add out of the compiler tag :

<include-namespaces>
     <uri>http://flex.apache.org/experimental/ns</uri>
</include-namespaces>

I guess, it's missing in the apache lib too, that the reason why it does not 
compile what there's in the manifest file and run without errors:

<include-namespaces>
     <uri>http://flex.apache.org/ns</uri>
</include-namespaces>

- Fred

-----Message d'origine----- 
From: Frédéric THOMAS
Sent: Sunday, December 16, 2012 2:44 AM
To: flex-dev@incubator.apache.org
Subject: Re: New Spark components

@Justin,
The compile target of the apache build.xml is simpler because it deleagates
the detail of the config to compile-config.xml, I tried to do so but I ran
into the problem that the manifest.xml hasn't been taken in account and had
to add manualy all the classes to ExperimentalClasses.as to solved this
issue and been to the same point I'm at the moment with the
<s:SolidColorStroke>.

BTW, if you look at the catalog.xml of the apache.swc, there's nothing
inside relative to the exposed classes, then I'm not sure the swc exposes
any classes.

- Fred

-----Message d'origine----- 
From: Justin Mclean
Sent: Sunday, December 16, 2012 2:16 AM
To: flex-dev@incubator.apache.org
Subject: Re: New Spark components

Hi,

The compile target is looking a bit too complex than needed, for instance if
you look at the apache build.xml one (which relies on mx classes) it's much
simpler. It's it perhaps just the order in which compile targets  are
compiled?

Thanks,
Justin


Mime
View raw message