Posts 

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

In KDE SC 4.8, Kate was extended by the line modification indicators. These indicators show you what lines currently contain unsaved data, but also lines that were once changed but now are saved to disk: With Kate in KDE 4.13, we have two new actions in the Edit menu: Move to Previous Modified Line Move to Next Modified Line In the screenshot above, moving to the next modified line does nothing, since we are already at the very end of the document. Moving to the previous modified line first goes to line 4, then to line 2, and finally to line 1. By default, no shortcuts are assigned, so if you you want to use this, it makes a lot of sense to configure shortcuts. Read More

I am the original author of the Lumen KTextEditor plugin and I am happy to announce, I just committed it to the Kate repository for KDE 4.13! Lumen is just the name for a plugin providing code-completion for the D programming language in KTextEditor/Kate and KDevelop. But Lumen is just a connection between the editor and the D Completion Daemon (a server providing all the information) called DCD. The plugin currently supports all major features of the completion server: feeding the server with import files, displaying documentation and several types of completion: Read More

From 18th to 25th of January 2014, the Kate, KDevelop and Skanlite developers met in Barcelona to work on these projects full time for a week. Full time usually implies about 14 hours per person a day (yes, besides food, we do nothing but developing). 11 developers working 14 hours a day for 7 days makes a total of 1078 hours. If we divide this by 8 hours, the typical amount of work hours in a day, this makes 134 man-days of work, or about 27 weeks of continued development time. While this calculation is a bit theoretical, it is still very valid to estimate the amount of work that is put into these projects during such a sprint, especially since usually developers have far less time for development in their spare time. Read More