[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-frameworks-devel
Subject:    Re: plasma-framework, kactivities and kactivities-stats: please consider proper de-KF-ication now
From:       christoph () cullmann ! io
Date:       2023-11-13 15:45:40
Message-ID: 50d45fc1b2b86ff93f4c7993ae8a375e () cullmann ! io
[Download RAW message or body]

On 2023-11-13 09:45, Matthieu Gallien wrote:
> On dimanche 5 novembre 2023 18:01:38 CET Nate Graham wrote:
>> On 11/5/23 07:42, Kevin Ottens wrote:
>> > I was clumsily advocating for this Akademy 2021 or 2022 (can't remember
>> > which).
>> >
>> > This way it's clearer to application authors when they tie themselves to a
>> > given workspace or not.
>> >
>> > Also, isn't Elisa able to work without Baloo? It even seems to do the right
>> > thing if I trust its CMakeLists.txt. It has Baloo as a recommended but
>> > optional dependency, and disable it altogether for Win32 builds.
>> 
>> Yes, Elisa also includes an internal indexer, for use on Windows and
>> Android, or on *Nix when Baloo isn't installed or is disabled.
>> 
>> I think the original idea for the app was to delegate all the indexing
>> heavy lifting to Baloo to avoid internal complication, but clearly 
>> this
>> has not worked out in practice, since to be truly cross-platform, it
>> can't assume that Baloo is present and active and does need its own
>> indexer. So maybe the best course of action is actually to remove 
>> Baloo
>> support entirely and always use the internal indexer, so that we don't
>> have two different code paths.
> 
> From my memory, linking to Baloo was needed to query its database 
> providing much faster discovery of your music files (and the main 
> reason od  a files indexer).
> From a user perspective, reusing the files indexer database makes for a 
> smoother experience.
> I would prefer to be able to also leverage files indexer services on 
> other platforms rather than tying us to the old way of having each 
> application scans files on its own (and monitor file system changes, 
> ...).
> That said, maybe there is a way to query baloo database without linking 
> to the library.

Hi,

that idea is nice, but for me, that didn't work out.

Baloo is under-maintained and it was never in any good state as the 
initial author left it in an state of limbo and vanished.

Just looking at

https://bugs.kde.org/buglist.cgi?bug_status=__open__&product=frameworks-baloo

and the state of

https://invent.kde.org/frameworks/baloo/-/merge_requests

tells me that one should just stay away from using it, if we can't get 
more manpower to fix at least the most prominent cashes.

I don't say that people working on it miss skills or passion, just that 
not enough people work on it to get this fixed.

But that is naturally just my opinion.

Greetings
Christoph

> 
>> Nate
>> 
> 
> Best
> 
> --
> Matthieu
[prev in list] [next in list] [prev in thread] [next in thread]