Re: Category question

I'm -1 for packages in multiple categories. It does cause hierarchy confusion. However, I think what we're talking about here is more of a "trove" category style grouping for search and browse capabilities. For example, consider a package that does rdate stuff. Logically, *I* would choose to put this under Net_RDATE because it's a network function. But it's also a date/time package. I think the package should remain under Net alone, but it could be "categorized" in both networking and date/time categories. So leave the category HIERARCHY the way it is and put packages where they fit best, but add a new field for category (probably called something else) that can be browsable as well. Then, I could search for all results in the Date/Time category, and I'll see both a Net_RDATE package and a Date_Lexical package. -eric On Tue, 20 May 2003, Martin Jansen wrote: > On Tue May 20, 2003 at 10:0750AM +0200, Tobias Schlitt wrote: > > I disagree with that. Having multiple categories for a package will only raise > > the complexity of the system... Think about having most packages in 3 or 4 > > categories... This would raise the number of entries in the system to 3 or 4 > > times mor than their are today... > > If "system" is equivalent to the package database for you, you are > absolutely wrong. > > -- > - Martin Martin Jansen > http://martinjansen.com/ > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >