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

Request #10812 list-categories and list-category
Submitted: 2007-04-23 17:50 UTC
From: tias Assigned: tias
Status: Closed Package: PEAR (version 1.5.3)
PHP Version: Irrelevant OS:
Roadmaps: 1.6.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 : 30 - 10 = ?

 
 [2007-04-23 17:50 UTC] tias (Tias Guns)
Description: ------------ I'm working on 2 new commands: list-categories and list-category <category>. They are already in the webfrontend, but some more work is needed to put them in Command/Remote.php For release 1.6.0

Comments

 [2007-05-20 00:08 UTC] cellog (Greg Beaver)
have a patch yet?
 [2007-05-28 21:23 UTC] tias (Tias Guns)
Yip, its attached. Two add functionality to REST (1.0 and 1.1) The other one adds functionality to Remote.php The last one patches the Remote.xml file
 [2007-05-28 21:26 UTC] tias (Tias Guns)
Can't attach, too big. You can find the patches at: http://tias.ulyssis.org/patch/pear/listcategory
 [2007-05-29 15:09 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. I've implemented the REST 1.1 functions. REST 1.1 is supported by all channel server code for over 1.5 years, we are not adding hacks to REST 1.0, just error out if the server does not support REST 1.1. Tias: adding new commands is the wrong way to implement this feature. The CLI frontend has absolutely no need for listing categories, you should access the REST directly for the web frontend. The same goes for the other attention on commands - "use the REST, Luke" Take a look at PEAR_Frontend_Gtk2 to see the best practices.
 [2007-05-29 16:57 UTC] tias (Tias Guns)
Hey, Thanks for including some of the code so far, some remarks: 1) REST1.0: There are still a few servers with REST1.0, like: components.ez.no and solarphp.com. Also, pearified.com has some invalid REST1.1 XML files, which means you have to fall back to REST1.0 if you want list-categories to work for it. I've done the effort of writing the code, I don't know if its such a big hassle to include it ? 2) The commands: I figured it would be a great addition to the PEAR CLI to have commands like 'list-categories': the current 'list-all' is very slow and returns waaaay to much data, having slicker commands like 'list-category' could solve this problem.
 [2007-06-01 23:41 UTC] cellog (Greg Beaver)
I've thought about this quite a bit before making a final decision. I will add the REST1.0 stuff As for the commands, my main concern is that the list of commands already scrolls off of the screen. I don't want to add any new commands at this point. PEAR 2.0 will have to fix this up somehow, perhaps with command categories.