[Kde-imaging] Reg KIPI

[Angelo Naselli]

> Yes I am not denying the responsibility of changing the libkipi stuff
> myself, but as a developer with relatively less experience I wanted to ask
> in the list of that kind of extention (adding a function or two in the
> interface) is okay. I am specially concerned about it breaking any
> compatibility with other apps. I would probably be testing it with the
> Digikam interface only.
> 
> Please let me know specifically as to whether adding some code in
> libkipi/libkipi/imageinfoshared.h libkipi/libkipi/imageinfoshared.cpp in the
> class definition/declaration is okay for everyone or not?

As far as i can say you can start working on it, but if that is going to 
break things for some time, we should probably 
a) freeze the system to work on 1.0 branch until 1.0 will be out
   and you can work on trunk. 
b) move on releasing 1.0 so that you can after break anything you like
   and make this project growing again ;)

WDYT?
  Angelo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-imaging/attachments/20060329/b4f56972/attachment.pgp