Thanks for your reply Thomas. I should have read more into the mailing 
list archives.

I can see why you chose hashes and can also see I'm a bit naive. Things 
always look simple until you have to do them yourself. From your 
description I can see that gpodder needs guaranteed unique directory and 
file names. I presume (but correct me if I'm wrong) that cases when the 
title is missing, contains characters unsuitable for file or directory 
names, is longer than a desired maximum length or is a duplicate are 
outlying cases. That is, the title is only unsuitable quite rarely. If 
this is the case then I would advocate using hashes as a fallback 
system. So if it's possible to use the title according to some set rules 
then the title is used and if not then use a hash. If the set rules are 
always used then the program can always tell if it should use the title 
or a hash.

That's my idea. I can see some other people are interested too. Can you 
see a bad test case for this idea?

Jay

Thomas Perl wrote:
> Hello, Pieter!
>
> On Wed, 2007-10-31 at 15:11 +0100, Pieter De Decker wrote:
>   
>> How about adding an option to the right-click menu of each channel
>> saying "Open channel folder"?
>>     
>
> I've tried to do that, but my solution is a bit dirty (I'm using
> "gnome-open" and "os.system()", which is not a good solution), the patch
> is attached, tell me what you think :)
>
> I've also attached a small script I just shuffled together that
> "describes" the download folder structure using the "gpodder" Python
> module, it's "describe_gpodder_downloads.py" and you can run it using
> Python. If you have not installed gPodder onto your system, you have to
> set the PYTHONPATH environment variable to "src/" in your local gpodder
> working copy.
>
> HTH.
> Thomas
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> gpodder-devel mailing list
> gpodder-devel@lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/gpodder-devel
_______________________________________________
gpodder-devel mailing list
gpodder-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/gpodder-devel

Reply via email to