<div>Hi,</div>
<div> The idea is good, One core problem that I saw with this idea (when we gave a small thought to it sometime back) was to handle the vary different amount of data and information various photo sites allow and the different apis they provide to developers. AFAIK flickr has a very rich API and a plugin supporting flickr APIs can do much beyond any other web photos interface. I intended to make many of this features available in flickr exporter over time, so that it would utlimately turn out to be a flickr client (exporting plus multiple other things).
</div>
<div> </div>
<div>I would say, in any case a common plugin would be an interesting idea. We might leave the users with the option of multiple plugins, from which they can choose the one that suits their need the most. For e.g a person willing to only upload photos to website migh use the websync plugin, while some one trying to do much more can use an advance plugin.
</div>
<div> </div>
<div>I was even thinking if kipi plugnis would end up becoming easier in installation and thereby accessible from simple konqueror window, so that more naive user can try exporting their photos to website, rather than having to install apps like digikam etc which they might not like. (I was thinking of kipi-plugnis being similar to firefox plugins with click to install feature, people can then choose the plugins much more easily, then the current case of installing from a single RPM or by code)
</div>
<div> </div>
<div>Just my 2 cents.</div>
<div> </div>
<div> </div>
<div>regards,</div>
<div>Vardhman</div>
<div><span class="gmail_quote">On 11/17/06, <b class="gmail_sendername">Colin Guthrie</b> <<a href="mailto:gmane@colin.guthr.ie">gmane@colin.guthr.ie</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Vardhman, <br><br>Vardhman Jain wrote:<br>> I am the owner and maintainer of the plugin. I will look around this on
<br>> the weekend and make sure you suggestions and efforts are used in<br>> improving the plugin.<br><br>I've not really looked at the flickr UI (generally, not the .ui file<br>Aaron posted!), but I posted a while ago my desire to potentially take
<br>Gallery and Flickr export plugins and combine them to a Websync plugin<br>and add support for e.g. Googles Picasaweb and other online photo<br>archives from one plugin.<br><br>Emphasis would be placed on synchronisation rather than one off export
<br>(athough this would also be possible).<br><br>Not knowing the UI of the Flickr plugin makes this suggestion a little<br>premature (I'll try and have a look very soon!).<br><br>Just with this short description, do you think it would be something
<br>you'd be interested in?<br><br>FWIW, I added multiple account support to Gallery a while back and<br>figured that adding a "type" field to an account definition and<br>abstracting the protocol level communication classes a little would
<br>allow a mega all-singing, all-dancing websync plugin!<br><br>WDYT? Possible or even wise? Or just ditch the whole idea?<br><br>Col.<br>_______________________________________________<br>Kde-imaging mailing list<br><a href="mailto:Kde-imaging@kde.org">
Kde-imaging@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/kde-imaging">https://mail.kde.org/mailman/listinfo/kde-imaging</a><br></blockquote></div><br><br clear="all"><br>-- <br>Blogs: <a href="http://vardhman.blogspot.com">
http://vardhman.blogspot.com</a><br>