As a quick notice: The highlight selection plugin was not removed in KDE SC 4.10.0. Instead, a silly bug results in not loading the plugin. This is fixed for DKE 4.10.1. If you cannot wait, you can find a workaround here
The project plugin in kate.git master has now the ability to call cppcheck.
This is just hacked in at the moment and needs more love, but it works.
Feel free to contribute integration of other code checkers, cppcheck is only the first, I hope 😉
According to our release schedule, KDE SC 4.10.0 will be available to the public in early February 2013. Following Kate in KDE 4.7, Kate in KDE 4.8 and Kate in KDE 4.9, this blog post highlights what’s new in Kate in KDE 4.10.
- Kate Part got a unified notification system. It’s used in several places already, for instance for remote file loading, data recovery and Search & Replace information.
- Kate Part can now be configured to show a minimap of the document instead of a scrollbar. The minimap shows text in a miniature view and is useful for fast text navigation in the document. While the feature itself is stable, it may be changed and should be considered experimental. Feedback is welcome on our mailing list.
- Kate Part got several predefined color schemes. Feel free to contact us with improvements.
- Kate Part shows the current line while scrolling.
- Kate got an integrated Quick Open feature (ctrl+alt+o) for fast file navigation.
News in the Plugins World
- Kate’s Pate plugin now provides several new plugins by default, with Python 3 support.
- Kate gained a new and very powerful Project plugin with ctags code completion. It is tightly integrated with the Search & Replace plugin as well as the GDB Plugin and the Quick Open feature.
- Kate Search & Replace plugin gained find-as-you-type support.
- Kate Part’s remove trailing spaces feature is improved.
- Kate Part’s scripting API gained several new features (e.g. zen coding script). The API now is more fine grained, e.g. you now need to “require(“cursor.js”);” in order to have the Cursor API.
- a lot of other little improvements, see our bug tracker for a full list.
Most of the following work was done during the yearly KDE conference and especially the joint Kate/KDevelop meeting this October in Vienna. A massive bug database cleanup was performed mainly by Christoph, so we closed several hundreds of bug reports, where ~280 are really fixed. So we are down to a total of 400 reports (only 70 of these 400 reports are bugs), where we initially had > 800 open issues. This also is reflected in the Kate bug charts:
Thanks to all contributors to make yet another release rock! And as always: We are happy for every contribution, so check out the Kate sources and send us patches! We hope you enjoy using Kate as much as we enjoy its development
Being vaguely aware that Python3 had some “interesting” differences compared to Python2, I had decided to not think about Python3 for now, but then one of our dear users piped up to say that even building it was broken! That seemed weird, so I started poking around only to find myself falling Alice-like into a Wonderland where strings were not always strings…
Well, I’ve long been interested in i18n and l10n in all their forms, especially as they apply to Indic languages, so I was somewhat aware of the sorts of issues that Unicode can throw up. Luckily, as a KDE developer I’m used to depending on QString handle all the routine grunt work so it was a bit of a rude awakening to discover that, the C API for Python strings takes many forms:
- Python 2.x has 2 run-time variants with 3 compile-time variants.
- Python 3.2 or less has 3 compile-time variants
- Python 3.3 or greater has 3 run-time variants
- Ubuntu does not yet have 3.3.
- The cmake support in KDE before 4.9.4 cannot find the right libraries.
- The PyKDE4 support for strings was broken-then-fixed.
- Python3 pickles structures differently than Python2.