Fallbacks for packages

[Marco Martin]

On Mon, Jul 21, 2014 at 11:26 AM, Marco Martin <notmart at gmail.com> wrote:

> Hi all,
>
> I have been thinking about the problem of the look and feel and shell
> packages: we want them to be easily customizable for distributions without
> forcing to copy and paste the mayority of the qml in the package (and also
> having things like providing only a spashscreen and nothing else)
>
>
Soo, after more thinking about this, I'm kinda going in another direction:
I really do not like the idea of having generic fallbacks in packages,
since this violates the idea of isolation that is a core concept of 99% of
the package use case.. practically except the look and feel one.
Since the main place we need this is lookandfeel, we need something more
central to access its files. Right now it's accessed by several processes,
in several places and all of them hardcode the default one.
There is a good possibility all of its users are in plasma-workspace
(something that could be enforced, even).
what i was thinking about was a very small library that reads what
lookandfeel package is configured, opens it and manages the fallback stuff
(by actually using 2 of them, the default one and the configured one, if
any)

It doesn't even have to be a real library, just a file statically linked
from where is used in workspace.
the one exception would be sddm, but would have to manage things by itself
anyways since it can't link to package anyways.

--
Marco Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20140723/88289fd7/attachment.html>