KIPI export plugin for vkontakte.ru social network

[Alexander Potashev]

Hi,

There was a wish in Bugzilla:
https://bugs.kde.org/show_bug.cgi?id=261451 and I've already written a
library for working with some parts of vkontakte.ru API
(playground-libs/libkvkontakte), so I decided to write a KIPI export
plugin for vkontakte.ru.

My code was based on the Yandex.Fotki export plugin, though it became
much cleaner since almost everything is being done by the library.
Also, my KIPI plugin is simpler, because it does only two thing:
1. Creates new albums,
2. Uploads photos into the selected album.
I can't even convert RAW files into acceptable formats.

But I think this plugin can already be useful. Of course, it still
requires some UI polishing.

What should I do in order to get it into kipi-plugins? Should I push
my code into a personal scratch repository or into a public branch in
the kipi-plugins repository?


--
Alexander Potashev
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

Hi Alexander,

Great to see another tool to export collection over a new web service.

Please push your code in git master. kipi-plugins 2.1.0 is planed
around September. I will have some time to review and polish your
code.

Best

Gilles Caulier

2011/8/6 Alexander Potashev <[hidden email]>:

> Hi,
>
> There was a wish in Bugzilla:
> https://bugs.kde.org/show_bug.cgi?id=261451 and I've already written a
> library for working with some parts of vkontakte.ru API
> (playground-libs/libkvkontakte), so I decided to write a KIPI export
> plugin for vkontakte.ru.
>
> My code was based on the Yandex.Fotki export plugin, though it became
> much cleaner since almost everything is being done by the library.
> Also, my KIPI plugin is simpler, because it does only two thing:
> 1. Creates new albums,
> 2. Uploads photos into the selected album.
> I can't even convert RAW files into acceptable formats.
>
> But I think this plugin can already be useful. Of course, it still
> requires some UI polishing.
>
> What should I do in order to get it into kipi-plugins? Should I push
> my code into a personal scratch repository or into a public branch in
> the kipi-plugins repository?
>
>
> --
> Alexander Potashev
> _______________________________________________
> Kde-imaging mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/kde-imaging
>

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Alexander Potashev]

2011/8/6 Gilles Caulier <[hidden email]>:
> Please push your code in git master. kipi-plugins 2.1.0 is planed
> around September. I will have some time to review and polish your
> code.

Pushed.


--
Alexander Potashev
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Alexander Potashev]

2011/8/6 Gilles Caulier <[hidden email]>:
> Please push your code in git master. kipi-plugins 2.1.0 is planed
> around September. I will have some time to review and polish your
> code.

When KIPI-Plugins 2.1.0 will be tagged exactly? I guess, the
"libkvkontakte" library needs to be released before KIPI-Plugins
2.1.0, right?


--
Alexander Potashev
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel