Write here for feature requests, etc. regarding WebExport 1.1.
This entry was posted
on Monday, August 20th, 2007 at 9:27 am and is filed under Hidden.
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
hello, I have found little problem with templates - they use command like
which causes problem in case of duplicate filenames - for example photos from different film rolls may have same filename like img023.jpg. In this case image files are overwritten. So it should be used something like
to get really unique filenames and avoid overwritting images (this syntax works but generates error message.
hello, I have found little problem with templates - they use command like
?image(900,600,'images/')?
which causes problem in case of duplicate filenames - for example photos from different film rolls may have same filename like img023.jpg. In this case image files are overwritten. So it should be used something like
?image(900,600,'images/'+str(p_index))?
to get really unique filenames and avoid overwritting images (this syntax works but generates error message.
Yes. This is a problem. I am not sure how to fix what you are describing, because using the original filename is a benefit in my eyes. I may change it so you can select what to name the file and that the same name is assumed, or something like that. However, you say there are errors/warnings about what you did on the second line. Please describe/paste these errors, because as far as I can tell, that looks like a valid statement.
It's the best iPhoto plugin I have. Good work. What I really needed was EXIF tag export. I am building a suitable template (will notify you when its done), but needed to modify export.py to import EXIF (the sourceforge python EXIF handler). I suggest including
try: import EXIF
except: pass
to export.py, so that people who have EXIF installed can use it, and those who don't will not be bothered.
November 7th, 2007 at 2:13 pm
hello, I have found little problem with templates - they use command like
which causes problem in case of duplicate filenames - for example photos from different film rolls may have same filename like img023.jpg. In this case image files are overwritten. So it should be used something like
to get really unique filenames and avoid overwritting images (this syntax works but generates error message.
November 7th, 2007 at 2:14 pm
hello, I have found little problem with templates - they use command like
?image(900,600,'images/')?
which causes problem in case of duplicate filenames - for example photos from different film rolls may have same filename like img023.jpg. In this case image files are overwritten. So it should be used something like
?image(900,600,'images/'+str(p_index))?
to get really unique filenames and avoid overwritting images (this syntax works but generates error message.
November 7th, 2007 at 3:19 pm
Yes. This is a problem. I am not sure how to fix what you are describing, because using the original filename is a benefit in my eyes. I may change it so you can select what to name the file and that the same name is assumed, or something like that. However, you say there are errors/warnings about what you did on the second line. Please describe/paste these errors, because as far as I can tell, that looks like a valid statement.
November 14th, 2007 at 7:28 am
webexport.pkg file doesn't want to open. 1.1r8
May 15th, 2008 at 7:20 am
It's the best iPhoto plugin I have. Good work. What I really needed was EXIF tag export. I am building a suitable template (will notify you when its done), but needed to modify export.py to import EXIF (the sourceforge python EXIF handler). I suggest including
try: import EXIF
except: pass
to export.py, so that people who have EXIF installed can use it, and those who don't will not be bothered.
May 15th, 2008 at 11:52 pm
That is awesome. I will definitely add that to the next round. Great finding a solution that works within the current framework!
Thanks!