Developers

Introducing Kate GDB Plugin

Wednesday, 6 October 2010 | Kåre Särs | Tags: planet

Have you, like me, had to switch to an external debugger or run raw gdb in the terminal plugin to debug the C/C++ application you develop with Kate? That might not be necessary any more. There is now a “GDB Plugin” in trunk that gives you the power of raw GDB with some QAction candy for the most common actions.

I have always been a bit frustrated with not having a debugger directly in Kate, but too lazy/busy to start a debugger plugin project. Fortunately Ian Wakeling started this GDB plugin and got it off the ground. When I got introduced to it at Akademy, it triggered an itch in me to get this plugin into kdesdk and to add some features for the more point and click type of persons. As it seemed I had a bit more free time to spend on the plugin, Ian let me take over as maintainer.

Kate – GSoC Summary

Thursday, 26 August 2010 | dianat | Tags: planet

Hello planet,

As Google Summer of Code is now finished and I have successfully passed the final evaluation, I would like to give a brief description of my project.

Kate is now able to recover (most of) what was written after last save in case of a crash or power failure. A swap file is created after the first editing action on a document that was successfully saved. If the user closes the document normally or saves its content, the swap file is deleted, otherwise, if Kate crashes, it remains on the disk. On load, Kate searches for the swap file, and if it exists, a warning bar pops from the top and provides the user with three possibilities: recover the lost data, discard the swap file or view differences between the original data and the recovered one. If the user chooses to restore the lost data, the editing actions from the swap file are replayed over the current content of the document. If somehow the swap file is not valid, for example a finishEditing statement is missing, the recovery is done, but the user is warned that it might be incomplete.

Kate Night-Make

Monday, 23 August 2010 | Christoph Cullmann | Tags: planet

Each night now Kate (part/app) is build from git and all unit tests are run. Yeah, we even got some tests .P
Until now, that just reminds on of our failures ;) But I hope the daily mail will perhaps motivate me and others more to fix them ;)

Beside, thanks for all the people working to write these tests, like Bernhard, Dominik and Milian.

Kate Nightmake Tests From: cullmann@kate-editor.org To: kwrite-devel@kde.org Date: Today 05:06:46

[HANDLER_OUTPUT] Test project /home/www/kate-editor.org/build/build

Start 1: katetextbuffertest 1/34 Test #1: katetextbuffertest ............... Passed 0.02 sec Start 2: range_test 2/34 Test #2: range_test ....................... Passed 1.09 sec Start 3: testkateregression 3/34 Test #3: testkateregression ...............***Failed 0.03 sec Start 4: undomanager_test 4/34 Test #4: undomanager_test ................. Passed 1.34 sec Start 5: plaintextsearch_test 5/34 Test #5: plaintextsearch_test ............. Passed 7.56 sec Start 6: regexpsearch_test 6/34 Test #6: regexpsearch_test ................ Passed 8.45 sec Start 7: scriptdocument_test 7/34 Test #7: scriptdocument_test .............. Passed 1.36 sec Start 8: completion_test 8/34 Test #8: completion_test ..................***Failed 0.95 sec Start 9: searchbar_test 9/34 Test #9: searchbar_test ...................***Failed 11.24 sec Start 10: movingcursor_test 10/34 Test #10: movingcursor_test ................ Passed 0.94 sec Start 11: movingrange_test 11/34 Test #11: movingrange_test ................. Passed 1.79 sec Start 12: katedocument_test 12/34 Test #12: katedocument_test ................ Passed 1.09 sec Start 13: revision_test 13/34 Test #13: revision_test .................... Passed 0.63 sec Start 14: templatehandler_test 14/34 Test #14: templatehandler_test ............. Passed 0.44 sec Start 15: indenttest 15/34 Test #15: indenttest .......................***Failed 25.87 sec Start 16: bug213964_test 16/34 Test #16: bug213964_test ................... Passed 0.73 sec Start 17: utf8.txt_create 17/34 Test #17: utf8.txt_create .................. Passed 0.17 sec Start 18: utf8.txt_diff 18/34 Test #18: utf8.txt_diff .................... Passed 0.01 sec Start 19: latin15.txt_create 19/34 Test #19: latin15.txt_create ...............***Exception: SegFault 0.04 sec Start 20: latin15.txt_diff 20/34 Test #20: latin15.txt_diff .................***Failed 0.01 sec Start 21: utf32.txt_create 21/34 Test #21: utf32.txt_create ................. Passed 0.13 sec Start 22: utf32.txt_diff 22/34 Test #22: utf32.txt_diff ................... Passed 0.01 sec Start 23: utf16.txt_create 23/34 Test #23: utf16.txt_create ................. Passed 0.10 sec Start 24: utf16.txt_diff 24/34 Test #24: utf16.txt_diff ................... Passed 0.01 sec Start 25: utf32be.txt_create 25/34 Test #25: utf32be.txt_create ............... Passed 0.10 sec Start 26: utf32be.txt_diff 26/34 Test #26: utf32be.txt_diff ................. Passed 0.01 sec Start 27: utf16be.txt_create 27/34 Test #27: utf16be.txt_create ............... Passed 0.10 sec Start 28: utf16be.txt_diff 28/34 Test #28: utf16be.txt_diff ................. Passed 0.01 sec Start 29: cyrillic_utf8.txt_create 29/34 Test #29: cyrillic_utf8.txt_create ......... Passed 0.10 sec Start 30: cyrillic_utf8.txt_diff 30/34 Test #30: cyrillic_utf8.txt_diff ........... Passed 0.01 sec Start 31: cp1251.txt_create 31/34 Test #31: cp1251.txt_create ................ Passed 0.10 sec Start 32: cp1251.txt_diff 32/34 Test #32: cp1251.txt_diff .................. Passed 0.01 sec Start 33: koi8-r.txt_create 33/34 Test #33: koi8-r.txt_create ................ Passed 0.11 sec Start 34: koi8-r.txt_diff 34/34 Test #34: koi8-r.txt_diff .................. Passed 0.01 sec

