Packs are necessary for the exact reason I listed below. Because you can create a class like this:
var obj = new eval("org.actionstep.NSObject")();
How would MTASC ever know to include org.actionstep.NSObject. It's a string!
Scott
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of John Grden
Sent: Fri 3/17/2006 4:42 PM
To: Open Source Flash Mailing List
Cc:
Subject: Re: [osflash] [Flasc] New version of FLASC
yeah, i know all of this:)
So, we're in agreement: providing a CP is simply to say "hey, my classes
start here" - but it does NOT mean that mtasc will recurse/dig into folders
within that CP. Now, maybe I just got screwed up in my testing, so please
set me straight on this - but again, I swear I heard Nicolas say it did NOT
recurse from the cp given.
Why would we have packs then?? Wouldn't it be good enough to point to one
single directory (like you can with the Flash IDE btw) and have it find all
necessary classes? It just doesn't work that way from what I've experienced
and read.
again, leaning on the fact that I'm often wrong the first time, I give way
to any facts you guys can provide ;)
On 3/17/06, Scott Hyndman <[EMAIL PROTECTED]> wrote:
>
> A classpath is the "root" directory for some classes. Any classes in this
> directory will not have packages associated with them. Any classes in a
> subdirectory of the root have dot-separated packages, named the same way as
> the directory structure from the classpath directory. (I'm sure you knew
> some of this, but just to be sure).
>
> You ALWAYS have to include the base classpaths. There's no way around it.
> Otherwise MTASC would have absolutely no idea where to look for classes.
>
> -pack is just a way to ensure a set of classes gets included into the
> resultant swf. Since a class may be used but not necessary referenced by
> name, MTASC would not ordinarily know to include the class. -pack solves
> this by forcing its inclusion into the swf.
>
> Hope this helps a bit,
>
> Scott
>
> -----Original Message-----
> From: [EMAIL PROTECTED] on behalf of John Grden
> Sent: Fri 3/17/2006 4:12 PM
> To: Open Source Flash Mailing List
> Cc:
> Subject: Re: [osflash] [Flasc] New version of FLASC
>
> then why have packs then? i thought a CP was just the same idea as a
> pack.
>
> You point to a directory, it uses what's in that directory, but won't go
> any
> deeper than that.
>
> hence why he states:
> -pack *path* : compile all the files contained in specified package - not
> recursively (eg to compile files in c:\flash\code\my\app do mtasc -cp
> c:\flash\code -pack my/app).
>
> When Nicolas talks about CP's, he doesn't mean recursively - he means you
> have to add all directories:
> -cp *path* : add a directory path to the ClassPath : this is the list of
> directories that MTASC will use to look for .as files. You can use several
> times -cp to add several directories.
>
> I will say, that in trying to figure all of this out with MTASC I saw
> several times where I didn't need to include a CP for some reason. but
> later, when I added a new class to the project, I got an error about
> having
> to include them later on.
>
> On 3/17/06, Scott Hyndman <[EMAIL PROTECTED]> wrote:
> >
> > 1.
> >
> > I don't believe this is correct. I just tried it. I removed all the
> -pack
> > options from the mtasc build file, and it seemed to do just fine
> figuring
> > out what needed to be included.
> >
> > Scott
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED] on behalf of John Grden
> > Sent: Fri 3/17/2006 3:02 PM
> > To: Open Source Flash Mailing List
> > Cc:
> > Subject: Re: [osflash] [Flasc] New version of FLASC
> >
> > ah ok, here's some explanations:
> >
> > 1. MTASC doesn NOT recurse. So you do have to put in each class OR you
> > can
> > specify a package. So, instead of adding a file, add a package. Go to
> > the
> > project/as folder and click ok. Flasc will add this as a new global cp
> in
> > the preferences and use it in your new project.
> >
> > 2. Global class paths in Flasc can be set in preferences. BUT, for a
> > single project to use them, you have to add a package. That's the only
> > way
> > a project knows which cp to include is when you include packages. I
> know,
> > this might seems awkward, but it's the way it is right now and I'm
> totaly
> > open to suggestion on how to make this easier.
> >
> > Mtasc just doesn't recurse like the Flash IDE does - not even -pack
> > recurses. It just uses all the files in that directory.
> >
> > So, if you have:
> >
> > classes/com/blitzagency
> > classes/com/blitzagency/util
> > classes/com/blitzagency/controls
> > classes/com/blitzagency/xray
> >
> > you have to add all those as packages if you want all the files to be
> > included.
> >
> > Now, the good news is, FLASC let's you point to the classes folder and
> > recurses FOR YOU and brings back all the possible packages that have
> > classes
> > in them.
> >
> > Does that help?
> >
> > On 3/17/06, David Rorex <[EMAIL PROTECTED]> wrote:
> > >
> > > Ok, there are some things I cannot figure out.
> > >
> > > First, here is my folder layout:
> > >
> > > project/
> > > project/Project.fla
> > > project/deploy/project.swf -- output
> > > project/as/MainClass.as -- contains as.MainClass
> > > project/as/sim/Class2.as -- contains as.sim.Class2
> > >
> > > Do I have to manually specify every class in the GUI? I just specified
> > > MainClass.as, and it complains that it can't find as.sim.Class2. I
> > > thought mtasc could automatically find nearby classes?
> > >
> > > When I run the batch file with pause, I see:
> > > C:\.....\project\as> ...mtasc.exe...."c:/.../project/as/MainClass.as"
> > >
> > > This seems incorrect, shouldn't it be running from the 'project' dir,
> > > and not the 'project\as' dir? Maybe that's why it can't find
> > > as.sim.Class2? And also, when I have run mtasc via commandline, I
> > > never specify the full path to the class (I would just write
> > > "as/MainClass.as"), but that may be fine.
> > >
> > > ---
> > >
> > > One other problem, I added a global classpath to the Preferences
> > > dialog, but I don't see that classpath anywhere in the .bat file, it
> > > seems to just ignore them.
> > >
> > >
> > > Thanks for the help,
> > > -David R
> > >
> > > On 3/17/06, David Rorex <[EMAIL PROTECTED]> wrote:
> > > > It seems to work pretty well, now that i solved the 'wrong windowswf
> > > > bug', this is very cool.
> > > >
> > > > I have one suggestion: Could you capture the output of the command
> > > > window, and display it in the flash output pane? This would be
> easier
> > > > to use than having to read from the command window, also, it would
> > > > eliminate the problem of the Flash IDE locking up while the command
> > > > window is open.
> > > >
> > > > Thanks!
> > > >
> > > > -David R
> > > >
> > > > On 3/17/06, John Grden <[EMAIL PROTECTED]> wrote:
> > > > > awesome!!!
> > > > >
> > > > > On 3/17/06, l u c h y x <[EMAIL PROTECTED]> wrote:
> > > > > >
> > > > > > Thanks It work perfectlly.!! on XP sp2 spanish. and no alert
> > apear.s
> > > > > > You are fantastic.
> > > > > > I´m posting the update on my blog too.
> > > > > > thanks again
> > > > > >
> > > > > > luchyx from argentina.
> > > > > > http://www.riaevolution.com/blog/
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 17/03/06, John Grden <[EMAIL PROTECTED]> wrote:
> > > > > >
> > > > > > >
> > > > > >
> > > > > > 1. Removed the DLL's from the MXP install
> > > > > > 2. Added option of where to save batch file,
> > > > > > 3. Took out all references to Guy's DLL - uses the MM DLL
> > completely
> > > > > > 4. Should be useable on a mac - but testing is needed for file
> > paths
> > > etc.
> > > > > > 5. Made class file selection a multi-selection list so removing
> > > multiple
> > > > > files is eaiser ;)
> > > > > >
> > > > > > Right now, it should install and work on a mac with the
> exception
> > of
> > > > > running the batch file. In talking with George, we've been told
> > that
> > > > > creating a BASH file (generic text file?) on the mac would be
> > > executable.
> > > > > We're actively looking into getting some help on how we might
> > execute
> > > that
> > > > > BASH file on a mac ;)
> > > > > >
> > > > > >
> > > > >
> > >
> >
> http://mirror1.cvsdude.com/trac/osflash/flasc/browser/downloads/FLASC.mxp?format=raw
> > > > > >
> > > > > > --
> > > > > > John Grden - Blitz
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Flasc mailing list
> > > > > > [EMAIL PROTECTED]
> > > > > > http://osflash.org/mailman/listinfo/flasc_osflash.org
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > l u c h y x
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > John Grden - Blitz
> > > > > _______________________________________________
> > > > > 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
> > >
> >
> >
> >
> > --
> > John Grden - Blitz
> >
> >
> >
> >
> > _______________________________________________
> > osflash mailing list
> > [email protected]
> > http://osflash.org/mailman/listinfo/osflash_osflash.org
> >
> >
> >
>
>
> --
> John Grden - Blitz
>
>
>
>
> _______________________________________________
> osflash mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/osflash_osflash.org
>
>
>
--
John Grden - Blitz
<<winmail.dat>>
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
