Hi Igor,
Sorry my mail wasn't really clear.
I've introduced a -rb_export_included_classes <path> switch to mtasc.
Matsc now writes a file with all Class names which were included.
e.g.
ww.map.Map
ww.map.Layer
...
This file can be used to prevent mtasc to compile these classes into
another swf.
My target is to create several small library swfs which can be combined
later using swfmill
or even be loaded at runtime.
So you don't have to write your own exclude file anymore as Mtasc tells
you what is compiled already.
Regards
Stefan
>Hello Stefan!
>
>Sounds very attractive as for me!! :) Could you provide more details how
>your hack works? How to export compiled classes from one SWF to another and
>what MTASC arguments must be used for?
>
>Regards,
>Igor
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
>Behalf Of Stefan Klug
>Sent: Thursday, February 23, 2006 1:07 PM
>To: Open Source Flash Mailing List
>Subject: [osflash] hamtsc export compiled classes
>
>Wheeeha,
>
>I just got Mtasc to compile and did my first steps with OCaml **funky**.
>
>It's now possible to create a file with all classes which were compiled.
>This file is compatible to mtascs -exclude syntax and makes it easy to
>create a dll system
>( I'm currently thinking of a dll system with a tree like structure to
>minimize double loading of classes)
>
>If anybody is interested in the code I'd be happy to share it.
>
>Sorry for mailing list pollution, but I had to tell someone.
>
>Have a good day
> Stefan
>
>_______________________________________________
>osflash mailing list
>[email protected]
>http://osflash.org/mailman/listinfo/osflash_osflash.org
>
>
>_______________________________________________
>osflash mailing list
>[email protected]
>http://osflash.org/mailman/listinfo/osflash_osflash.org
>
>
>
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
