Re: [Flickrfs-users] Bug fixes and my enhancement checked in.
Brought to you by:
manishrjain
From: Manish R. J. <man...@gm...> - 2006-02-09 02:03:11
|
On 2/9/06, rdm...@bi... <rdm...@bi...> wrote: > > I've checked in the bug fixes that have been talked about here, as well > as my ctime/mtime enhancement. I've put comments in the README for > each bugfix/enhancement. I'm not sure if the REAME is supposed to be > the changelog or if I should create a changelog? Gr8 that you finished off the ctime/mtime functionality. And I think it wd be more useful if ctime is 'time photo is taken' extracted from photos Exif data. While utime wd be the time when photo is uploaded. If it's OK with you, Manish, I'd next like to do something that I > actually enjoy, though many programmers don't: refactoring. I can see > several places where the code could be tightened up and simplified, > now that you've roughed out how it all works. It will mean some fairly > radical changes to the code, but in the end I think it will be easier > to maintain and enhance (or I wouldn't suggest I do it!). Ok David. No probs with me, but I got some concerns. Lot of changes may ten= d to break the code. To make sure that the changes can be tracked, and the code is still working, it wd be better to do all the changes followed by thorough testing locally, and then put it upstream in 1 go, instead of doin= g cvs update after each small change. Also, there are some functionalities and testing I wanted to complete: 1. Automatically resizing the photos to 800x600, 1024x728 etc. while uploading. The user will specify which resolution the photos shd be converted to through a 'settings.properties' file located in flickrfs Home directory. 2. Meta data - I have tested the editing of metadata files through sed, vim= , and gedit. But more tests need to be done on other editors, for e.g. nano, xemacs 3. Sync any changes done directly to flickr with flickrfs (while its still mounted obv). This will mean flickrfs can automatically detect any new photos uploaded to flickr (directly), and show them. Also means, that any change in meta-data will be reflected as well. Though search results i.e. tags/public or tags/personal need not be affected (or even synced). It wd be best to do this using a command rather than a time bound recurring thread. This wd prevent any inconsistencies. I'd like someone to take these up, and remove the final obstacles to 'using flickrfs'. Manish -- http://tuxmann.blogspot.com "If I have seen further it is by standing on the shoulders of Giants" "Software is like sex: it's better when it's free." "An infinite number of monkeys typing into GNU emacs would never make a goo= d program." |