On 3/29/06, <b class="gmail_sendername">Tom Albers</b> <<a href="mailto:tomalbers@kde.nl">tomalbers@kde.nl</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Op Tuesday 28 March 2006 17:56, schreef Vardhman Jain:<br>Yep. To be honest, I dont think anyone will do the necessary work on libkipi<br>for you. If you need it, you need to make it yourself. I don't think anyone<br>with knowledge has time or motivation (to prevent a misunderstanding: I know
<br>less about libkipi then you do).</blockquote><div><br>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.
<br><br>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?<br></div><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Also Can we have a more regular release<br>> schedule for kipi-plugins ? If its too difficult to coordinate why not
<br>> allow the Digikam developers to take the complete responsbility. I am not<br>> trying to start a flame war here, I just want to express my concern over<br>> the issue.<br><br>The release script is in svn, anyone can run it and make a tarball. There is a
<br>kipi sf page where you can get access to to upload it. Again, this is<br>something _you_ can do.<br><br>remark 1<br>The digikam team has a new packager, maybe someone should contact him and ask<br>to do it for kipi as well, I think he will enjoy it.
<br><br>remark 2<br>in the digikam repository there are packaging instructions, maybe they are<br>usefull to read.<br><br>> As a kipi-developer, I don't see my plugin being available to the user<br>> easily. (First they have to seperately install this libkipi etc stuff and
<br>> then the updated version can only be obtained from the SVN). With so much<br>> development going on in various kipi-plugins we should atleast ensure as<br>> frequent issues of kipi as we have for digikam and digikam image plugins.
<br>> This is not to overshadow the other projects which support kipi but only to<br>> enhance the kipi-plugins availability to users.<br><br>I think it would be best to package it now (as in asap) as final version<br>
(unless there are grave bugs), so that is behind us and start with a clean<br>sheet.<br><br>I'm available for questions about the packaging.<br><br>Toma<br></blockquote></div>I am going to spend some time reading the scripts and see if I can help myself.
<br><br clear="all">Vardhman<br>-- <br>Blogs: <a href="http://vardhman.blogspot.com">http://vardhman.blogspot.com</a><br>