Re: future of PEAR

Hi, * Michael Wallner wrote: > Yes there is a standard: Docbook XML, or what are you thinking about > with 'standard' in mind? A kind of templates can be found, too: > http://cvs.php.net/cvs.php/peardoc/en/authoring That's nothing appropriate. > > Provide an "author's SDK", a .tgz or .ZIP with all kinds of > > templates for classes, documentation, perhaps unit tests and a > > skeleton PEAR package, some kind of automatic tools to verify if a > > PEAR package complies to the standards (or complies to the > > standards for PFC etc.). > I think that's easier to say than to do. Regarding the automatic verification I agree (I mentioned this only because it was mentioned in another posting of somebody). > When making docs - I think - it's the easiest way to look how others > have done this before. That's not appropriate. The easiest way (especially regarding the recent PEAR2 discussion) is IMHO to provide access and tools to the developer where he can easily start with. Name it whatever you want - "A dummy's guide to PEAR", "PEAR SDK", whatever. > Questions about Docbook can be most probably best answered here: > http://www.oreilly.com/catalog/docbook/chapter/book/docbook.htmlbÔo×í > QOÖ‰qภI know how to write docbook (I'm using XMetal for that), but that's not the point here. -- Schnellanbindung an 350 Standorte?! CaseStudy anfordern unter: transaktionsserver@emailseminar.de ThinkPHP / rent-a-phpwizard bjoern@thinkphp.de Sedanstraße 27 Tel: 0931 / 78 43 804 97082 Würzburg Fax: 0931 / 78 43 795 http://www.thinkphp.de/ http://www.rent-a-phpwizard.de/