Hello there,
I am sorry I kept silent for some time.
Well, the Sexie project is back, and now I can be proud of a piece of code ^^
Sexie Reloaded (that is, Sexier) has been built while thinking about automation
for build and deployement. Thus, pretty much like Asigen, it does not need to
use the swc workaround anymore.
Yep, you read well : SexieR can now process a source package to generate an
output intrinsic package, exclusion xml or exclusion file.
Well that's not everything. The gui is still to come, but... You allready have
ant Ant Task to process a source folder, here's how it works :
- build.xml -
<taskdef name="sexiePackage" className="org.aggelos.sexie.app.ant.SexiePackage"
classpath="${path.to.sexie}" />
<target name="default" >
<sexiePackage outputDirectory="${basedir}/src" source="${src}"
mode="mtasc" dependencies="${dep1};${dep2}" />
</target>
arguments :
outputDirectory : where the result should be created
source : root of the package to process
mode : mtasc - intrinsic - xml. Default to intrinsic
dependencies : classpathes to include ";" separated
Still, it's a work in progress, I've got much more to do. I plan to have at
least a build a week. Things still to implement (on their way allready) :
- generation from a file with a list of classes. The Library.as should be
created
- management of the #include statement
- finishing the GUI
- refactoring of the good ol' swc code to add it to the current architecture
- comment everything ~_~ (I know, I'm a baaaad bad boy)
current limitations :
- sexier cannot yet process files with an #include statement
- sexier cannot handle multiline function declarations
- swc processing is not implemented yet (use the old sexie if you need it)
Please give me any feedback.
Hope you'll find it useful
Clément
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
