Stefan Matthias Aust wrote:

>  >
>  >Edward P Luwish wrote:
>  >>
>  >> What I do, since I equate documentation with source code, is to select
>  >> the category, class or method I want to document (from any browser), and
>  >> "print it" from the popup menu.  This creates a nicely formatted html
>  >> file that can be viewed (and printed) with any web browser.
>  >At 13:28 12.05.00 -0400, Doug Way wrote:
>
> >Huh, somehow I never noticed this feature.
>
> Me too.  I second the idea that the label should be changed.  I never
> bothered to thing about printing out code so I completely ignored that menu
> item.
>
> Although the output is nice.  Unfortunately, that's nothing I'd compare
> with what JavaDoc is able to create.  First of all, I don't want to see the
> source by default. This also doesn't generate hyperlinks and tabular
> overviews.  Finally, it's uglier than needed because of the
> chunk-format.  I'd agree with Stephan R that we don't need the file-in
> compatibility.

Not very good with pretty print with color either :-(
Some converting is needed.
Karl

>
>
> bye
> --
> Stefan Matthias Aust  //  Bevor wir fallen, fallen wir lieber auf