Version: inconnu (using 4.3.2 (KDE 4.3.2), Mandriva Linux release 2010.0 (Cooker) for i586) Compiler: gcc OS: Linux (i686) release 2.6.31.6-desktop-69mib export a photo to picasaweb export same photo to picasaweb result : you have 2 occurrences of the same photo in your picasaweb this is a pb often you modify a photo for example you fix it, you add a legend or a tag then you want to update the photo in your picasaweb
Which kipi-plugins version you use ? Gilles Caulier
kipi-plugins 0.7
Try 0.8.0 Gilles Caulier
dgikam 1.0.0b6 kipi-plugins 0.8 same pb
digikam 1.0.0rc kipi-plugins 0.8 same pb
digikam 1.0.0 kipi-plugins 1.0.0 same pb
digikam 1.1 kipi-plugins 1.1 pb still there same pb for movies
Therefore we have two possabilities: -take the filename as reference, handled as title attribute inside picasaweb. I see problems here when renaming the offline image or any other application change this picasaweb tag (the title attribute needs not to be unique, also not per album) -use the unique picasaweb gphoto:id attribute, but as the id is generated online we have to store it back to the original image. No problems with filerenaming etc but we can only store the gphoto:id attribute when we have access rights. Also we need a exif/xmp tag to take for. Any opinions? Jens
1. be simple for a first shot the user knows only the name the name for user is not only a name this is an identifier if the user changes the name this is another photo (accurately another occurence of the same photo) frequently i use 2 occurrencies of the same photo (an original and a modifed one and for me they are different ones apply the principle : if you change the name then this is not the same photo 2 we must think about this new feature as a beginning or a part of a future synchronization mecanism 3. perhaps this solution is more closed than using gphoto.id for future modification to add or extend a feature perhaps it is handy for future feature to use gphoto.id and to see several photos with same gphoto.id as occurrencies of the same photo this way opens the future possibilities, the future operators
I fully agree to 1) in the above comment But here is another usecase: A user want to set up a 'best shots' collection, therefore he take several images from different albums and load them up in one step. Some cameras start counting taken photos by zero again when the card is empty. So the user has several images with the same filename in his upload step. I think everybody will agree to say that there should no 'do want to override <that> existing file?' messageboxes, all images should be uploaded as new ones. No problem so far. But now the user change something, for example brightness of one image, and want to update the corrosponding image. If there is a image with the same title attribute (filename) digikam should bring up a messagebox and ask for 'replace'|'add'|'skip'. But what do to when there a more than one image with the same title attribute? Which one to replace? You can also get in this trouble through: Upload a image, upload the image again and select 'add' from the messagebox. Now you upload the image again and select 'replace'. Which one to take for? Jens
Ah ok i understand - several photos has same filename - we must use a digikam identifier for each photo (don't forget movies) - picasaweb ignores this identifier then we must put the identifier in the photo file as a data in the exif-xmp field your solution is more general and good another question you say "gphoto.id" why not a digikam id ? sorry for facebook i don't use facebook
The (overall picasaweb universe) unique id is called gphoto:id in picasaweb. Jens
@Gilles: I need a 'picasawebGPhotoId'-attribute stored inside XMP. For documentation look here: http://code.google.com/intl/de-DE/apis/picasaweb/docs/2.0/reference.html#gphoto_id , description will be someting like 'The unique id of an element inside picasaweb' or something like that. I tryed to save that one in a new tag but do not succeed. The tag is not there after, setXmpTagString return false. If I reuse a existing tag for testing it works. You wrote for pure write/read tags this is not neccessary in #224893?
Jens, let's me see the code... Gilles Caulier
SVN commit 1088903 by jmueller: store unique gphoto:id of uploaded images CCBUGS: 215787 CCBUGS: 217539 M +3 -18 picasawebitem.h M +41 -48 picasawebtalker.cpp M +14 -6 picasawebtalker.h M +145 -93 picasawebwindow.cpp M +7 -5 picasawebwindow.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1088903
@Gilles: relevant code is in picasawebwindow now, please look for 'xmp'
Jens, I cannot see any problem in your code. Which version of libkexiv2 you use ? Trunk ? (recommended) And Exiv2 ? 0.19.0 ? trunk ? Gilles
currently: LibExiv2: 0.18.2 LibKExiv2: 0.6.0 But I will upgrade KDE now.
yes, i think version is the problem... Gilles Caulier
updating LibKExiv2 to 1.0.0 make saving XMP work
Great, so Philippe will see this file closed soon, for 1.2.0 release. Nice job have been done on Picasa tool Jens, congratualtions ! Gilles
Thanks, Gilles. Work is not completed yet, but hopefully for 1.2.
SVN commit 1091885 by jmueller: finalize update option of existing photos BUGS: 217539 CCBUGS: 215787 M +2 -1 NEWS M +1 -0 picasawebexport/CMakeLists.txt M +2 -2 picasawebexport/picasawebalbum.cpp M +1 -1 picasawebexport/picasawebalbum.h A picasawebexport/picasawebreplacedialog.cpp [License: GPL (v2+)] A picasawebexport/picasawebreplacedialog.h [License: GPL (v2+)] M +17 -15 picasawebexport/picasawebtalker.cpp M +0 -1 picasawebexport/picasawebtalker.h M +73 -23 picasawebexport/picasawebwindow.cpp M +1 -0 picasawebexport/picasawebwindow.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1091885
Updating photos work now. But for videos we need to find a place where to store picasaweb id as xmp is not available.
Soon the hope to use no more picasa software to manage picasaweb albums ! And to do more : managing movies with linux version does not work by default and even with somme adds manages only .mov file, not avi) thanks
Philippe, This file still valid using kipi-plugins 2.4 ? Gilles Caulier
digikam 2.5 no more pb
Sorry but for movie pb still valid with digikam 2.5
when do you think this interesting feature will be supplied ? today with digikam 2.9.0 in the contrary of a photo when sending a second time a movie then the export tools does not ask fo me if i want to replace it or to add a second occurence then i have a second occurrence in picasaweb site
Philipe, This file still valid using new GDriveExport tool instaed PicasaWebExport ? Gilles Caulier