Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!pt.cs.cmu.edu!andrew.cmu.edu!eb1z+ From: eb1z+@andrew.cmu.edu (Edward Joseph Bennett) Newsgroups: comp.sys.mac.system Subject: Re: System 7 talk: Hierarchial Apple Menus Message-ID: Date: 14 Jun 90 13:38:50 GMT References: <68207@cc.utah.edu> <41795@apple.Apple.COM>, <14112@burdvax.PRC.Unisys.COM> Organization: Class of '91, Carnegie Mellon, Pittsburgh, PA Lines: 29 In-Reply-To: <14112@burdvax.PRC.Unisys.COM> >>You don't turn them on with a silly checkbox somewhere, though. You turn >>them on by creating a sub-folder in the apple folder and sticking stuff in >>it. The name of the sub-folder is the menu-item that roots the hierarchical >>menu, and the stuff in the folder is on the menu. Then you make sure you >>only allow one level of hierarchical menu to keep people honest. >But how do you "only allow one level of hierarchical menu"? Do you >disallow folders from being nested more than one deep? Or if not, >what do you do when they are more deeply nested? I also agree that this is a good idea. But your original intention was to allow users to intuitively configure it how they wanted. If a user wants more than one level, then why not, you can limit yourself to one if that's what you want or zero if people don't want hier menus at all. So that solves both problems in an intuitive manner. I hope someone at Apple is reading. Another observation: The alias files (and can you also make alias copies of folders?) If so that could radically change the concept of folders being nested hierarchially all together. You could make a system of links to folders that would be similar to linking cards in a hypercard stack. Ed