Sorry, after I read my post I didn't follow it either. :P
Basically, I was thinking you could put a private function in your classes that tells if it is being included. Within that function it checks the calling class to see if a private var is present (IE: the classes you control WILL have this var because you put it there.)
If the var is not present, exclude the class.

Probably not what you need at this point after reading your further posts, but wanted to explain myself.


Karl


On Apr 13, 2010, at 10:21 AM, Merrill, Jason wrote:

Sorry, I didn't follow that at all.  AFAIK, ASDoc looks for any imports
in your classes and tries to compile those imported classes as well.


Jason Merrill

Bank of  America  Global Learning
Learning & Performance Solutions

Join the Bank of America Flash Platform Community  and visit our
Instructional Technology Design Blog
(note: these are for Bank of America employees only)






-----Original Message-----
From: flashcoders-boun...@chattyfig.figleaf.com
[mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Karl
DeSaulniers
Sent: Monday, April 12, 2010 11:24 PM
To: Flash Coders List
Subject: Re: [Flashcoders] ASDoc & third party libraries

Maybe build a function that controls the class hierarchy
and in the classes you control, set a specific variable
that gets read with this function and makes sure that if the variable
is not present,
to exclude that classes information in any calls from third party
classes that don't have that variable in it.

Karl


On Apr 12, 2010, at 10:14 PM, Ktu wrote:

I'm assuming you've already googled it, and that your google foo is
strong
because I did not search.

If there doesn't seem to be a way to do it there is the annoying way:
copy just the files you want ASDoc'ed into a different directory...

I've done it before for its simplicity, but not a great long term
solution

Ktu

On Thu, Apr 8, 2010 at 10:30 AM, Merrill, Jason <
jason.merr...@bankofamerica.com> wrote:

Those of you who use ASDoc I'm sure have come across this before.
If you
use FlashDevelop and ASDoc - then even better as that is my setup.

How do you handle running ASDoc on a Flash or Flex project where
you are
also using other third party libraries?  If you run ASDoc on a project
that uses a third party library like Greensock's TweenLite or
Papervision3D, as I am, you can get all kinds of compiler errors
because
it tries to include those in the documentation as well (since they are
imported into your classes), and those are not necessarily set up for
ASDoc.  I know in FlashDevelop, the Actionscript Documentation
Generator
has a field for classes to exclude - but it would be impossible to
list
out all those third party classes - is there a way to exclude an
entire
package?

Thanks,

Jason Merrill

Bank of  America  Global Learning
Learning & Performance Solutions

Join the Bank of America Flash Platform Community
<http://sharepoint.bankofamerica.com/sites/tlc/flash/
default.aspx>   and
visit our Instructional Technology Design Blog
<http://sharepoint.bankofamerica.com/sites/SDTeam/itdblog/
default.aspx>
(note: these are for Bank of America employees only)






_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Karl DeSaulniers
Design Drumm
http://designdrumm.com

_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Karl DeSaulniers
Design Drumm
http://designdrumm.com

_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Reply via email to