From kde-core-devel  Tue May 03 15:26:04 2005
From: Fred Schaettgen <kde.sch () ttgen ! net>
Date: Tue, 03 May 2005 15:26:04 +0000
To: kde-core-devel
Subject: Re: [another PATCH]: Kicker find as you type
Message-Id: <200505031726.04789.kde.sch () ttgen ! net>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=111518813226218

On Tuesday, 3. May 2005 16:56, Dominik Seichter wrote:
> Am Tuesday, 3. May 2005 16:45 schrieb Tom Karasek:
> > well - *searching* a menu for it's contents only shows that there is a
> > problem with the menu in general: the lack of organisation and the
> > crowdedness (uh, does this word really exist?) - but this is solved in
> > well organised kde-centric distributions like mandrake.

You can fix a bad structure, but some people simply do have lots of 
applications installed. Then you only have the choice between flat or deep 
hierarchies, but the information must be somewhere. How are you going to 
solve that?

> > also, this feature *will* be difficult to use, since you (a) have to be
> > careful not to click outside of the k-menu (otherwise it will close
> > itself), (b) you introduce a mix of menu (k-menu) and textarea (for
> > searching).

(a) That's how a works like and nobody complains about it. And it certainly 
won't happen while typing something in the search field.
(b) why is this bad in this case? Does it lead to unexpected behavior?

> > however, i agree that there is a need to find applications sometimes. my
> > quick ideas: (a) provide a kio-slave (e.g. app: "word") inside konqueror.
You must be joking. 
A kioslave is about the worst user interface kde has to offer. The only reason 
it is abused so often is because it's the easiest way to present a 
hierarchical structure without having to care about a proper user interface 
yourself and because they are reachable in file dialogs.
I'm one of the wrongdoers myself with the bluetooth kioslaves, and I deeply 
regret this decision sometimes.

> > (b) insert an entry inside the context menu of the k-menu (e.g. something
> > like "search for applications...") or inside the k-menu itself (e.g.
> > beneath "run command..."). this would open a separate window (e.g. a
> > special
> > konqueror-profile) and could provide the feature of saving searches.

Saving searches?! Are you sure we are talking about the same thing here?
If I can't find the tea timer, I want to type "timer" somewhere and and see 
where the hell its hidden. 
Now you want to save this search? Reminder: This isn't about searching the 
whole harddisk.

> > (c) wait until there is some beagle or spotlight-tool for KDE where
> > searching for applications could easily be integrated... ;-)

And then what? Do you think that beagle or a spotlight-alike magically reduce 
the complexity of the k-menu?  

> > disadvantages:
> >
> > (a) ordinary users mostly don't use kio-slaves. it's  a shame, because
> > just typing audiocd:/ and copying virtual MP3s is such a magical thing...
> > ;-)

"magical" is the correct word. I'd prefer something more obvious.

> > (b) this would add another entry to the k-menu / it's context menu.

IT might be able to replace the "Run command.." entry.

> One more item is a small price if it increases useability for many users.
> And if you do not like it you could simply disable it in kickers
> preferences.

Yes, especially since it doesn't alter the way the menu works as long as you 
don't use the search. Should we move the whole discussion to kde-usability?

Fred

-- 
Fred Schaettgen
kde.sch@ttgen.net