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

List:       kwrite-devel
Subject:    Re: Final list of default styles
From:       "Philipp A." <flying-sheep () web ! de>
Date:       2014-02-25 13:30:31
Message-ID: CAN8d9g=Z49AJUwV_vdPK42ZM8KiQqkaVO4hAYyFdnb6QzPjqQA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


i'm glad about the list of styles that made it: they also make a lot of
sense to me, and even if someone might find it a tad much: nothing forces
anyone to use every available style :)

i'm pretty sure that (apart from the numerous number styles) most scripting
languages will make use of all.

2014-02-24 22:48 GMT+01:00 Dominik Haumann <dhaumann@kde.org>:

>  The only reason of not doing this for v3 is that v3 is very late in the
> release cycle. If I am the one implementing these default styles, it'll be
> for
> KF5, and then it can be backported. But we should try hard to avoid
> regressions.
>

i'm only a bit sad about that part. earlier adoption → faster porting of
the styles.

i think regressions are hardly plausible and the backporting should be
straight-forward if all that's added are enum values and documentation? or
am i missing something?

best, phil

[Attachment #5 (text/html)]

<div dir="ltr"><div>i'm glad about the list of styles that made it: they also make a \
lot of sense to me, and even if someone might find it a tad much: nothing forces \
anyone to use every available style :)<br><br></div>i'm pretty sure that (apart from \
the numerous number styles) most scripting languages will make use of all.<br>

<div><div><div class="gmail_extra"><br><div class="gmail_quote">2014-02-24 22:48 \
GMT+01:00 Dominik Haumann <span dir="ltr">&lt;<a href="mailto:dhaumann@kde.org" \
target="_blank">dhaumann@kde.org</a>&gt;</span>:<br><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">

<div class="">
</div>The only reason of not doing this for v3 is that v3 is very late in the<br>
release cycle. If I am the one implementing these default styles, it&#39;ll be \
for<br> KF5, and then it can be backported. But we should try hard to avoid<br>
regressions.<br></blockquote><div><br></div><div>i'm only a bit sad about that part. \
earlier adoption → faster porting of the styles.<br><br></div><div>i think \
regressions are hardly plausible and the backporting should be straight-forward if \
all that's added are enum values and documentation? or am i missing something?<br>

<br></div><div>best, phil<br></div></div></div></div></div></div>



_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel


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