Plasma5 automatic theme switcher

marav · 04-26-2021, 02:10 AM

Hi,

If my memories are good, this option exists under gnome
And I wanted a similar one under KDE :
Be able to change themes according to the hours of the day

I made a slackbuild
It uses the wonderful daemon thanks to ZhaoLin & raforg

feedbacks are welcome

https://github.com/maravtdm/lookandfeel

LuckyCyborg · 04-26-2021, 03:02 AM

Quote:

Originally Posted by marav

Hi,

If my memories are good, this option exists under gnome
And I wanted a similar one under KDE :
Be able to change themes according to the hours of the day

I made a slackbuild
It uses the wonderful daemon thanks to ZhaoLin & raforg

feedbacks are welcome

https://github.com/maravtdm/lookandfeel

Congratulation for you project and for practical demonstrating also that this daemon supervisor is of general purpose, for any "user target" daemons we will want eventually to handle.

And also looks like you understand properly what those "user target" daemons are, up to to creating your own ones.

Regarding your 5 minutes sleep from script, I believe that's a not so fortunate idea...

As well, you can split this sleep time in seconds sized pieces, making your script much more responsive.

Like this

Code:

COUNT=300

while [ "$NOW" -lt "2359" ] ; do
  if [ "$COUNT" -lt "300" ] ; then
    COUNT=$((COUNT+1))
    sleep 1
    continue;
  fi
  COUNT=0

  ...
done

Giving to the $COUNT a big value from start permits an initial execution of the loop, then it will do nothing (for 300 seconds / 5 minutes) other than processing the loop with sleeping 1 second each time.

Alien Bob · 04-26-2021, 03:10 AM

I wish you would stop mentioning in every post the systemd concept "user target". We do not have systemd and I'd like to keep the terminology out of the distro.

marav · 04-26-2021, 03:21 AM

Quote:

Originally Posted by LuckyCyborg

Regarding your 5 minutes sleep from script, I believe that's a not so fortunate idea...

As well, you can split this sleep time in seconds sized pieces, making your script much more responsive.

Thank you very much for your feeback

I will try your suggestion ;-)

LuckyCyborg · 04-26-2021, 03:23 AM

Quote:

Originally Posted by Alien Bob

I wish you would stop mentioning in every post the systemd concept "user target". We do not have systemd and I'd like to keep the terminology out of the distro.

Okay, but how we should name this kind of programs like the one made by OP, which is designed to run in background and to be started on user login (for every user reaching the graphics desktop), then being stopped on user logout?

In fact, someone can just add an unit file and package it for openSUSE as well. Or Kubuntu.

Honestly, I believe we should be proud that we are The First non-systemd distribution having a consistent way to handle this kind of programs.

Alien Bob · 04-26-2021, 03:43 AM

Quote:

Originally Posted by LuckyCyborg

Okay, but how we should name this kind of programs like the one made by OP, which is designed to run in background and to be started on user login (for every user reaching the graphics desktop), then being stopped on user logout?

In desktop land that's just called session management. Nothing new or magical. Has worked for 10s of years without requiring systemd.

The fact is that pipewire is badly written so that it only works properly with systemd... and a separate daemon application had to be found for Slackware to make pipewire work with regular graphical session management.

ZhaoLin1457 · 04-26-2021, 03:59 AM

With all respect, I do not think that this kind of programs is connected with the graphical session management only.

For example, I use this daemon supervisor to manage a VPN client, with a command put on ~/.profile and another on a XDG autostart file, then no matter if I login on Plasma5 from SDDM or in the Linux console, the VPN is automatically started and in logout it's automatically stopped.

How about to name them just "user daemons" or "user services" if the "user target daemons" naming is questionable?

marav · 04-26-2021, 04:27 AM

Sorry to cut you
But, while it's not uninteresting, I don't think the thread's topic is: how to name this user daemon

LuckyCyborg · 04-26-2021, 05:03 AM

Quote:

Originally Posted by marav

Sorry to cut you
But, while it's not uninteresting, I don't think the thread's topic is: how to name this user daemon

Speaking of your user daemon, looks like you forgot to add the initial value of the $COUNT - proposed patch bellow.

Code:

diff -urN lookandfeel.orig/lookandfeel lookandfeel/lookandfeel
--- lookandfeel.orig/lookandfeel	2021-04-26 13:00:20.860031653 +0300
+++ lookandfeel/lookandfeel	2021-04-26 13:00:51.333031733 +0300
@@ -9,6 +9,8 @@
   . /etc/lookandfeel.conf
 fi
 
+COUNT=300
+
 while [ "$NOW" -lt "2359" ] ; do
   if [ "$COUNT" -lt "300" ] ; then
     COUNT=$((COUNT+1))

marav · 04-26-2021, 05:12 AM

Quote:

Originally Posted by LuckyCyborg

Speaking of your user daemon, looks like you forgot to add the initial value of the $COUNT - proposed patch bellow.

Code:

diff -urN lookandfeel.orig/lookandfeel lookandfeel/lookandfeel
--- lookandfeel.orig/lookandfeel	2021-04-26 13:00:20.860031653 +0300
+++ lookandfeel/lookandfeel	2021-04-26 13:00:51.333031733 +0300
@@ -9,6 +9,8 @@
   . /etc/lookandfeel.conf
 fi
 
+COUNT=300
+
 while [ "$NOW" -lt "2359" ] ; do
   if [ "$COUNT" -lt "300" ] ; then
     COUNT=$((COUNT+1))

Oups ...

EDIT : fixed. thanks again

LuckyCyborg · 04-26-2021, 05:37 AM

Quote:

Originally Posted by marav

Oups ...

EDIT : fixed. thanks again

No problem.

And now you can probably delete also this text from your README.md

Code:

NB: because of the "sleep 5m" in the while loop
It needs ~5min. to exit the loop on logout

In fact, now it needs ~1sec. to exit the loop on logout.

marav · 04-26-2021, 05:43 AM

Quote:

Originally Posted by LuckyCyborg

No problem.

And now you can probably delete also this text from your README.md

Code:

NB: because of the "sleep 5m" in the while loop
It needs ~5min. to exit the loop on logout

In fact, now it needs ~1sec. to exit the loop on logout.

Thx again again

LuckyCyborg · 04-26-2021, 05:55 AM

Quote:

Originally Posted by marav

Thx again again

No problem.

BTW, WHY you ship that file README when you have README.md too?

marav · 04-26-2021, 06:00 AM

Quote:

Originally Posted by LuckyCyborg

No problem.

BTW, WHY you ship that file README when you have README.md too?

because I had checked the box "create the readme.md" at the initialization of the repo
and I also have the file README in the directory I uploaded
I didn't pay attention to that
I'll clean up later

LuckyCyborg · 04-26-2021, 06:06 AM

Quote:

Originally Posted by marav

because I had checked the box "create the readme.md" at the initialization of the repo
and I also have the file README in the directory I uploaded
I didn't pay attention to that
I'll clean up later

For a GIT repo like yours, I suggest you to keep the README.md