Right now, every common things on Sleex (like reusable components, config options etc) are defined in the tree of the Shell.
The idea would be making a Sleex UI kit that is located on a global directory (such as /usr/share/sleex-ui-kit), so when we want to make quickshell instances that are detached of the shell, we can access all those components.
For example, if we want to make a lockscreen, instead of mixing it's code with the shell, we could make another QS instance that uses this UI Kit.
I had this idea when thinking about #136, that would have a separate instance.
Right now, every common things on Sleex (like reusable components, config options etc) are defined in the tree of the Shell.
The idea would be making a Sleex UI kit that is located on a global directory (such as
/usr/share/sleex-ui-kit), so when we want to make quickshell instances that are detached of the shell, we can access all those components.For example, if we want to make a lockscreen, instead of mixing it's code with the shell, we could make another QS instance that uses this UI Kit.
I had this idea when thinking about #136, that would have a separate instance.