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

List:       kde-usability
Subject:    Re: Mounting Media
From:       Christoph Held <c-held () web ! de>
Date:       2002-07-20 17:30:23
[Download RAW message or body]

On Saturday 20 July 2002 15:43, Friedrich W. H. Kossebau wrote:
t doesn't.
>
> 3.
> Using kio-slaves for devices also accessable by the os' vfs results in
> inconsistent view for non-kde and kde apps.
>
> -> don't use kio-slaves for devices supported by os' vfs!
No, -> don't use non-kde apps ;-) Serious the os' vfs is inconvinient and will 
always look like a quick dirty hack. A user cannot make errors using floppy:/ 
but hole lot mounting it - including loosing data. If using media is 
difficult or even results in loosing data, a user will say kde sux. If its 
difficult for non kde apps to use media, a user will say kde ruls, non kde 
sux. So os'vfs vs. kioslave should be a simple desicion, isn't it?
>
>
> Last but not least a solution I would vote for if asked:
>
> Addition of kicker devices bars or individual devices (kicker) applets:
> -----------------------------------------------------------------------
>
> each device, known (hard disk, floppy) or expected (digicam), is
> presented by a symbol reflecting it's state. The user can edit which
> devices should appear or
> can be expected. Optional: show only when connected, would result in a
> dynamically sized bar (like the taskbar).
>
> The symbols should not only offer the usual, like
> * LMB click action,
> * LMB long click opening quick browser,
> * RMB menu,
> but also drag'n'drop support:
> when dropping a file on it, a floppy symbol should try to automatically
> mount the floppy disk and copy the file into the root dir;
> when hovering with a dragged file over the symbol for some time, also
> mounting should be tried, after that opening a quick browser view for
> choosing the directory to drop.
>
> Additionally other devices, like printers, or the trashcan might appear
> there,
> to have always a quick access. Hovering a dragged file over a printer's
> symbol might result in a popup menu to choose either standard print or
> settings menu. The printer applet should state whether the drag was from
> a file view (e.g. konqueror) so it has to start the specific app to do
> the print ("app --printonly --printer=me file") or if it was from a
> running app so it has to signal the wish for a print to the app via
> dcop.
>
> If I only had the time... I would try to code this immediately...
> sigh... :(
>
> Friedrich
> _______________________________________________
> kde-usability mailing list
> kde-usability@mail.kde.org
> http://mail.kde.org/mailman/listinfo/kde-usability

_______________________________________________
kde-usability mailing list
kde-usability@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]