On Thu, Feb 20, 2003 at 11:24:33AM +0100, Marcelo E. Magallon wrote: > This means you parse all the menu entries, and then apply selectors to > decide which entries go in which menus.
Right, yep. > What I am missing here is the ability to merge small menus into its > parents. For example, given this: > > > Tools/ > Clocks/ > Asclock > Archive Generator > Search Tool > > "menu" will merge Asclock back into "Tools" because the "Clocks" > submenu is too small. You can see it from another POV: Asclock is > initially in the Tools menu, and has a "hint" named "Clocks". Iff > there's at least a certain number of menu entries with the same > "Clocks" hint, they will be grouped in the "Clocks" submenu, otherwise > they will be left in tools. This way you can avoid creating large > menus by creating deeper hierarchies and you avoid deep hierarchies of > sparse menus. Ah, I see. That should be reasonably straightforward to implement, just a <MergeIntoParentIfSmallerThan>5</MergeIntoParentIfSmallerThan> or something along those lines. Havoc
