Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.32.0

Request #9973 Add a "developing with PEAR effectively" document to the site
Submitted: 2007-01-30 05:02 UTC
From: justinpatrin Assigned: cellog
Status: Closed Package: pearweb
PHP Version: Irrelevant OS: Irrelevant
Roadmaps: 1.9.0    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 11 + 34 = ?

 
 [2007-01-30 05:02 UTC] justinpatrin (Justin Patrin)
Description: ------------ Greg suggested that I write up an article on devloping with PEAR effectively. I've combined some previous writings and added a few more things to come up with some best practices for users when it comes to handling PEAR_Error and I/O. http://pear.reversefold.com/~papercrane/pearDev.txt

Comments

 [2007-01-30 05:03 UTC] justinpatrin (Justin Patrin)
 [2007-02-04 09:09 UTC] davidc (David Coallier)
I remember suggesting that maybe a year or two back but never been adopted. Perhaps (again) a wiki would be good for pear :). If anyone is for it, I can even integrate it I don't mind, would actually be a pleasure.
 [2007-02-04 16:08 UTC] justinpatrin (Justin Patrin)
I agree that a wiki would still be great. Someone did set up a wiki a while ago but it never went live.
 [2007-02-24 15:00 UTC] mj (Martin Jansen)
Have you considered publishing this (or an extended version of it) as an article in one of the PHP print publications? In any case, this is no website bug, so I'm moving this over to the documentation.
 [2007-02-24 16:56 UTC] justinpatrin (Justin Patrin)
Greg asked for this for the website. I have no idea what the print publications are or how I'd get an article into them...
 [2007-02-27 23:45 UTC] cellog (Greg Beaver)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.