mgallien added a comment.

  In https://phabricator.kde.org/D4911#92732, @mgallien wrote:
  
  > In https://phabricator.kde.org/D4911#92718, @cullmann wrote:
  >
  > > Just my 2 cents from the sideline:
  > >
  > > 1. baloo is unmaintained and the bugs pile up, just check bugs.kde.org 
for that, not sure if adding yet-an-other feature to it is a good idea
  > > 2. as vhanda said, perhaps better use other API for that
  >
  >
  > Those APIs are not free and takes some kernel resources.
  >
  > > I tried to replace baloo with tracker, see 
https://cgit.kde.org/clones/baloo/cullmann/tbaloo.git/ but failed out of time 
(searching works, but not all API), that won't support such things anyways.
  >
  > I was hoping to support the same file indexer that Plasma is using hence my 
work on Baloo. On my roadmap, I plan to also support Tracker.
  >  For Windows and Android, I have implemented an indexer with Qt + 
KFileMetaData APIs. I was just hoping that Baloo would provide live refresh of 
queries. I have to check if Tracker does it or not.
  
  
  I have installed again Tracker and an application using it on my Debian 
unstable. With qdbusviewer, I see a DBus signal for signaling changes to its 
database.  i have to check but I think this is exactly the feature I need to be 
able to really use Baloo. This way, an application know when to execute once 
more its query to get an updated result.
  
  I will also modify my patch to implement only one signal fired without 
parameters (i.e. no list of modified content) when Baloo database is modified. 
Vishesh do you think this would be problematic performance wise ? This would 
allow my application to always get an updated list of audio files whenever 
files are added, removed or modified. This would avoid duplicating file system 
watches.
  
  I will try using Tracker with your work compatibility layer. Did you get 
feedback from frameworks maintainer ?

REPOSITORY
  R293 Baloo

REVISION DETAIL
  https://phabricator.kde.org/D4911

To: mgallien, vhanda
Cc: cullmann, apol, #frameworks

Reply via email to