On Wed, Aug 29, 2001 at 06:51:29PM -0400, Kirrily Robert wrote:
> On Wed, Aug 29, 2001 at 08:45:34PM +0100, Tim Bunce wrote:
> | On Wed, Aug 29, 2001 at 10:01:07AM -0400, Kirrily Robert wrote:
> | > This seeks reasonable to me, given that Tk:: and Gtk:: and other GUI
> | > toolkits have similar top-level namespaces.
> | >
> | > (Though I do think it'd be nice to group them all under GUI sometime, if
> | > we could ever get all the authors together to do it.)
> |
> | I know it seems tempting, but what significant value would it _really_
> | buy you that the section groupings in the module list don't already provide?
>
> Searchability via m /GUI/ in CPAN.pm
That should also search section groupings. Or at least list the names
of sections that match and how to then search or list those sections.
> Searchability via search.cpan.org
Likewise. But if wanting to explore GUI modules I'd be much more likely
to start by clicking on the relevant section link on the front page.
> Searchability of modules which, for some reason or another, are not in
> the modules list (eg it hasn't been updated recently).
The description of a GUI module should include GUI.
> Easy navigability of a CPAN archive via FTP, or on a CD-ROM.
There is (or should be) a by-section tree just like by-module and by-author.
> That's just off the top of my head. How many more do you want me to
> come up with?
I don't know, but I'm not very convinced.
Thing is, GUI is a too-easy example. There are pleanty of other modules
that cover more than one area of functionality. It would be impractical
to try to put every aspect of the functionality into the module name.
The section groupings in the module list and the module descriptions will
always be needed to provide sufficient information.
Tim.
