Posts 

Hello everyone! In this post i am going to introduce the new Scripting IDE Plugin for Kate. Although scripting KatePart via ECMAScript is a powerful feature that has been available for quite some time now, it is still rarely used. In order to make it appealing for a wider public, the Script IDE aims at supporting the user with the process of creating and managing scripts. The Plugin mainly consists of a tree view which shows currently available scripts, as well as functions contained in these scripts. Additional scripts can be imported and new scripts can be created via a dialog, which requests necessary information about the script. Supported is the creation of all three types of scripts used in KPart: indentation scripts, command line scripts and API scripts. Further, help for command line scripts will be editable via the GUI. After i have finished some crucial refactoring, the future plan for Scripting IDE features involves auto-completion for available APIs in the document view, as long as the Script IDE Plugin is loaded. Also, some restructuring of the way KPart handles scripts will most likely be necessary. Read More

After some days of more hacking on the plugin, there current state is already nice for my daily use. A simple file like { "name": "Kate" , "files": [ { "git": 1 } ] } defines already the complete project for the kate.git. If you open any file with Kate inside your local kate.git clone (and the project plugin from master branch is loaded), Kate will auto-open the project and highlight the file you just opened there in the tree. No need to think about opening some project in the menu, just open the file you want to start working at and start. The project plugin won’t get into your way or require additional steps. Read More

Christoph already wrote several blog posts about the upcoming projects plugin. In his last blog, he mentioned that a project can now be created on-the-fly by reading the git or subversion output: All the files under version control are automatically listed as files in the project. However, this is restricted to git and subversion. If you always wanted to contribute to Kate, you can give other version control systems a try, such as Mercurial (command: hg manifest). Just quickly build Kate, and send us a patch! Read More

After bit more playing around with the project plugin, I did get aware that I am even to lazy to open project files. Normally if I need to fix something or add new features, I just go to the directory and open the source or build system files I need to work on. Therefore the project plugin now just watches which files you open and will load the corresponding project on the fly for you ;) (instead of naming your project, you create a .kateproject hidden file in the toplevel project dir, just like Git would do it with its .git directory) Read More

After a bit toying around, the first version of project management plugin has landed in the master branch of the kate.git. First time I developed a new feature in a feature-clone in my scratch space on git.kde.org. Very cool, KDE sysadmins did a GREAT job with that stuff: easy to setup and use ;) Now, people wanting to try out that, just clone our kate.git and compile the master branch. Example project is toplevel in kate.git: kate.kateproject Read More

Some years ago the Kate team introduced the “Session” feature. This allows you easily to keep around different Kate sessions for different work tasks, like coding, web design, writing, … Whereas I used that feature a lot at start during my normal daily work, I kind of no longer used it already since some years. For my normal work pattern: Checkout a project, fix something in it or code an extension, then hop over to the next one, the session feature doesn’t really provide the right workflow. Read More

It is easy and fun, please help to fix the remaining small things in the cleanups section of the frameworks branch. See here: http://community.kde.org/Frameworks/Epics/kdelibs_cleanups And use the nice and complete build howto here: http://community.kde.org/Frameworks/Building And yeah, I have already stolen some really easy tasks :) Don’t allow David to have all the fun.

Since the upgrade on bko, the bug charts were a bit broken. Thanks to our awesome sysadmins, this is fixed now: Example for Kate. In case you notice any wrong behavior, please let the sysadmins know immediately! Thanks :)

The Kate homepage will move to a new faster server. There will be some downtime in the next days, as DNS update will take some time and stuff needs to be setup on the new machine. Hope we are back with an even faster homepage afterwards ;)

Currently, we use our own passive notification bar to show a recovery bar when a swap file was found: Since version 4.7 we have a class called KMessageWidget (api documentation). Using KMessageWidget, the notification could also look like this: Imo, the new one looks nicer, as it much better distinguishes the notification popup from the rest of the ui. However, it several drawbacks: Read More