KNewStuff for KateSchemes?
Aleix Pol
aleixpol at kde.org
Wed May 18 18:46:55 UTC 2016
On Wed, May 18, 2016 at 6:35 PM, Dominik Haumann <dhaumann at kde.org> wrote:
> Hi Alex,
>
> you are missing the body of the mail. A mail without contents is
> typically not how we communicate.
>
> With respect to the topic: Yes, KNewStuff for schemas would be nice,
> but I would like to first discuss whether we shouldn't change the
> format of the exported schemas, and in general hour our hl schemas
> work.
>
> The format right now sucks:
> 1. Parts of the scheme are in kateschemarc.
> 2. other parts are in katesyntaxhighlightingrc
> 3. katesyntaxhighlightingrc looks like this:
> Base-N Integer=ffb08000,ffffdd00,,,,,-,-,,---
>
> In my opinion, this is not readable, therefore hard to maintain. And
> also the split in two files is the reason why we cannot simply ship
> one file that contains all colors.
I agree.
Maybe it would be a good idea to adopt someone else's format? Could
mean free themes...
http://colorsublime.com/
https://wiki.qt.io/QtCreatorStyling
> Instead, what I propose:
> - save each schema in one file.
>
> Then we'd have:
> - one Normal.kateschema
> - one Printing.kateschema
> - one Breeze Dark.kateschema
> - ... etc
>
> and in addition to that, I suggest that shipped schemas from us are
> read-only. If one wants to edit a schema one simply copies it (needs a
> button in the UI, like qt creator). This has the advantage, that if we
> ship updated ones, the user's schemas are not overwritten.
+1
> And I suggest that we choose either xml (like for our syntax
> highlighting) or JSON as format.
>
> When we have that, *then* I think KNewStuff is a good idea.
Aleix
More information about the KDevelop-devel
mailing list