82% tests passed, 6 tests failed out of 34

Total Test time (real) = 64.64 sec

The following tests FAILED: 3 - testkateregression (Failed) 8 - completion_test (Failed) 9 - searchbar_test (Failed) 15 - indenttest (Failed) 19 - latin15.txt_create (SEGFAULT) 20 - latin15.txt_diff (Failed) [ERROR_MESSAGE] Errors while running CTest </pr

Kate History ;)

Sunday, 15 August 2010 | Christoph Cullmann | Tags: planet

While setting up the new server for the Kate homepage, I actually found again old stuff ;)
Amazing that mails nearly ten years old can still be somewhere on the filesystem.
Perhaps a little hint, to post the beginnings of what today is Kate/KatePart/KWrite and KTextEditor.

Ten years ago, I asked the original author of KWrite, if he is interested in a MDI version of it (sorry, german, original mail):

SmartRanges goodbye

Friday, 13 August 2010 | Christoph Cullmann | Tags: planet

Like told in previous posts here and there, KDE 4.6 won’t have a KatePart that supports the SmartInterface but instead KatePart moves on to the new and shiny (and much simpler) MovingInterface for the handling of automatic moving cursors and ranges.

Now the big cut is done: KatePart in /trunk no longer implements the SmartInterface. KDevelop already adopted the new interface in a development branch, lets see how that all evolves.

Featured Articles

Thursday, 12 August 2010 | Dominik Haumann | Tags: planet

Looking back at the last month, migrating our Kate homepage over to WordPress was a vast success. The useful content we had on our old Drupal was copied over. The benefit of WordPress is that we now have a nice blog software as well with which we even aggregate some external blogs related to Kate. The new homepage is also more structured by having a list of featured articles showing useful resources, such as links to user or developer documentation. Read More

KDE 4.5 is approaching, thanks to all Kate contributors

Friday, 6 August 2010 | Christoph Cullmann | Tags: planet

KDE 4.5 will be released in the next days with the most polished Kate/KWrite and KatePart during the KDE 4.x series.

A lot of work went into fixing bugs and cleaning up old code for this release. Many important aspects where redone, just to enumerate a few:

encoding detection & handling
the text buffer
the undo/redo system (thanks Bernhard)
search/replace (thanks again Bernhard)
handling cursors and ranges
improved spell checking (thanks Michel)
improved indentation (thanks Milian)
speed improvements (Milian too)
better JS scripting (Dominik)
porting of KDevelop to new interfaces (David Nolden)

It will be the most unit-tested release of KatePart ever I guess, but still a long way to go until we have a good test coverage. (we just scratch the surface)

KateSQL, a new plugin for Kate

Thursday, 29 July 2010 | Marco Mentasti | Tags: planet

Hello,

today i will show you a new plugin for Kate, called KateSQL.
As you may have guessed, it brings to Kate the basic features of an SQL client, allowing you to open connections, execute queries, and display result data from SELECT statements or stored procedures.
Since this plugin makes an extreme use of the Qt Sql module, most of database drivers are supported..

Said this, let me explain how it works..

GSoC – View differences for Kate’s swap files

Tuesday, 27 July 2010 | dianat | Tags: planet

Hello,

As I stated in a previous post, the swap file feature for Kate is almost done. Back then, the view differences feature wasn’t ready, but now we have a basic implementation of it.

So now, by pressing the “View changes” button, a new KProcess is created, which receives as command line arguments the ‘diff’ program and the two files to be compared. One file is the original file on the disk, and the other one is represented by the recovered data read from the standard input. Then, Kompare launches, and there you can see the differences.

But sadly, at the moment you can’t merge the changes or some of them through Kompare, but I’m working on it. All you can do is see the differences and decide whether you want to recover the lost data or not. Close Kompare, and then press the “Recover” button or the “Discard” one, depending on what you want to do.

Join Kate Development!

Friday, 23 July 2010 | Dominik Haumann | Tags: planet

The Wheel of Time turns… meaning that the Kate Project has quite along history by now. The Kate Project was started back in December 2000, so it’s almost 10 years old. Development sometimes continues with a fast pace; and at other times there is almost no progress for weeks. But all in all, looking back at those 10 years, we can proudly tell you that the project is very much alive. Let’s take a look at the traffic of our mailing list: