[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: RFC: Theming and styles of KDE applications
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2024-05-04 23:04:00
Message-ID: CA+XidOEzWGxjDcCQ-dfrAC6EQ+QR=eAmCy1wRJfnQeHuj9LwVQ () mail ! gmail ! com
[Download RAW message or body]

On Sun, May 5, 2024 at 8:37 AM <christoph@cullmann.io> wrote:

> On 2024-05-04 21:56, Akseli Lahtinen wrote:
> > On Saturday 4 May 2024 14:47:35 GMT+3 christoph@cullmann.io wrote:
> >> My proposal: we enforce Breeze as icon set and style everywhere. And
> >> we
> >> provide still a way to overwrite that for the user, but if the user
> >> didn't set something manually,  idenpendent what the system propose,
> >> we
> >> just use Breeze. And we depend on that as dep e.g. in Kate, if you
> >> install Kate, that icon set and theme is installed.
> >
> > +1. For me as someone who changes icons sometimes just to see and
> > tinker
> > around,
> > i think this makes sense. We have reliable fallback, but we still allow
> > users to customize things which is, well, our thing! :)
> >
> > And if the custom icons break i do not end up with broken apps, so
> > i really do not see any downside here, as user or dev perspective.
>
> Yes, if some user switches a theme or style in our system settings
> or in the application (like we do it with the color scheme switcher some
> applications like Kate have) that is fine.
>
> But beside that, we should just force our default style and icon set,
> like we do on Windows and macOS already, that will even make some
> patches
> and ifdef's useless we need now to sprinkle in all apps we really
> support on
> these platforms.
>

Definitely agree with this, having to add special handling to every
application to get a good experience on that platform is not ideal.

Having our Frameworks handle this in one place, with a consistent approach,
will overall improve the quality of the experience users get with our
software outside of a Plasma desktop environment (and reduce developer
porting workload) - and might help break some of the age-old stigma that
KDE apps have to be used with a KDE desktop environment.


>
> Greetings
> Christoph
>

Cheers,
Ben


>
> >
> > - Akseli
> >
> > ps. I am bad with mailing lists, lets hope this sends to right place
> > lol
>

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr">On Sun, May 5, 2024 at 8:37 AM &lt;<a \
href="mailto:christoph@cullmann.io">christoph@cullmann.io</a>&gt; wrote:<br></div><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">On 2024-05-04 21:56, Akseli Lahtinen wrote:<br> &gt; On Saturday 4 May \
2024 14:47:35 GMT+3 <a href="mailto:christoph@cullmann.io" target="_blank">christoph@cullmann.io</a> \
wrote:<br> &gt;&gt; My proposal: we enforce Breeze as icon set and style everywhere. And <br>
&gt;&gt; we<br>
&gt;&gt; provide still a way to overwrite that for the user, but if the user<br>
&gt;&gt; didn&#39;t set something manually,   idenpendent what the system propose, <br>
&gt;&gt; we<br>
&gt;&gt; just use Breeze. And we depend on that as dep e.g. in Kate, if you<br>
&gt;&gt; install Kate, that icon set and theme is installed.<br>
&gt; <br>
&gt; +1. For me as someone who changes icons sometimes just to see and <br>
&gt; tinker<br>
&gt; around,<br>
&gt; i think this makes sense. We have reliable fallback, but we still allow<br>
&gt; users to customize things which is, well, our thing! :)<br>
&gt; <br>
&gt; And if the custom icons break i do not end up with broken apps, so<br>
&gt; i really do not see any downside here, as user or dev perspective.<br>
<br>
Yes, if some user switches a theme or style in our system settings<br>
or in the application (like we do it with the color scheme switcher some<br>
applications like Kate have) that is fine.<br>
<br>
But beside that, we should just force our default style and icon set,<br>
like we do on Windows and macOS already, that will even make some <br>
patches<br>
and ifdef&#39;s useless we need now to sprinkle in all apps we really <br>
support on<br>
these platforms.<br></blockquote><div><br></div><div>Definitely agree with this, having to add special \
handling to every application to get a good experience on that platform is not \
ideal.</div><div><br></div><div>Having our Frameworks handle this in one place, with a consistent \
approach, will overall improve the quality of the experience users get with our software outside of a \
Plasma desktop environment (and reduce developer porting workload) - and might help break some of the \
age-old stigma that KDE apps have to be used with a KDE desktop environment.</div><div>  \
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> <br>
Greetings<br>
Christoph<br></blockquote><div><br></div><div>Cheers,</div><div>Ben</div><div>  </div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> <br>
&gt; <br>
&gt; - Akseli<br>
&gt; <br>
&gt; ps. I am bad with mailing lists, lets hope this sends to right place <br>
&gt; lol<br>
</blockquote></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]