>From: Christian Biere <[EMAIL PROTECTED]>
>To: [email protected]
>Subject: Re: [Gtk-gnutella-devel] Suggestion for a new feature
>Date: Sun, 10 Dec 2006 20:59:47 +0100
>
>Lloyd Bryant wrote:
> > How about having an option to specify a download directory for each
>search?
>
> > But it got me to thinking - what if there was an option (via the search
> > pane's right-click menu) to specify a different directory for files that
>are
> > downloaded from that search? That way, a person could potentially have
>many
> > non-related searches active, download whatever looks interesting from
>each,
> > and not have to sort the files into separate directories later.
>
>Looks like a good idea to me. I'd prefer if this allowed only a relative
>directory for simplicity and safety though. People can always use symlinks
>if
>they really want to scatter them over their filesystems. One question is
>how to
>map this to corrupt/incomplete/complete? Should it only be applied to
>complete
>files or others as well? I think it should be irrelevant for corrupt and
>incomplete
>files because that would cause nothing but trouble.
>
>I had a similar issue recently when mirroring all files from one
>gtk-gnutella
>to another. This does not preserve the relative pathnames, so you lose some
>potentially significant information. Consider enumerated pictures which
>provide
>zero information without a - hopefully - expressive directory name.
>
Here's what I'm thinking: Have the rigth-click menu pop up a dialog, in
which you set a download path relative to the default. For example, if you
specified "images", then it would put all downloads originating from that
search in "~/gtk-gnutella-downloads/complete/images". That way all
downloads will still wind up under that "complete" directory, but can be
categorized.
For the "relative path" issue - have a checkbox in the dialog that says
"apply remote relative path (if available)". You would still be free to
specify your own download directory, but the relative directory from the
remote would be applied beneath it - If you specify "music", and the remote
supplies a directory of "Folk", then the file would wind up in
"~/gtk-gnutella-downloads/complete/music/Folk".
I agree that "incomplete" and "corrupt" should be exempt from this. This is
only useful in regards to the final "complete" directory.
> > Another possibility (not useful in the above situation, but I can see
>some
> > use for it) would be to have download directories linked to the file
> > extension - "home/mp3" for mp3's, "home/jpg" for jpeg's, "/dev/null" for
> > .asx files, etc). That would have to be configured in "preferences".
>
>That does not look too useful to me because this can be easily derived
>from the filename and even be automized with a script. Well, if you
>provided
>a clean patch and if didn't get in the way of anything else, I would not
>mind applying such a patch.
Maybe a global option "Place in download subdirectory based on extension"
would be appropriate. I'm a bit leery of this one myself - I can see it
being useful, but not really that useful (especially if the idea of setting
download directory on a per-search basis is implemented).
I'm going to start digging though the code to see what it will take to make
the search-specific option work. If that can be implemented without too
much hassle, then there's really no use for the extension-based option.
Lloyd Bryant
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Gtk-gnutella-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
