Hi again ! I am going on my investigations, and found out another partial solution : ASDOC only generated documentation for public methods... As my MXML classes declare most of the time private methods, nothing appears in the documentation. Is there a way to force ASDOC documenting private methods as well ? Last question, but not least : how do I include the general description of my MXML classes in the documentation ?
Thanks for your help Ben --- In [email protected], "Benoit Thiebault" <[EMAIL PROTECTED]> wrote: > > Hi again ! > > I finally found how to (partially) solve my problem ! > In ASDocAntTask, there are two files the user has to fill in : the > build.xml file and a properties file. In the properties file, you > define, for example, the name that you want to appear in the browser > window... And as my project is French, I used a French special > character é... which messed everything up... > So finally, I got rid of this problem... But don't leave now : I have > another one for you : > > I have now a great documentation, but nothing about mxml files ! > The class is in the list of files, but ASDOC somehow misses all my > ASDOC comments in the <mx:Script> tag... > > How can I solve this problem ? > > --- In [email protected], "Benoit Thiebault" <neopium@> wrote: > > > > Hi everyone, > > > > I'm also trying to use ASDOC and encounters problems as well. > > I'm not using command line, but Eric Feminella's ASDocAntTask > > > <http://www.ericfeminella.com/blog/2007/06/07/asdocanttask-project-for-e\ > > clipse/> . I have a strange error message : Impossible to open the > > document, Invalid byte 2 of 3-byte UTF-8 sequence. It happens for a > > whole bunch of files in the asdoc/templates directory, including the > > asdoc-util.xsl file. > > Do you have any idea what to do in that case ? > > > > Thanks > > > > Ben > > > > > > --- In [email protected], "Christophe Herreman" <lists@> > > wrote: > > > > > > have you tried using -doc-sources "path/to/project" instead of > > -source-path? > > > > > > AFAIK you don't need to specify the libs you're using then. > > > > > > regards, > > > Christophe > > > > > > --- > > > Christophe Herreman > > > http://www.herrodius.com > > > http://www.pranaframework.org > > > > > > 2007/12/7, Rico Leuthold rleuthold@: > > > > > > > > I already have the swc in the source-path. I'm running asdoc from > > the > > > > root of the project folder like this: asdoc -source-path . > > -doc-sources. > > > > > > > > thanks_rico > > > > > > > > On 06.12.2007, at 16:14, Muzak wrote: > > > > > > > > > Add the location of the flexlib swc to the -source-path parameter > > list > > > > > > > > > > asdoc -source-path "path/to/project" "path/to/flexlib" ... > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > From: "rleuthold" rleuthold@ <rleuthold%40access.ch>> > > > > > To: [email protected] <flexcoders%40yahoogroups.com>> > > > > > Sent: Thursday, December 06, 2007 12:02 PM > > > > > Subject: [flexcoders] AsDoc and libraries problem > > > > > > > > > > > > > > > Hi, > > > > > > > > > > I want to run asdoc (from command line) for my project, but always > > > > > getting an error cause of > > > > > the flexlib components I'm using (Error: Could not resolve > > > > > <flexlib:SuperTabNavigator> to a > > > > > component implementation). Does somebody have an idea how to > > > > > exclude the flexlib > > > > > components when running asdoc ? > > > > > > > > > > thanx_rico > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Flexcoders Mailing List > > > > > FAQ: > > http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > > > > Search Archives: > > > http://www.mail-archive.com/flexcoders%<http://www.mail-archive.com/flex\ > > coders%25> > > > > > 40yahoogroups.com > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > > > ................................... > > > > Rico Leuthold > > > > rleuthold@ <rleuthold%40access.ch> > > > > +41(0)76 512 05 50 > > > > ................................... > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Christophe Herreman > > > http://www.herrodius.com > > > http://www.pranaframework.org > > > > > >
