Stefan Hundhammer wrote: > On Monday 26 November 2007 15:50, Stephan Hegel wrote: >> grapics tablet and mouse should have it's own entry point in >> the hardware section like printers and scanners. > > That's one problem we have. On one hand, we'd like to consolidate modules > with > similar tasks into one. This avoids cluttering the control center with lots > of entries. > > On the other hand, it's sometimes not obvious for users where to find any > specific module or setting. This is where having somewhat redundant entries > might be handy. > > This is why we need some different means of navigation. Even if that means > just having a very much advanced search facility (the current search only > searches module name and summary - not very much to get good results from). > > Maybe something in the way of tag clouds.
My humble suggestion is that you don't really need any new technology (although it might also provide some benefit). What you do need - IMHO - is a good set of design rules and the will to implement/enforce them. Taking Stephan's example, a design rule that said 'every hardware device should have an entry in the hardware section' [and it may have other entries elsewhere] would be sufficient, if implemented. Search would presumably work sufficiently well as is if there was a design rule 'all keywords and tags must be listed at the end of the module summary'. The latter rule seems to me perfect to be implemented by the community. List all the summaries on wiki pages and let the community add keywords until they're happy. Then import them to YaST. For that matter, one or more revised YaST menu designs (with multiple entries, i.e. a lattice) could be prototyped as wiki pages. Then people could discuss actual designs and on a much faster cycle than the YaST release cycle. Of course, the design rules could be published on the wiki as well. Go to it folks! Cheers, Dave -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
