[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: autorun?!
From:       Gav Wood <gav () indigoarchive ! net>
Date:       2003-08-20 12:26:18
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Wednesday 20 August 2003 11:25, Matthias Wieser wrote:
> Gav Wood wrote:
> > in the case of a mixed cd (data and audio), suppose you want it
> > automounted - which layer looks after it? suppose you want it left
> > unmounted and the cdplayer started - which layer attends to it then?
>
> You don't know what I want. And the computer doesn't know, too. That's the
> problem.

no. the point is that the decision (if any) has to happen at the same system 
level.

> If I insert an audio-CD, maybe I want the cdplayer to startup - but maybe
> I want to rip the cd.
> If I insert an data-CD, maybe I want the setup program to start - but
> maybe I only want to copy the documentation.pdf to my local drive. Or I
> only want to find out, what that CD contains.
> > you seem to be harping back to the (bad) old windows days
>
> You mean good old unix days?

no. i don't call having to manually mount a medium, start a console, enter the 
directory and execute "autorun" a good thing, especially for those users who 
have never met a console in their life and just want to install a game.

> > when magasine
> > cover discs/game instructions always had to say "navigate into the cd
> > rom; click autorun.exe".
> > i always found my self asking why the fsck
> > can't the computer just do that?!
>
> It's simple: The computer can't do that because it doesn't know what you
> want to do. If it tries to do that, the user get's annoyed (ask a
> Windows-user).

no; the correct action can be guessed enough of the time to make it 
indispensible to me, and many others. those who find it annoying would be 
able to turn it off.

gav
-- 
Gav Wood <gav@indigoarchive.net>

codito ergo non satis bibivi

[Attachment #5 (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]