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

On T= uesday 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 a= ddition 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 make= s 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 t= oo?
> > > >
> > > > 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 st= yles, it'll
> > > be
> > > for
> > > KF5, and then it can be backported. But we should try hard t= o avoid
> > > regressions.
> > >
> > > I think it's already now a problem that there are some p= arts developed
> > > in
> > > v3 that are not yet in KF5: latest example is the new KateCo= lors class
> > > Milian added. In essence, we first have to port his code bef= ore touching
> > > parts that may conflict with his changes.
> > >
> > > I'm pretty sure Milian will do pretty much everything th= at this hits v3,
> > > too. @Milian: correct? ;)
> >
> > We will need to touch many syntax files and make them incompatibl= e to old
> > kate versions and we will need to change the API of KTE to includ= e 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 agai= n.
>
> 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 cann= ot build KF5
since I'm apparently too "exotic" so far, for using ccache an= d 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