Re: Peardoc2
| From: | Stig S. Bakken | Date: | Mon, 29 Apr 2002 15:58:02 +0000 |
| Subject: | Re: Peardoc2 | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-5896@lists.php.net to get a copy of this message | ||
On Mon, 2002-04-29 at 16:45, Martin Jansen wrote:
> On Mon, 29 Apr 2002 15:45:14 +0200, Alexander Merz wrote:
>
> >Martin Jansen wrote:
> >
> >> 1.: The structure of "Packages" should IMO better be:
> >...
> >> Otherwise we will have a giantic list of packages on the first
> >> page, which is very counter-productive.
> >This is a render problem. book - part - reference. There is no element
> >between part and reference. A non-render related solution would be to
> >divide the manual into different books:
> ><set>
> > <book>PEAR Introduction
> > <part>general PEAR doc stuff
> > <part>PEAR Core
> > <part>Contributing PEAR
> > <book>PEAR Packages
> > <part>Net_Finger
> > <book>Packages
>
> Why don't you use the same structure as in version 1? It worked
> like a charm there.
>
> >> 2.: Just to get it right: "Core" will now only contain documentation
> >> for PEAR and PEAR_Error, no?
> >
> >I suggest the classes of php4/pear/pear too
>
> Most of the things there don't really fit in a end-user
> documentation, don't you think?
If you mean the installer code, I agree, it's not really "re-useful" for
most people.
- Stig