[ATTENTION] pearweb *major* useability issues
| From: | Davey | Date: | Sat, 12 Jul 2003 02:15:39 +0000 |
| Subject: | [ATTENTION] pearweb *major* useability issues | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-18185@lists.php.net to get a copy of this message | ||
OK, this is very confusing to me, I'd hate to see what newbies will make of it.
We have this situation:
A userland implementation of SOAP, with no documentation
A C extension implementation of SOAP, with full (seemingly) documentation
The problem is, that the userland implementation has plenty of releases and downloads, whilst the C extension has *no* releases.
This creates the impression that there is only one package (which is the userland one), and that the docs for it are those for the C extension. You see the problem?
We *really* need to implement some sort of website notification of which packages are PECL and which are PEAR. We should either do this *very* abruptly by seperating them in the package list as it is in the documentation (i.e. the Package Browser page has two seperate set of lists, one for PEAR and one for PECL) or slightly more transparently (and this idea I prefer), put the little PEAR/PECL buttons (the 88x31 images) in the Package Information box... we also desperately need links from package pages to documentation... why hasn't this happened yet? I will take a look at the pearweb code next week to see about getting patches for both of these things out the door.
Anyone else have opinions on these matters and/or patches? :)
- Davey