appstream in Plasma

[Alexander Potashev]

Martin,

Please find my comments below.

2016-04-08 8:55 GMT+03:00 Martin Graesslin <mgraesslin at kde.org>:
> On Thursday, April 7, 2016 11:28:17 PM CEST Alexander Potashev wrote:
>> What if
>>  1. I don't use a desktop environment, but I need a way to setup
>> localization for KDE applications?
>
> Ever heard of setting the LC_LANG env variables? Yes, nowadays KDE
> applications use the standard Linux way for localization and not a custom
> thing where one needs a special configuration module.

Localization section in System Settings also includes spellchecker KCM
that writes to ~/.config/KDE/Sonnet.conf. There is no other place to
configure spellchecker for KF5-based applications.

>>  2. I have GNOME installed, but can't figure out how to use its tools?
>> The way out from this situation is that I install systemsettings5 and
>> use it to configure localization while in a GNOME shell session.
>
> Report a bug against GNOME then, if their software is unusable.

GNOME software might be OK, but I don't want to spend time on learning it.

Everyone should be free to use systemsettings5. What you suggest is
not freedom [1].

>> > Erm no. I just did a search for Akonadi in systemsettings and it returns
>> > nothing. Even if it were in systemsettings it would be wrong. That needs
>> > to be offered from the applications.
>>
>> Please search for "PIM Accounts and Resources" in systemsettings.
>
> doesn't exist on my system.

OK, I might have an old version of KDE PIM.

>
>>
>> >>  - Baloo,
>> >
>> > Use the DEs search tool
>>
>> What if I want to use Dolphin? It only integrates with Baloo, thus I'm
>> forced to use it. Editing baloorc is not very user-friendly.
>
> Then dolphin needs to make the baloo configuration accessible. Expecting users
> to know that they need to install systemsettings is no solution.

Reported against Dolphin: https://bugs.kde.org/show_bug.cgi?id=361557

>> >>  - systemd
>> >
>> > There is no such thing as a systemd kcm in systemsettings
>>
>> Please see https://quickgit.kde.org/?p=systemd-kcm.git
>> You can install it and find it in systemsettings root menu.
>
> 3rd party modules are not a reason for us to do things.

OK, then it's a problem in Systemd KCM.
Reported: https://bugs.kde.org/show_bug.cgi?id=361558

>> Is your vision that writing third-party KCMs should be forbidden? (By
>> "third-party" I mean those that are not released as part of Plasma.)
>
> Everybody is free to write 3rd party KCMs to integrate with Plasma. But it's
> no reason to make Plasma applications available to non-Plasma users.
>
> To make it clear: we care here about the Plasma workflows and a good
> integration of Plasma inside Plasma. You are free to use Plasma tools outside
> Plasma, but that is not what we aim for. If you want to use systemsettings
> outside of Plasma: do so! But that doesn't mean that we want to expose
> systemsettings to non-Plasma users. Just like we don't want GNOME's settings
> tool exposed to Plasma users.

What I have understood so far, systemsettings5 is supposed to be a
Plasma-only tool. Given that, we (KDE) are lacking a KCM browser tool
suitable for everyone.


[1] https://dot.kde.org/2016/04/05/kde-presents-its-vision-future

-- 
Alexander Potashev