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

List:       kwrite-devel
Subject:    Re: SyntaxHighlighting Framework
From:       Christoph Cullmann <cullmann () absint ! com>
Date:       2016-09-28 21:39:32
Message-ID: 1030098740.434107.1475098772564.JavaMail.zimbra () absint ! com
[Download RAW message or body]

Hi,

> Hi all,
> 
> in the last month, Volker turned the SyntaxHighlighting into a
> framework on its own (essentially a rewrite from scratch). We are now
> at a point where we need to decide whether we want to release the
> first version next Saturday (tagging date for KF 5.27), or whether we
> want to postpone this by one month.
> 
> From what I can say the framework looks really good, is mostly
> documented, very well unit tested, and pimpled where needed.
> 
> As of now, it supports
> - all xml files we have (almost 300), compiled in as resource (all
> like in KTextEditor)
> - a highlighter class that can be used as QSyntaxHighlighter
> - a html file output highlighter (also used in unit test)
> - color themes, defined in *theme files (also compiled in as resource)
> - overwriting colors (itemDatas in xml, or even what KTextEditor has
> overwriting for each language for each theme independently)
> 
> From the QSyntaxHighlighter usage, and the HTML output we can say that
> the highlighting State that is accessible through API seems to provide
> what we need to keep the State in e.g. a KateTextLine or similar.
> There is also a demo app that uses this to incrementally highlight the
> text in a QTextEdit.
> 
> What's still missing is API to change themes (excluding the UI), and
> to save these again. This can be added later, but of course the needed
> API should not conflict with the current "read-only" API.
> 
> So I still think a closer look would be cool (cullmann?) :)
> 
> My personal feelings are we should not rush things (especially since
> we would loose just one month), but I also don't want to hold back a
> release if consensus is that it's ready :-)
> 
> If we agree to go for a release, we still have next week to withdraw
> this, since the real release typically is one week later after the
> tag.
As I was on project trip this week and will be bit busy in next 1-2 weeks
with releasing stuff, I would like to have it delayed one month
to be able to review the API once for real, which I did miss to do, sorry :(

I hope that would be ok.

Greetings
Christoph

-- 
----------------------------- Dr.-Ing. Christoph Cullmann ---------
AbsInt Angewandte Informatik GmbH      Email: cullmann@AbsInt.com
Science Park 1                         Tel:   +49-681-38360-22
66123 Saarbrücken                      Fax:   +49-681-38360-20
GERMANY                                WWW:   http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand
Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
[prev in list] [next in list] [prev in thread] [next in thread]