[osflash] FAR was [Hacked MTASC: ask for new feature]
Igor V. Sadovskiy
isadovskiy at gmail.com
Tue Jan 17 10:07:46 EST 2006
Just one more idea.
I think it also will be very useful to have "-rb_include_package <package>"
option in addition to "-rb_exclude_package <package>". It will be very
comfortable to create DDLs.
For example, I'm using AsWing in my project. Extra compilation time for
compile only used AsWing classes every time takes about 20-30 seconds for me
(using MTASC). So I'd like to create a DLL and place all used "org.aswing.*"
classes to. Later I could load this DLL in runtime or import using swfmill.
But to create such DLL now I need to list all AsWing classes. I need to keep
this list alive and revisit it every time I'm adding or removing some AsWing
class from my sources. Also I don't want to create DLL contained all AsWing
stuff to omit list revisiting (it could be too heavy).
So having "-rb_include_package <package>" option I could create special ANT
task and run it only if I started to use new class from AsWing framework. It
will create DLL for me contained only classes used in my project. And I
don't need to recompile all sources anymore after any tiny changes in my own
What do you think about?
From: osflash-bounces at osflash.org [mailto:osflash-bounces at osflash.org] On
Behalf Of Simon Wacker
Sent: Tuesday, January 17, 2006 4:20 PM
To: Open Source Flash Mailing List
Subject: Re: [osflash] FAR was [Hacked MTASC: ask for new feature]
it is definitely possible to do this in ant, but it is much more
convenient to use if you do not have to do it, but let the compiler do
the job for you. ;) (and let's not forget about the programmers that do
not use ant)
Ralf Bokelberg wrote:
>Yes, that's what i understood also.
>But i wonder, why we should do it inside MTASC, when we can do it in ant
>also? Couldn't we add a dependent target, which unzips a library.zip and
>adds the directory to the classpath of mtasc?
>Carlos Rovira wrote:
>>Ant would be useful to package the classes into a FAR file, but I think
>>that Igor wants HAMTASC recognize that file and be able to asimilate it
>>(I suppose hamtasc must unpack and process the files inside it)
>>If not, please Igor, give your vision
>>FAR file would be a great addition to our arsenal ;)
>>2006/1/17, Ralf Bokelberg < info at bokelberg.de <mailto:info at bokelberg.de>>:
>> Hi Igor,
>> sounds interesting.
>> If i would implement it, i would unpack the zip into a temporary
>> directory and add the name of the newly created directory to the
>> classpath. I wonder, if this can't be done more easily with Ant?
>> Igor V. Sadovskiy wrote:
>> > Hello Ralf.
>> > I'd like to ask you about adding new feature to the MTASC. It's FAR
>> > (Flash Archive) support. FAR is just like a JAR in Java. It
>> > archived AS sources and could be used as element of the
>> classpath. To my
>> > mind it will be great if MTASC and most of well-known IDE
>> supports it. I
>> > could place all third-party libraries to FAR file so my project
>> > quite compact and portable. Libraries packed to the archive could
>> > easy shared between projects, easy added to the CVS. Library
>> > control will become really easier. It even will be possible to
>> use Maven
>> > with library repository to build Flash applications.
>> > I already talked with some peoples from OSFlash about (Simon
>> > Carlos Rovira and other) and they found this idea interesting too.
>> > soon as this feature will be implemented we could push this idea
>> to the
>> > flash community. I think all will find FAR useful. Also we will
>> ask for
>> > FAR support by the top used IDE. I think it won't be a big issue to
>> > implement this feature in some IDE.
>> > So what do you think about? Could you add FAR support to the
>> Hacked MTASC?
>> > Regards,
>> > Igor
>> osflash mailing list
>> osflash at osflash.org <mailto:osflash at osflash.org>
>>::| Carlos Rovira
>>osflash mailing list
>>osflash at osflash.org
>osflash mailing list
>osflash at osflash.org
osflash mailing list
osflash at osflash.org
More information about the osflash