Re: [rox-devel] The TODO file

[Thomas L. <ta...@ec...>]

On Wed, Mar 10, 2004 at 08:56:43PM +0000, Stephen Watson wrote:
> Here's a copy of the current TODO file, with annotations and questions
[...]
> :Installing an icon theme isn't an error!
> 
> Don't know this one.

If ~/.icons/ROX doesn't exist, ROX-Filer creates a symlink. But, it
reports this with a scary-looking error box.

> :Bookmarks:
> :- Short name for bookmarks.
> 
> What does this mean?

You can assign names to items, so instead of seeing "/usr/share/doc" in
the menu, you see "Documentation".

> :When copying or moving files and asking for confirmation, display details
> of the two files to aid comparison.
> 
> As is this, unless we need more info.

I think I'd like to see an indication of which file is to be overwritten.
I can never remember which way around the display is ;-)

> :More options to set fonts?
> 
> Which ones?

In the filer I suppose. This doesn't sound very useful, since you can
always theme it if you really want and we have too many options already.

> :Use an environment variable to override the platform-name guessing in
> :AppRun.
> 
> Just done that (and in ROX-Session)

Good :-)

> :Allow filtering on any expression (not just Show Hidden).
> 
> Filter by name is in.  If filer_match_filter() took a DirItem* then more
> filtering options are possible.

Tried it before. It's quite difficult, because the window is sized before
the extra details are known, so it tends to appear the wrong size. We
could just force the items to be statted, though (it would be slower, but
might be useful anyway).

> :More permissions checking in Find? -RWX?

Think we already have this...

> :Use a separate process to access the filesystem. Prevents hanging when you
> :try to access a dead filesystem. Do this via gnome-vfs?
> 
> Wouldn't need to be a thread rather than a process?
> Can we assume gnome-vfs is available?  Does it work on Solaris?

gnome-vfs uses shared MIME now, I think, so we can probably make it an
option without too much pain.

The whole threading thing is a lot more work than it first appears,
because even if you use a different thread for IO, you still have to
change the logic so that the main thread doesn't block on it.

Random example:

When you press "1", the filer switches to the saved directory, gets a list
of the file names in it, and selects the ones that are set. Then it
handles the next key press. If you want to make this non-blocking, you
have to set up a callback handler to select the files when the scan
completes. Now, if the user presses Ctrl-X while this is going on, what
happens? Do we delete the files selected so far (possibly none if we're
waiting until the end), queue the key-press (seems unresponsive), etc?


-- 
Thomas Leonard			http://rox.sourceforge.net
tal00r at ecs.soton.ac.uk	tal197 at users.sourceforge.net
GPG: 9242 9807 C985 3C07 44A6  8B9A AE07 8280 59A5 3CC1