[Panel-devel] The ALI: do we really need or want it?

[Brian Beck]

> Right now, KDE (and other desktops as well) work so that the user has to
> first know what each application does. He's then expected to start the
> correct application, and he then uses that application to access the
> content. My suggestion removes the need to start the application, since the
> user simply accesses the content. How would I listen to my music right now
> in KDE? First, I start Amarok, then I navigate to my music inside Amarok,
> and start to play it back. With my suggestion. the first step for me would
> be to select the music I want to listen, and the playback starts
> automatically. No need to select & start an app, no need to use that app to
> select music. I simply select the music I want to listen, and I'm done with
> it. The number of steps is reduced, the time it takes to start the playback
> is reduced, and everyone is happy :).

Unless I'm totally misunderstanding this sounds awful.

I have about 1000 music files on my computer, I also have one music player I 
like to use (juk).  I can tell you right off that I'd rather click on juk and 
use him to listen to my music then select x songs out of 1000 I'd like to 
listen to first.

So I guess I see two problems with the music example.

1. I have to select x songs out of y to just to listen to music.

2. What if I change my mind about what I want to listen to? Do I need to stop 
the player, dig through all my music files again and restart?

Currently I start Juk and type what I want to listen to in the search bar.  If 
I change my mind I type something different.  What could be easier than that.

Please if I've misunderstood, tell me where, but I've seen mock-ups and read 
descriptions, and it all sounds more complicated than going to the K-menu if 
I want an application or going to Konqueror if I want a document.

Thanks,
Brian