Re: Menu & autocollapsing of submenus

[gsstark@mit.edu (Gregory S. Stark)]

So I think the main problem here is that "Net" was a bad idea in the first
place. It's far too vague and doesn't actually say anything about what the
program does.

We already have Web for WWW browsers. 

Remote Login:	rlogin, telnet, ssh, etc.
Chat:		Talk, IRC, Mud clients, etc.
File Transfer:	ftp, scp, rcp, etc.
Mail:		Pine, Mutt, maybe even fetchmail
Dictionaries:	ispell, wordnet, etc.
Debian:		apt, bug, etc.
Help:		dhelp, manual pages viewers, etc.

Note that all of these could, in theory, go in "Net". They all deal with
network protocols in some way. The fact is that on Unix nearly everything does
have network based features, but with few exceptions, programs like ifconfig,
manipulating the network isn't the ultimate goal.

Also, I think we should flatten the hierarchy at least until we know we need
to have submenus. It would make things easy to find than a maze of submenus.
Who's to say what's a "tool" and what's an "app" anyways? 

greg


--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org