[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-03-02 16:53:49
Message-ID: CAN8d9g=P5R0NXeukGWQWPWKHpfcsRpweLheWwXVrBcC2MCpV7g () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


how about using GCC here? you don't have to build *everything* with clang…


2014-03-01 18:45 GMT+01:00 Milian Wolff <mail@milianw.de>:

> On Tuesday 25 February 2014 14:04:41 Milian Wolff wrote:
> > On Tuesday 25 February 2014 09:38:00 Christoph Cullmann wrote:
> > > > On Monday 24 February 2014 22:32:43 Michal Humpula wrote:
> > > > > On Monday 24 of February 2014 22:22:50 Dominik Haumann wrote:
> > > > > > Hi all,
> > > > > >
> > > > > > the list below provides 17 new default styles in addition to our
> > > > > > existing
> > > > > > 14 default styles, making it a total of 31 default styles. Albeit
> > > > > > this
> > > > > > sounds like a lot of default styles, the list makes a lot of
> sense
> > > > > > to
> > > > > > me.
> > > > > >
> > > > > > The list includes all styles that we discussed in the last two
> > > > > > rounds,
> > > > > > plus
> > > > > > dsPreprocessor, dsAttribute, and dsImport. I added dsImport
> since a
> > > > > > lot
> > > > > > of
> > > > > > languages have the concept of imports, modules, or include files,
> > > > > > and
> > > > > > other
> > > > > > text editors (e.g. vim) highlight these imports in a special
> color
> > > > > > (which
> > > > > > I personally like :p )
> > > > > >
> > > > > > A discussion is still welcome, although I'd be happy especially
> > > > > > about
> > > > > > Ship-it!-like feedback ;)
> > > > > >
> > > > > > The next step is to implement this in KF5.
> > > > >
> > > > > Is there a reason why this cannot be added to kate v3 too?
> > > > >
> > > > > I recall Christoph writing something about syncing the web syntax
> > > > > repository
> > > > > from ktexteditor in which case for kate v3 users those scripts
> will be
> > > > > unusable, right?
> > > >
> > > > 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 think it's already now a problem that there are some parts
> developed
> > > > in
> > > > v3 that are not yet in KF5: latest example is the new KateColors
> class
> > > > Milian added. In essence, we first have to port his code before
> touching
> > > > parts that may conflict with his changes.
> > > >
> > > > I'm pretty sure Milian will do pretty much everything that this hits
> v3,
> > > > too. @Milian: correct? ;)
> > >
> > > We will need to touch many syntax files and make them incompatible to
> old
> > > kate versions and we will need to change the API of KTE to include all
> > > that
> > > new enums.
> > >
> > > I really think we should do that only for KF5 and we should only make
> > > smaller changes to kate.git master.
> > >
> > > Milian's changes should be ported soon, or we loose them again.
> >
> > Yes, I hope to have time for that on the weekend. Whenever I tried to
> setup
> > buildsrc/KF5 I failed so far. Maybe I have more luck this time.
> >
> > Otherwise someone else can help me with it...? :)
>
> As you can see on the kde-frameworks-devel mailing list, I cannot build KF5
> since I'm apparently too "exotic" so far, for using ccache and clang. If
> someone wants to work on porting my two patches to kf5, it would be
> appreciated.
>
> It should be pretty straight forward, I think.
>
> Thanks
> --
> Milian Wolff
> mail@milianw.de
> http://milianw.de
> _______________________________________________
> KWrite-Devel mailing list
> KWrite-Devel@kde.org
> https://mail.kde.org/mailman/listinfo/kwrite-devel
>

