[prev in list] [next in list] [prev in thread] [next in thread]
List: kwrite-devel
Subject: Re: How can i make kate behaviour go back to normal?
From: Waqar Ahmed <waqar.17a () gmail ! com>
Date: 2022-12-11 11:54:46
Message-ID: CAPesRH61QotkhxGAZWwPS8LWHzjhxAagxHJc88V+YsKPp_N0nw () mail ! gmail ! com
[Download RAW message or body]
> Not using a separate dialog isn't a viable solution for many KDE
applications. By making Kate differ from other applications you confront
the users with
different concepts which is against KDE's goal to present a common user
experience across all applications (unless there are good reasons to derive
from the common UX).
There are good reasons which I noted already. We do not need dialogs at all
when we can use our main view for something. Also we do not need to think
what size the dialog should be anymore. It just fits in the existing
window.
We diverge from kde experience in many ways where we think something else
is better or sometimes we just want to be more consistent with other
editors e.g code. E.g Ctrl + shift + f in Kate doesn't make the app full
screen and we use chord shortcuts which are rarely used by anyone else in
KDE. You also have to keep in mind that a lot of our users are not KDE or
even Linux users. So the kde consistency argument doesn't fully apply in
such scenarios.
Regards,
Waqar
On Sun, Dec 11, 2022, 4:17 PM Ingo Kl=C3=B6cker <kloecker@kde.org> wrote:
> [Please reply inline instead of TOFU. It makes following an argument much
> easier and it makes it much easier to remove irrelevant context from a
> reply.]
>
> On Sonntag, 11. Dezember 2022 11:58:03 CET Waqar Ahmed wrote:
> > Can you explain why this is worse UX?
>
> Not using a separate dialog isn't a viable solution for many KDE
> applications.
> By making Kate differ from other applications you confront the users with
> different concepts which is against KDE's goal to present a common user
> experience across all applications (unless there are good reasons to
> derive
> from the common UX).
>
> > This is an improvement, as it allows you to change settings without
> > reopening the dialog every time.
>
> This could have been solved easily by making the settings dialog not-moda=
l
> (like in Kleopatra and probably many other applications).
>
> > It also makes tweaking the theme and
> > editor settings a lot more pleasant which was just a crappy experience =
in
> > the past.
>
> I'm wondering what this has to do with the settings being presented in a
> dialog or embedded in the main window.
>
> Regards,
> Ingo
[Attachment #3 (text/html)]
<div dir="auto"><div>> Not using a separate dialog isn't a viable solution for \
many KDE applications. By making Kate differ from other applications you confront the \
users with</div><div dir="auto">different concepts which is against KDE's goal to \
present a common user</div><div dir="auto">experience across all applications (unless \
there are good reasons to derive</div><div dir="auto">from the common UX). \
</div><div dir="auto"><br></div><div dir="auto">There are good reasons which I noted \
already. We do not need dialogs at all when we can use our main view for something. \
Also we do not need to think what size the dialog should be anymore. It just fits in \
the existing window. </div><div dir="auto"><br></div><div dir="auto">We diverge \
from kde experience in many ways where we think something else is better or sometimes \
we just want to be more consistent with other editors e.g code. E.g Ctrl + shift + f \
in Kate doesn't make the app full screen and we use chord shortcuts which are \
rarely used by anyone else in KDE. You also have to keep in mind that a lot of our \
users are not KDE or even Linux users. So the kde consistency argument doesn't \
fully apply in such scenarios. </div><div dir="auto"><br></div><div \
dir="auto">Regards, </div><div dir="auto">Waqar</div><div dir="auto"><br><div \
class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Sun, Dec 11, \
2022, 4:17 PM Ingo Klöcker <<a \
href="mailto:kloecker@kde.org">kloecker@kde.org</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">[Please reply inline instead of TOFU. It makes following an \
argument much <br> easier and it makes it much easier to remove irrelevant context \
from a reply.]<br> <br>
On Sonntag, 11. Dezember 2022 11:58:03 CET Waqar Ahmed wrote:<br>
> Can you explain why this is worse UX?<br>
<br>
Not using a separate dialog isn't a viable solution for many KDE applications. \
<br> By making Kate differ from other applications you confront the users with <br>
different concepts which is against KDE's goal to present a common user <br>
experience across all applications (unless there are good reasons to derive <br>
from the common UX).<br>
<br>
> This is an improvement, as it allows you to change settings without<br>
> reopening the dialog every time.<br>
<br>
This could have been solved easily by making the settings dialog not-modal <br>
(like in Kleopatra and probably many other applications).<br>
<br>
> It also makes tweaking the theme and<br>
> editor settings a lot more pleasant which was just a crappy experience in<br>
> the past.<br>
<br>
I'm wondering what this has to do with the settings being presented in a <br>
dialog or embedded in the main window.<br>
<br>
Regards,<br>
Ingo</blockquote></div></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic