kde

Wish: Options for Kate’s Indenting Scripts

At the start of Kate’s indenting script for C/C++, the following options are available:

// BEGIN USER CONFIGURATION
var cfgIndentCase = true; // indent ‘case’ and ‘default’ in a switch?
var cfgIndentNamespace = true; // indent after ‘namespace’?
var cfgAutoInsertStar = false; // auto insert ‘*’ in C-comments
var cfgSnapSlash = false; // snap ‘/’ to ‘*/’ in C-comments
var cfgAutoInsertSlashes = false; // auto insert ‘//’ after C++-comments
// END USER CONFIGURATION

To set these options one would first have to actually find the indenting scripts under /usr/share, then copy it to one’s home directory to be able to modify it, and then modify the javascript source. This could – of course – be done in a much better way. In an ideal world options like these should be available in Kate’s settings as check boxes. It should also be possible to have non-boolean options, like choosing a value from a list of possible values for a setting.

I would love to see something like the following:

registerSetting(“Indent ‘case’ and ‘default’ in switch statements”, “cfgIndentCase”,  “boolean”);

produce

☑ Indent ‘case’ and ‘default’ in switch statements

in Kate’s settings.

I don’t have the time myself, but I don’t think it would be very hard, and I’m sure that many people would be a bit happier. Me and the other Kate developers would glady be of assistance. ☺

Kate’s Vi Input Mode — What will KDE 4.4 bring?

Please see http://kate-editor.org/kate-vi-mode/ for an updated overview of the Kate VI mode project.

Dear “Katevim” users.  Kate’s Vi Mode is steadily improving and I want to take a moment to tell what’s on the horizon for KDE 4.4. There has been quite a few bugs fixed since 4.3, but some major new features have also been introduced:

More >

How Kate got X-rated

(Ok, not really.)

Kate’s maintainer, Christoph Cullmann, shared a funny story over a beer one of the first days here at GCDS.

In ye olden days, what is now Kate and Kwrite was one application called “KWrite – KDE’s Advanced Text Editor”. However, the author of Kwrite mysteriously disappeared. Christoph forked Kwrite and continued working on it and after some time it greatly surpassed Kwrite’s capabilities and was becoming more of a power tool. A name change was long overdue.
Being a good German, Christoph decided to name it after the philosopher Immanuel Kant, so in KDE 2.1 the editor “Kant” was born.
For some strange reason, probably easier to understand for native English speakers, it was renamed to “Kate” in KDE 2.2. And thus what still is KDE’s Advanced Text Editor was born.

Google Calendar Plasmoid, Take Two

After the positive feedback on my quick 27 line python hack, I decided to make a slightly improved version. This fixes the two major problems with the old one: you can now use your Google Apps for your Domain email and you can use kwallet to remember your login.

gcal2

gcal_settings

It’s not a simple, 27 line python script any more, but now it’s much more usable. (unless there are some stupid bugs I have overlooked. :) )

As suggested I uploaded it to KDE Look: http://www.kde-look.org/content/show.php?content=104182, so you can install it from the “Add widgets…” dialogue or download it and install it with plasmapkg -i gcal-1.1.plasmoid.

More >

Google Calendar Plasmoid

Update: A new, better version can be found here:

http://hamberg.no/erlend/2009/05/07/google-calendar-plasmoid-take-two/

In case anyone is interested:

I made a simple Plasmoid for viewing coming events from Google Calendar. It’s simply a webview showing the iPhone version of Google Calendar. It’s written in Python and took 10 minutes to write (27 lines of code) by following the excellent tutorial on techbase.

gcal

You can download it here: http://hamberg.no/erlend/files/gcal.zip. If you improve it or make another Google Calendar plasmoid: let me know! :)

Oh, btw. To install it run plasmapkg -i gcal.zip.

P.S: openSuse users: I had to install python-dev to actually run a python plasmoid. Don’t know why.

Wikibooks, now also for us who like physical books

In “just” 19 days I’ll have completed my last exam for this semester and I can travel home for a nice, quiet Christmas with my family. As usual, I’ll travel by train, which takes 16-17 hours each way. Partly because it’s cheap (25 EUR), but most of all because it’s very comfortable and is a nice way to “stress down” after an intense exam period. As usual I’ll pack plenty of books and an iPhone with all the podcast episodes I have postponed listening to.

Among the new books I’ll bring there will also be at least one wikibook. Yes, a real, physical wikibook. :)
You see, I have been using the x86 disassembly wikibook quite often, and recently I read that there were a “a collection for print-on-demand publishing from PediaPress” available for the book. Being curious, I had to click the link to see what that actually meant…

It turns out that PediaPress will print a copy of a wikibook for a very fair price. It can even be your own compilation of parts of books (and Wikipedia support is coming, according to their webpage). Printing and shipping of the book (200 pages) to Norway was a little over 10 EUR.

I’m now sitting with three printed wikibooks in front of me, and the quality of the printed book are very good. Needless to say, I’m very happy. They even donate a portion of the proceeds to the Wikimedia Foundation (though, they don’t say how much).

Shiny new books

Shiny new books

Okteta

Okteta is of course mentioned :)

The Vi input mode for Kate is “done”

Please see http://kate-editor.org/kate-vi-mode/ for an updated overview of the Kate VI mode project.

I just marked the Vi input mode (“V.I.M.”? :) ) for the Kate kpart as done in the feature plan for KDE 4.2. It feels a bit weird to mark it as done, though, as there are tonnes of things I want to implement after KDE 4.2.

As you may know this started as a Google Summer of Code project and I’m quite happy with the way things have turned out. Since we are in feature freeze I would like to present the features that will be in the Vi input mode for the Kate part in KDE 4.2.

Kate Vi Input Mode in action

Kate Vi Input Mode in action – visual mode selection

More >

GSoC is over: The state of Kate’s Vi input mode

The Google summer of code programme’s coding part officially ended this Monday. That won’t be the last you will hear from me, though. Kate’s vi input mode has turned out to be quite nice, and there are lots of improvements I want to do in the coming months. The biggest news are a visual mode + visual line wise mode. Visual mode is one of those things that really make vim stand out from all of the vi clones, and having support for it makes Kate’s vi input mode it much more usable for me. More >

GSoC 2008: Vi input mode for the Kate kpart

I’m one of the lucky students doing a Google Summer of Code project for KDE, and I would like to introduce my project. I’m making a vi-like, modal editing mode for the Kate kpart. I’m doing this because many people—me included—find using a vi-like editor much more efficient and pleasant than using a non-modal editor. Especially for editing code. This will of course be an optional mode, and if you don’t want to use it, you will never notice it. This should be obvious, but I want to mention it because I have already gotten a reaction from a Kate user who were frightened to death when he heard the word “vi” and feared that I will destroy his beloved Kate. Fear not! :-)

More >