Who relies on Soprano::Model::statement[s]Added|Removed signals?

Volker Krause vkrause at kde.org
Wed Oct 5 07:55:08 BST 2011

On Friday 30 September 2011 13:36:22 Sebastian TrĂ¼g wrote:
> Hi lists,
> with frameworks in the building and Nepomuk probably going that
> direction already for 4.8 I would like to clean up a bit. One of these
> cleanup tasks targets the Soprano::Model statement signals. So far these
> were the only way to get informed about changes in Nepomuk - with a very
> bad impact on performance and bad usability.
> With 4.7 we already introduced a preliminary version of the
> Nepomuk::ResourceWatcher[1] which is now in charge of informing clients
> about changes.
> I would like to anyone using the "old" API to change to the new
> ResourceWatcher as soon as possible because I would like to disable the
> old signals soon. They simply entail to many problems and clutter the API.

kdepim uses those signals in the following places:
- libmessagelist (kdepim/messagelist)
- kmail 
- Nepomuk tag resource (kdepim-runtime/resources/nepomuktag)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20111005/e2ade2e7/attachment.sig>

More information about the kde-core-devel mailing list