[RFC] One ioslave to rule them all...

Alexander Neundorf neundorf at kde.org
Wed Jun 29 19:06:07 CEST 2005


On Tuesday 28 June 2005 20:03, Thomas Zander wrote:
> On Tue, Jun 28, 2005 at 11:17:57AM -0600, Aaron J. Seigo wrote:
> > On Tuesday 28 June 2005 10:45, Thomas Zander wrote:
> > > Reiterating from my former mail; showing the user a new (forced)
> > > hierarchy again is not an improvement over the current situation.
> >
> > it's not as good as a search & context centric design can and will be,
> > but it's certainly an improvement over the current situation where there
> > is no single point of entry.
> >
> > just because something isn't as good as something else, doesn't mean it's
> > not better than what we have.
> >
> > i think this is a pragmatic and innexpensive step forward.
>
> The system:// thingy is cool, I fully agree with you on that.
> Providing a home:/ as a new entry point for the user is what I have an
> issue with as it is expensive (new concept to learn in an already covered
> domain).
>
> The initial email went on about providing home:/ instead of $HOME; I have
> a problem with *that* replacement.

Yes, the same for me. It would add some small improvement (I think), but would 
turn the native UNIX path every application understands into a url only KDE 
apps understand.

Where is actually the real difference between about: and system:/ ?

I like both, but they are very similar.

Bye
Alex
-- 
Work: alexander.neundorf at jenoptik.com - http://www.jenoptik-los.de
Home: neundorf at kde.org                - http://www.kde.org
      alex at neundorf.net               - http://www.neundorf.net


More information about the Kde-usability-devel mailing list