KFileMetaData and API level requirement

[Aleix Pol]

On Tue, May 9, 2017 at 9:36 AM, Matthieu Gallien
<gallien.matthieu at gmail.com> wrote:
> Hello Aleix,
>
>
> Le 8 mai 2017 16:50, "Aleix Pol" <aleixpol at kde.org> a écrit :
>
> Hi Matthieu,
> To be honest, I don't have a lot of experience with kfilemetadata, so
> it's hard for me to tell.
>
> I would suggest not to adapt too much the code in kfilemetadata to fit
> in different platforms. But then, if your projects hinges on the
> feature, then I can see it making sense some closer look.
>
>
> To summarize my question is : should I make parts of the framework optional
> at the prize of ABI change or API doing nothing ?
> This change is necessary to support Android 4.4 .
>
>
> HTH,
> Aleix
>
>
> On Mon, May 8, 2017 at 12:08 PM, Matthieu Gallien
> <gallien.matthieu at gmail.com> wrote:
>> Hello,
>>
>> I am trying to use KFileMetaData on Android. Currently, it requires API
>> level
>> 21. My current phone is Android 4.4. This means I cannot use it to test my
>> application. Not good for me.
>>
>> As I see it, there is two strategies:
>> * doing nothing and keeping the current requirement on API level 21 and
>> having
>> always built in the support for extended attributes (mainly used to have
>> generic ratings and comments on any file) not necessarilly well integrated
>> outise Plasma desktop ;
>> * making the dependency on extended attributes optional and pushing
>> current
>> extractors to support audio rating tags for file format having it. On
>> Plasma,
>> we could keep doing like now.
>>
>> What is your advice ?
>>
>> Best regards
>
>

This is more of a kfilemetadata maintainer thing to decide, IMHO.
Alternatively, send an e-mail to kde-frameworks-devel and we can
discuss this together.

Aleix