Re: Categories

------=_Part_8782_5702796.1012524654843
Content-Type: text/plain
Content-Transfer-Encoding: 7bit



Technical -> utilities (grep, awk, sed)
Technical -> editors (emacs, vi)


  DR> and maybe other categories.  The only sticky wicket that needs to be
  DR> decided is if a book can be in a parent and child at the same time, like:

  DR>  Technical -> Programming
  DR>  Technical -> Programming -> Perl

u>hmm, a node only has other nodes or books? u>or could it have both? 

u>i would like to keep nodes either filled u>with books or other
u>nodes. sharing a node bothers me somehow.

nntp.perl.org seems to be down atm, so you get the lovley formating of my web based email.. *shrug*

ok, I can see that format working well, I was designing from a frontpage standpoint rather than an organizational(sp?)

my vote is to make it so a book can't be a member of any child nodes.

I think it works ok to have a node contain both books and sub-nodes, because otherwise the perl heirarchy will have to be so amazingly complex in order to hold everything that it would be almost worthless.  <a href="http://directory.google.com/Top/Computers/Programming/Languages/Perl/?tc=1">an example of this in practice</a>


~Sean
------=_Part_8782_5702796.1012524654843--