Thanks Stephen, that did the trick On Mon, Jan 26, 2009 at 4:33 PM, Stephen Gilson <[email protected]> wrote:
> Are you using -doc-sources to reference your source code? Try compiling > it with -doc-classes or doc-namespaces instead, along with setting your > source path. > > > > Stephen > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Rich Tretola > *Sent:* Monday, January 26, 2009 3:13 PM > *To:* [email protected] > *Subject:* Re: [flexcoders] asdoc > > > > col: 1 Error: The public attribute can only be used inside a package. > > > On Mon, Jan 26, 2009 at 3:06 PM, Stephen Gilson <[email protected]> > wrote: > > We use that technique with ASDoc builds all the time. > > > > What is the error that you are getting from ASDoc? > > > > Stephen > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Rich Tretola > *Sent:* Monday, January 26, 2009 2:08 PM > *To:* [email protected] > *Subject:* [flexcoders] asdoc > > > > I have a bunch of classes that are extending from base flex components. > They also all share 5 properties and a few methods. So, rather that adding > the shared properties and methods to each file. I used the old include > "SharedInclude.as"; statement within each class to include an ActionScript > file (not a class). All is happy and all compiles nicely. However, asdoc > doesn't like this approach and pukes on the included properties when trying > to create documentation. Anyone else ever tried something like this? > > > Rich > > > > >
