Indicators New Architecture and Online Service
Closed, ResolvedPublic

Description

IMPORTANT: All the entire Indicators architecture has been updated!!

NEW ARCHITECTURE
PROS:

  • each indicator style can be loaded independently included its settings, config ui etc...
  • each indicator style now looks a lot as the qml plasmoids, so it will be easy for programmers to create their own styles
  • In upcoming weeks Latte will be able to download/install/use Latte Indicators styles from kde store

CONS:

  • your current indicator configuration can not be used because all configuration options are set by the indicator and maintained by it
  • When the online service is in place the Unity indicator will be provided only online and it will be moved out of Latte codebase

Sorry for any inconvenience but the benefits of the approach and the freedom to all kde developers to create their own indicator styles without even touching the Latte codebase are very big to ignore...

It might be a good idea if any kde developers are interested in this to take part of the discussion early because that way more robust experience and features will be provided.

I will publish more info etc. when the online category at kde store is available and Latte is able to play with it.

trmdi added a comment.Mar 24 2019, 1:25 PM

Hmm, I think the directory name is too long:

/usr/share/latte/indicators/org.kde.latte.indicator.default/metadata.desktop

should just be:

/usr/share/latte/indicators/default/metadata.desktop
/usr/share/latte/indicators/default/metadata.desktop

done

trmdi added a comment.Mar 24 2019, 1:40 PM
/usr/share/latte/indicators/default/metadata.desktop

done

I meant that should be also applied to other indicators: /usr/share/latte/indicators/plasma/metadata.desktop, /usr/share/latte/indicators/unity/metadata.desktop ...

this is not possible because we are going to have multiple indicators in the future... It follows the plasma applets logic that is doing the same thing... pluginid names the root directory of the plugin

trmdi added a comment.Mar 24 2019, 4:19 PM

this is not possible because we are going to have multiple indicators in the future... It follows the plasma applets logic that is doing the same thing... pluginid names the root directory of the plugin

1, I just meant you should use plasma/unity..., or maybe psifidotos.plasma/psifidotos.unity for X-KDE-PluginInfo-Name...
That removes the unneeded part "org.kde.latte.indicator." but still keeps the name unique as well as clean/simple.

You can use "Latte Indicator" for the X-KDE-PluginInfo-Category line. I guess this field is used only for the readability of the metadata.desktop file, in this use case.

2, Btw, I got this error in the latest commit:

file:///usr/share/latte/indicators/org.kde.latte.indicator.unity/package/ui/main.qml:28:1: LatteComponents.IndicatorItem is not a type

this is not possible because we are going to have multiple indicators in the future... It follows the plasma applets logic that is doing the same thing... pluginid names the root directory of the plugin

1, I just meant you should use plasma/unity..., or maybe psifidotos.plasma/psifidotos.unity for X-KDE-PluginInfo-Name...
That removes the unneeded part "org.kde.latte.indicator." but still keeps the name unique as well as clean/simple.

I renamed them in the following that I am a bit more comfortable:

org.kde.latte.default
org.kde.latte.plasma
org.kde.latte.unity

You can use "Latte Indicator" for the X-KDE-PluginInfo-Category line. I guess this field is used only for the readability of the metadata.desktop file, in this use case.

done, good idea

2, Btw, I got this error in the latest commit:

file:///usr/share/latte/indicators/org.kde.latte.indicator.unity/package/ui/main.qml:28:1: LatteComponents.IndicatorItem is not a type

strange, I dont get that in my system, please open a bug report if that remains and checkout that LatteComponents from declarativeimports directory have installed correctly

trmdi added a comment.Mar 24 2019, 5:25 PM

It's ok now. Thanks!

mvourlakos closed this task as Resolved.Mar 31 2019, 1:25 PM

architecture landed so this is ready!