[Digikam-devel] [digikam] [Bug 332665] digiKam should use Baloo for KDE 4.13

[Vishesh Handa]

https://bugs.kde.org/show_bug.cgi?id=332665

--- Comment #41 from Vishesh Handa <me at vhanda.in> ---
(In reply to Veaceslav Munteanu from comment #39)
> @Vishesh, in older Nepomuk Api, I was able to register in ResourceMonitor
> which type of resource I want to monitor. 
> 
> I used to register: comments, tags, ratings and images.
> 
> what I really need from Baloo is signalFileMetadatachanged(Kurl file), so I
> can also trigger it in digiKam.
> 
> At least, if filemodifyjob could register a folder path, that would be much
> better.
> 
> If it's to expensive to fire a signal when Baloo register a change.... well
> there is nothing more I can do to integrate better with digiKam except basic
> read/write on request.

We do fire a change when the file metadata is modified. There is the
FileMonitor, but I think I understand what you mean - there is no way to
globally watch everything. You could just listen to the dbus code (look at the
implementation of the FileMonitor), but that's hackish. Either way, Baloo in
Qt4 is now frozen, so the API isn't going to change.

-- 
You are receiving this mail because:
You are the assignee for the bug.