Yes, of course, intrinsic headers are another way to resolve compile time issue. But appropriate suitable for me tool (SexieR) was announced only today ;) And to my mind it's always better to have complete tool arsenal to resolve some issue using your favourite or desired way. And it still doesn't resolve compilation necessary sources to the DLL issue.
I will check the exact size of the complete pure AsWing binary code. Regards, Igor -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sonke Rohde Sent: Tuesday, January 17, 2006 6:11 PM To: 'Open Source Flash Mailing List' Subject: Re: [osflash] FAR was [Hacked MTASC: ask for new feature] I already got the issue but you spoke about the problem with the compiletime while including the complete code and I liked to show another solution. Btw: How big would an aswing-code.swf be? Cheers, Sönke > Hello Sonke. > > The issue is not in excluding classes from main application, > but in creating > DLL contained only necessary (not ALL) classes. I'm using > about 30% of the > AsWing's capabilities now. So why I need to compile another > 70% to my DLL > which will increase my binary's size on 70%? > > Of course, for some purposes it will be better to have > COMPLETE library > compiled to the DLL. And we already have suitable tools for. > But what's the > easiest way now to create DLL contained only required sources > (referenced > from my main application)? > > Igor > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Sonke Rohde > Sent: Tuesday, January 17, 2006 5:46 PM > To: 'Open Source Flash Mailing List' > Subject: Re: [osflash] FAR was [Hacked MTASC: ask for new feature] > > Hi Igor, > Why don't you compile your project with AsWing > instrinsic-classes and load > and swf which all AsWing-Code before loading your content.swf? > Intrinsics compile lightspeed and this should save your 20-30secs. > > Cheers, > Sönke > > > 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 > > sources. > > > > What do you think about? > > > > Regards, > > Igor > > > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] 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] > > > > Hi Ralf, > > > > 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) > > > > > > Greetings, > > Simon > > > > 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? > > >Cheers, > > >Ralf. > > > > > >Carlos Rovira wrote: > > > > > > > > > > > >>Hi Ralf, > > >> > > >>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 ;) > > >> > > >>Cheers, > > >> > > >>C. > > >> > > >> > > >>2006/1/17, Ralf Bokelberg < [EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>>: > > >> > > >> 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? > > >> > > >> Cheers, > > >> Ralf. > > >> > > >> 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 > > contains > > >> > 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 > > >> becomes > > >> > quite compact and portable. Libraries packed to the > > archive could > > be > > >> > easy shared between projects, easy added to the > CVS. Library > > version > > >> > 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 > > Wacker, > > >> > Carlos Rovira and other) and they found this idea > > interesting too. > > As > > >> > 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 > > >> [email protected] <mailto:[email protected]> > > >> http://osflash.org/mailman/listinfo/osflash_osflash.org > > >> > > >> > > >> > > >> > > >>-- > > >>::| Carlos Rovira > > >>::| http://www.carlosrovira.com > > >> > > >> > > >>------------------------------------------------------------ > > ------------ > > >> > > >>_______________________________________________ > > >>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 > > > > > > > > > > > > > > > > -- > > Simon Wacker > > www.simonwacker.com > > www.as2lib.org > > www.hq-heilbronn.de > > www.flik-flak.de > > > > > > _______________________________________________ > > 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 > > > _______________________________________________ > 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
