Posts 

The yearly KDE conference Akademy just ended, so it’s time to look at what changed in the holy Kate in the Frameworks 5 land. KTextEditor Framework silent reload of document: Switching a git branch, Kate always pops up a dialog asking whether to reload the document. With this patch, if the document is version controlled by git, the git hash of the file computed and then it’s checked whether the file exists in git. If so, the file is reloaded without asking you. This should be very handy for developers using git! Thanks to Sven Brauch for this idea! new highlighting unit testing infrastructure several new syntax highlighting files cursor down in the last line in the document moves the cursor to the end of the line, same for the cursor up behavior, after just 8 years a bugzilla wish becomes true ;) properly load/save the search & replace history fix kateversion tags in all our >200 highlighting files, thanks to Martin Walch as always: lots of improvements to the vi input mode Kate Application use native dialogs on all platforms, including OS X, Windows split view: action to toggle splitter orientation the toolbar is by default turned off (see screenshot), resulting in a very cleaned up interface. You can turn it on in the Settings menu. new document switcher plugin (see screenshot) through Ctrl+Tab, providing quick access to the most recently used documents (similar to Alt+Tab in kwin), based on KDevelops code improvements to the tab bar revive, cleanup and improve the text snippet plugin by Sven Brauch projects plugin: autoload project even if no .kateproject is found (configurable to not clash with the auto-generated cmake .kateproject file), implemented by Michal Humpula the Plasma 5 applet to start a Kate session is back, thanks to the work of Josef Wenninger A big thanks to the organizers of this year’s Akademy, and a big thanks to all our sponsors and supporting members. The location was amazing and the venue allowed us all to have a very productive week! Looking forward to next year! :-)

Only some days until the yearly Akademy starts. Its a real great thing to get known to other KDE/Qt contributors and meet old and new friends. Already amazed, lets hope the airlines don’t go on strike during my travel :=) See you all there, lets have fun & be productive! Already now thanks to all people that help to organize this cool event and all our sponsors!

Hi, from today on, the master branch of kate.git is KF5 based. That means, for the next KDE applications release after 4.14, Kate will use the awesome KF5 stuff! The KTextEditor framework is already in a good shape and most active KatePart development is since months pure KF5 based. The same should now be true for Kate itself (and KWrite). Pâté will need a lot of love, as PyQt5 is there, but PyKDE5/PyKF5 still in the works. Read More

You like KDE software? You like to have a polished and nice KDE Frameworks 5 release? But you can’t help out yourself by coding, translating, bug finding, designing, documenting and whatever? => Feel free to fund our Randa Meetings 2014. Perhaps it feels strange that a free/open source project wants money, but sprints & meetings are not for free, given you need to pay for the accommodations, travel, rooms for hacking, … Read More

Just like some time ago, here are several links that might be of interest: C++11 compiler support overview Five new algorithms to C++11 that you should know about: Interesting read about std::all_of, any_of, none_of, is_sorted, is_sorted_until, is_partitioned and some others. (And here some more generic numeric algorithms) noexcept – what for? An interesting read about C++11’s noexcept. Also interesting: Scott Meyers’ thoughts. An overview of C++14 language features: Mostly highlights constexpr and auto All about C++11 move semantics Number and string conversion in C++11 What you should know about C++11 Lock-free data structures (part 1, part 2) Use of assertions Static code analysis of Qt5 Interpreter pattern vs. stack-based bytecode interpreter: very good introduction to bytecode interpreters Overview of design patterns Programming sucks: There is quite some truth in this, although this is probably less valid in open source projects.

Happy news arrived on the kwrite-devel mailing list with this post before Easter ;) Kate has won the advanced text editor comparison in the Linux Voice magazine – Issue 2, yeah ;) Nice to see that our work on Kate is awarded. About Linux Voice: Seems to be some pretty new magazine about Linux & Open Source (Issue 2 says it all) and they promise to give 50% of their profit back to the Free Software community, developers and events. Hope that works out, it is a nice goal. Read More

Since version 4.10 Kate comes with a simple project plugin, as introduced here . The project plugin works by automatically reading a simple json file and providing the information found there to various parts and plugins in Kate. “Opening” a project Projects are opened automatically by Kate. Whenever a file is opened, Kate goes the directories from that file upwards until it finds a file named .kateproject , which defines the project. This is a simple json file, which is intended to be written manually by the user. Read More

This is sort of a poll: Please write in the comments below exactly one line about what you like on Kate, and one line what you want improved. Please spread the word so we get a lot of feedback – Thanks! :-)

Kate comes with a build plugin, which supports running make, or ninja, or actually any arbitrary command directly from within Kate. This is obvisouly useful when using Kate as development editor, and this plugin has seen several improvements for the 4.13 release. A small change, but for affected developers a major improvement, is that Kate can now parse warning and error messages from the Intel compilers, icpc and icc. So for those of you using icpc, Kate can now automatically jump to the line of code which caused the error. Actually you don’t have to wait for 4.13 for this, it is already available since 4.12.3. Read More

Kate Part gained 17 new default styles in addition to the existing 14 default styles. These changes are available for Kate based on the KDE frameworks 5 initiative and currently live in ktexteditor.git module. Default Styles are predefined font and color styles that are used by Kate Part’s syntax highlighting. For instance, Kate Part always had a default style for comments. Therewith, the comments in all syntax highlighting files look the same (by default, a gray color). Or keywords are by default always bold and black. Read More