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

List:       kwrite-devel
Subject:    Re: qt4.xml -> qt.xml
From:       Milian Wolff <mail () milianw ! de>
Date:       2014-02-23 13:42:11
Message-ID: 4110666.nkr7AaxNlk () minime
[Download RAW message or body]

On Sunday 23 February 2014 14:32:11 Alexander Neundorf wrote:
> On Sunday, February 23, 2014 10:16:41 Sven Brauch wrote:
> > Hi,
> > 
> > On Saturday 22 February 2014 18:42:13 Milian Wolff wrote:
> > > Opinions?
> > 
> > I agree with you. The differences between languages are minimal on the
> > kate
> > highlighting level and do not justify the extra pain for users and
> > developers which is caused by maintaining two versions of the highlighting
> > files.
> > 
> > In Python, yes, the differences are very noticeable, but barely any of it
> > can be detected on the highlighter level. Especially since people often
> > write Python 3 compat layers nowadays to have Python 3 functions available
> > in Python 2 code too, which makes the distinction extra useless.
> > 
> > That something is highlighted by far doesn't mean it can indeed be used
> > anyways. I can come up with hundreds of cases where something is
> > highlighted but can't be used like that. The kate highlighting is a rough
> > help for reading code, not a semantics checker.
> > 
> > I think the distinction between the C++ highlighter and the C++/Qt
> > highlighter is useless already. Who cares about the occasional oddity of
> > having a Qt keyword highlighted somewhere -- I certainly don't. By
> > splitting it into a C++ and a C++/Qt highlighter and making the C++ one
> > default you'll take Qt highlighting away from 90% of users who will be too
> > lazy or too stupid (in the "I didn't know that existed" sense) to change
> > to
> > the Qt one. Why not at least have the Qt one be the default, btw?
> 
> +1

Personally, I'd also be in favor of having the Qt highlighter as default - 
it's what we had for years in Kate. Now we offer the purists a pure 
highlighting scheme which they can use if they so prefer. Best of both worlds, 
no?

Bye
-- 
Milian Wolff
mail@milianw.de
http://milianw.de
_______________________________________________
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]