[Attachment #5 (text/html)]

<div dir="ltr">how about using GCC here? you don't have to build *everything* with \
clang…<br></div><div class="gmail_extra"><br><br><div \
class="gmail_quote">2014-03-01 18:45 GMT+01:00 Milian Wolff <span dir="ltr">&lt;<a \
href="mailto:mail@milianw.de" target="_blank">mail@milianw.de</a>&gt;</span>:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Tuesday 25 February \
2014 14:04:41 Milian Wolff wrote:<br> &gt; On Tuesday 25 February 2014 09:38:00 \
Christoph Cullmann wrote:<br> &gt; &gt; &gt; On Monday 24 February 2014 22:32:43 \
Michal Humpula wrote:<br> &gt; &gt; &gt; &gt; On Monday 24 of February 2014 22:22:50 \
Dominik Haumann wrote:<br> &gt; &gt; &gt; &gt; &gt; Hi all,<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; the list below provides 17 new default styles in addition to \
our<br> &gt; &gt; &gt; &gt; &gt; existing<br>
&gt; &gt; &gt; &gt; &gt; 14 default styles, making it a total of 31 default styles. \
Albeit<br> &gt; &gt; &gt; &gt; &gt; this<br>
&gt; &gt; &gt; &gt; &gt; sounds like a lot of default styles, the list makes a lot of \
sense<br> &gt; &gt; &gt; &gt; &gt; to<br>
&gt; &gt; &gt; &gt; &gt; me.<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; The list includes all styles that we discussed in the last \
two<br> &gt; &gt; &gt; &gt; &gt; rounds,<br>
&gt; &gt; &gt; &gt; &gt; plus<br>
&gt; &gt; &gt; &gt; &gt; dsPreprocessor, dsAttribute, and dsImport. I added dsImport \
since a<br> &gt; &gt; &gt; &gt; &gt; lot<br>
&gt; &gt; &gt; &gt; &gt; of<br>
&gt; &gt; &gt; &gt; &gt; languages have the concept of imports, modules, or include \
files,<br> &gt; &gt; &gt; &gt; &gt; and<br>
&gt; &gt; &gt; &gt; &gt; other<br>
&gt; &gt; &gt; &gt; &gt; text editors (e.g. vim) highlight these imports in a special \
color<br> &gt; &gt; &gt; &gt; &gt; (which<br>
&gt; &gt; &gt; &gt; &gt; I personally like :p )<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; A discussion is still welcome, although I&#39;d be happy \
especially<br> &gt; &gt; &gt; &gt; &gt; about<br>
&gt; &gt; &gt; &gt; &gt; Ship-it!-like feedback ;)<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; The next step is to implement this in KF5.<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; Is there a reason why this cannot be added to kate v3 too?<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; I recall Christoph writing something about syncing the web \
syntax<br> &gt; &gt; &gt; &gt; repository<br>
&gt; &gt; &gt; &gt; from ktexteditor in which case for kate v3 users those scripts \
will be<br> &gt; &gt; &gt; &gt; unusable, right?<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; The only reason of not doing this for v3 is that v3 is very late in \
the<br> &gt; &gt; &gt; release cycle. If I am the one implementing these default \
styles, it&#39;ll<br> &gt; &gt; &gt; be<br>
&gt; &gt; &gt; for<br>
&gt; &gt; &gt; KF5, and then it can be backported. But we should try hard to \
avoid<br> &gt; &gt; &gt; regressions.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; I think it&#39;s already now a problem that there are some parts \
developed<br> &gt; &gt; &gt; in<br>
&gt; &gt; &gt; v3 that are not yet in KF5: latest example is the new KateColors \
class<br> &gt; &gt; &gt; Milian added. In essence, we first have to port his code \
before touching<br> &gt; &gt; &gt; parts that may conflict with his changes.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; I&#39;m pretty sure Milian will do pretty much everything that this \
hits v3,<br> &gt; &gt; &gt; too. @Milian: correct? ;)<br>
&gt; &gt;<br>
&gt; &gt; We will need to touch many syntax files and make them incompatible to \
old<br> &gt; &gt; kate versions and we will need to change the API of KTE to include \
all<br> &gt; &gt; that<br>
&gt; &gt; new enums.<br>
&gt; &gt;<br>
&gt; &gt; I really think we should do that only for KF5 and we should only make<br>
&gt; &gt; smaller changes to kate.git master.<br>
&gt; &gt;<br>
&gt; &gt; Milian&#39;s changes should be ported soon, or we loose them again.<br>
&gt;<br>
&gt; Yes, I hope to have time for that on the weekend. Whenever I tried to setup<br>
&gt; buildsrc/KF5 I failed so far. Maybe I have more luck this time.<br>
&gt;<br>
&gt; Otherwise someone else can help me with it...? :)<br>
<br>
</div></div>As you can see on the kde-frameworks-devel mailing list, I cannot build \
KF5<br> since I&#39;m apparently too &quot;exotic&quot; so far, for using ccache and \
clang. If<br> someone wants to work on porting my two patches to kf5, it would be<br>
appreciated.<br>
<br>
It should be pretty straight forward, I think.<br>
<br>
Thanks<br>
<div class="HOEnZb"><div class="h5">--<br>
Milian Wolff<br>
<a href="mailto:mail@milianw.de">mail@milianw.de</a><br>
<a href="http://milianw.de" target="_blank">http://milianw.de</a><br>
_______________________________________________<br>
KWrite-Devel mailing list<br>
<a href="mailto:KWrite-Devel@kde.org">KWrite-Devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kwrite-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/kwrite-devel</a><br> \
</div></div></blockquote></div><br></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] 

Configure | About | News | Add a list | Sponsored by KoreLogic