[prev in list] [next in list] [prev in thread] [next in thread]
List: kfm-devel
Subject: Re: KFM 0.8
From: weis () stud ! uni-frankfurt ! de
Date: 1997-06-29 11:30:48
[Download RAW message or body]
Hi,
I dont have much time right now. I will read your report very
carefully and answer tomorrow.
Nicee weakend and thanks
Bye
Torben
On Sat, 28 Jun 1997, Sven Radej wrote:
> Problems:
>
> NOTIFY:
> ********
> When copying dir, kiojob notifyes the newly created dir that isn't
> shown, and last recursed dir in source dir.
> Precisley:
> Displayed are two windows: ~ and /tmp; copy ~/Latex/ to /tmp.
> He notifies ~/Latex/figures (subdir in Latex, not shown) and /tmp/Latex
> (Shown is /tmp, not /tmp/Latex) => doesn't display newly created dir.
> notifylists should be fixed.
>
> Maybe there is a way to monitor shown dirs (and Desktop, Trash and
> shown devices with icons on desktop) with some timer... I had before
> KFM Offix filemanager that monitored its dirs for change every
> 800 ms - didn't add much to the load. This is important for non-KFM
> file management (cp, rm, mv ...)
>
> RECURSIVE DELETE
> ********************
> Acording to kioslave/main.cpp directories are deleted with rmdir () and
> errno==ENOEMPTY is not tested after, so it returns error, and displays
> "doesn't exist or no permission" messagebox.
>
>
> PROPS
> *******
> Right click on FIFO (named pipe) freezes kfm. Kfm shouldn't try to read
> from such special files. Socket with 'rwx' is displayed as Executable.
> Obviously, 'x' bits are examined before type bit ('s'). This is not so
> important since this counts only for X sockets in /tmp/.X11-unix/ witch
> are 'srwxrwxrwx' None of special files has its type written in props (Is
> socket, Is character dev ... but that's not so important)
>
> KIOSLAVE/KIOSERVER
> **********************
> Showes sometimes badly resized emty window. Sometimes at copyng/moving
> folders forgets at some folders - writes down file with size 0.
>
> Since there is no recursive deletion of dirs, I added that in kioslave.
> I added another argument for mkdir, copy and del functions. This
> parameter would determine whether to Recurse dir, to overwrite
> existing files etc.
>
> It should work like this (for file:/): You try to delete nonempty dir.
> kioslave sends fatal error (with errno=ENOTEMPTY). Kiojob
> promts you wether to recurse directory, and calls again delete with
> recurse argument set. The same is for deleting your RO files, mkdir
> when same name exists... etc.
>
> The problem is in terribly complicated kioserver side. I belive that
> all recursing should be done in kioslave (kioserver should send just
> one url or list of urls - if some of these are dirs kioslave should do
> the recursion). This goes for move over different filesystems, too
> (kioserver should decide that. It seems (am I wrong?) that this is not
> the case right now - kioserver does some things too on file:/. Maybe
> there are some transient misunderstanding between kioserver and
> Stefan's new kioslave.
> I think that Kioserver side should be clean from all menagement.
> So it would be more easy to add new protocols (mailfolders, or
> whatever there is to add)
>
> Well, this kioserver problem is in fact my problem since I can't (yet)
> clue who's calling who, why and when. And all that debuging output...
>
> bye
> --
> Sven <sven.radej@iname.com>
>
>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic