Re: [yast-devel] Moving past CSS for the Installer

On Thu, Jan 30, 2020 at 08:56, Josef Reidinger wrote:

On Wed, 29 Jan 2020 22:21:03 +0100 Stasiek Michalski wrote:

...

Hi,

I have been thinking about this for quite a while, and decided it might be a good time to take action in this direction. As you might know, we use an extensive set of CSS files to make our installation medium look like it looks. However since those CSS files are CSS2, because Qt pretty much abandoned CSS in Qt entirely, and it's probably going to be removed at some point. I have asked KDE maintainers how hard it would be to compile Breeze without Kfluff, and while possible, it's not exactly the easiest. Also, from my short interaction with HuHa today, we also need a high contrast theme. I did find something that would work, however it might be a pretty bizarre choice for us. Adwaita-Qt and HighContrast-Qt are two themes that qualify for both: no Kfluff and have high contrast option (and SUSE can use Adwaita-Dark ;). From there, we can get rid of the rest of the CSS, only having to write small helpers to add our branding per distro on top of that. What do you think?

Hi Stasiek, as it will affect also SLE and its branding I think it needs to be coordinated also with its designers or making it supporting both. I see some new style for SLE15 SP2, so I worry we probably should not change it before Leap 15.2.

Yeah, I am willing to maintain CSS for Leap until we hit 16.0, it feels like a reasonable transition time for something like that. We can start with transitioning Tumbleweed in the meanwhile to actually get ready. LCP [Stasiek] https://lcp.world -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org