| Summary: | Flickr tool should be able to access image tags | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Jesús Jiménez <jesjimenez> |
| Component: | Plugin-WebService-Flickr | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | 5.6.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Jesús Jiménez
2006-04-09 17:13:59 UTC
On 9 Apr 2006 15:13:59 -0000, Jes May I draw your attention to ImageInfo::attributes(), this was designed with tagging in mind, so I believe this is what you need. Kind Regards Jesper. On Sunday 09 April 2006 19:44, Vardhman Jain wrote: | On 9 Apr 2006 15:13:59 -0000, Jes Vardhman, i second Jesper about this point. ImageInfo::attributes() is the better way to use Image tags. This is want mean that : - plugins need to check this properties. - kipi Hosts interface need to do something about this method, if host support Tags (KPhotoAlbum, and digiKam for example). Like you working with digiKam, and if you want do some tests, i recommend you to check the digikam kipi-interface : http://websvn.kde.org/trunk/extragear/graphics/digikam/digikam/kipiinterface.cpp?rev=526233&view=auto ... look like we have this code : QMap<QString,QVariant> DigikamImageInfo::attributes() { QMap<QString,QVariant> res; // TODO ! This will used for the futures tags Digikam features. return res; } void DigikamImageInfo::clearAttributes() { // TODO ! This will used for the futures tags Digikam features. } void DigikamImageInfo::addAttributes( const QMap<QString,QVariant>& ) { // TODO ! This will used for the futures tags Digikam features. } This is want mean that something must be done here (:=))). If you is interressed to implement this feature, we can trying to implement this method together and after you just need to support ImageInfo::attributes() in your Flicker plugin. My 10 cts... Gilles > > ------- Additional Comments From caulier.gilles free fr 2006-04-11 15:35 > ------- > Vardhman, > > i second Jesper about this point. ImageInfo::attributes() is the better > way to use Image tags. > > This is want mean that : > > - plugins need to check this properties. > - kipi Hosts interface need to do something about this method, if host > support Tags (KPhotoAlbum, and digiKam for example). > > Like you working with digiKam, and if you want do some tests, i recommend > you to check the digikam kipi-interface : > > > http://websvn.kde.org/trunk/extragear/graphics/digikam/digikam/kipiinterface.cpp?rev=526233&view=auto > > ... look like we have this code : > > QMap<QString,QVariant> DigikamImageInfo::attributes() > { > QMap<QString,QVariant> res; > > // TODO ! This will used for the futures tags Digikam features. > > return res; > } > > void DigikamImageInfo::clearAttributes() > { > // TODO ! This will used for the futures tags Digikam features. > } > > void DigikamImageInfo::addAttributes( const QMap<QString,QVariant>& ) > { > // TODO ! This will used for the futures tags Digikam features. > } > > This is want mean that something must be done here (:=))). If you is > interressed to implement this feature, we can trying to implement this > method together and after you just need to support ImageInfo::attributes() > in your Flicker plugin. > > Gilles, Should we start working on this? Or we have to wait for some release etc ? -- Blogs: http://vardhman.blogspot.com <div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">------- Additional Comments From caulier.gilles free fr 2006-04-11 15:35 -------<br>Vardhman, <br><br>i second Jesper about this point. ImageInfo::attributes() is the better way to use Image tags.<br><br>This is want mean that :<br><br>- plugins need to check this properties.<br>- kipi Hosts interface need to do something about this method, if host support Tags (KPhotoAlbum, and digiKam for example). <br><br>Like you working with digiKam, and if you want do some tests, i recommend you to check the digikam kipi-interface :<br><br><a href="http://websvn.kde.org/trunk/extragear/graphics/digikam/digikam/kipiinterface.cpp?rev=526233&view=auto"> http://websvn.kde.org/trunk/extragear/graphics/digikam/digikam/kipiinterface.cpp?rev=526233&view=auto</a><br><br>... look like we have this code :<br><br>QMap<QString,QVariant> DigikamImageInfo::attributes()<br> {<br> QMap<QString,QVariant> res;<br><br> // TODO ! This will used for the futures tags Digikam features.<br><br> return res;<br>}<br><br>void DigikamImageInfo::clearAttributes()<br>{<br> // TODO ! This will used for the futures tags Digikam features. <br>}<br><br>void DigikamImageInfo::addAttributes( const QMap<QString,QVariant>& )<br>{<br> // TODO ! This will used for the futures tags Digikam features.<br>}<br><br>This is want mean that something must be done here (:=))). If you is interressed to implement this feature, we can trying to implement this method together and after you just need to support ImageInfo::attributes() in your Flicker plugin. <br><br></blockquote></div>Gilles,<br> Should we start working on this? Or we have to wait for some release etc ?<br>-- <br>Blogs: <a href="http://vardhman.blogspot.com">http://vardhman.blogspot.com</a><br> yes we can implement this feature in digiKam kipi interface from trunk. It's not very complicated, normally the implementation is just limited to the empty digiKam kipi interface methods. Gilles Implementation is done in kipi-interface of digikam from trunk. Tests are require using flickr export plugin. Gilles Caulier This entry is implemented since a long time. I close it now... Gilles Caulier Closed |