Saturday most Kate developers will depart, therefore now the most work has been finalized (or at least brought to some intermediate state that works OK).
Below, the mandatory screenshot, Kate started without any configuration set in the framework branch, new and shiny:
Find the differences
And one screenshot with some files open:
After the first initial status bar integration into the KatePart, we thought a bit more about what users might expect. Looking at the competition, one common feature is to allow quick-switching the indentation settings.
Joseph gave that a try and we now have an even better version available in the KF5 KTextEditor framework.
Mandatory screenshot (KWrite, Kate or other applications using it will look the same), updated version after feedback below:(Update: Using now again non-bold + Line/Column swapped with status)
Just started to introduce a default status bar to KatePart.
Instead of forcing all applications to implement an own one with varying quality and features, it provides a default status bar that is an improved variant of the status bar of the Kate application. Now Kate and KWrite have exactly the same features there
If the host application doesn’t want that, the KTextEditor interface allows to deactivate it completely.
The new status bar allows e.g. finally to switch the file mode (== highlighting) and encoding directly from the status bar
Here we sit, in Barcelona, hacking away at KTextEditor & Kate.
During the first 2 days, we already got some stuff done, like cleaning up KTextEditor interfaces and port more parts to KF5 (like ctags plugin, sql plugin, …).
More and more, KTextEditor & Kate get into a usable state for frameworks
It is really good to have some free days in a nice location to focus on that goal!
We will not fundamentally change a lot of stuff but really concentrate on long term items we had on the radar for the 4.x => 5.x change and on having a GOOD 5.0 release that is as usable as the 4.x series with hopefully only as few regressions as possible.