<br><br><div><span class="gmail_quote">2007/6/7, Colin Guthrie <<a href="mailto:gmane@colin.guthr.ie">gmane@colin.guthr.ie</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Gilles Caulier wrote:<br>> yes, from 'cooker'. but it a little out of date. like KDE4 API will be<br>> frozen next monday (if i remember), i hope than kde4 package will be<br>> updated at soon...<br><br>Yeah that would be handy.
<br><br>I'm sure we can all work out what we need to be able to work safely!<br><br>I think they co-exist happily anyway. I guess it'll be harder to work on<br>e.g. kipi-plugins without a converted host application tho' :)
<br><br>I definately think we should break the KIPI API here tho'... it's just<br>too handy a time not to do it!!</blockquote><div><br>Without an host to perform test, this is not recommended...<br><br>We need to check if all work fine with the current API, like the KDE3 branch
<br><br>So Gwenview port is under progress but it do not support kipi (the application have be completly rewritted)<br><br>like libkipi/libkexiv2/and likdraw port is done in trunk, digiKam port will be started just after
0.9.2-final release will be published.<br><br>I think than we need 1-2 month to port the code and test it indeep. Marcel and me we will do it during this summer. If anyone is interressed to me us in this task, you are welcome...
<br><br>So when digiKam will be ported and tested, we can change API in libkipi as well. Fine for you Colin ?<br> </div></div>Gilles<br>