Developers 

Hello!

Last week I focused on analyzing the interface of the actual implementation. Now, it’s time to develop the new interface.

As I mentioned in my proposal, one of my project’s goals is compatibility: I want to make as few changes as possible in the other sources. This is the reason why I studied the previous implementation for a whole week.

Another goal of my project is simplicity. The interface will be implemented in an abstract class. This class will be inherited by two other classes: one for C style languages (those who use elements like “{}”) and one for Python style languages (those who use indentation level to define the code blocks), as you can see from the diagram. I believe the code will be simpler and clearer if it is more specialized.

Hi everybody!

I am Adrian and, as Erlend already mentioned in a previous post, I will rewrite Kate’s code folding algorithm on this GSoC edition.

Starting from this week, I will post a weekly report of my work. At the end of each week I will post some info about the project’s progress and some details about what I have scheduled for the next week (according to my presented timeline).

Recently we’ve had several feature requests in comments of a blog post. If you are interested, you can easily implement this and contribute to Kate. And I’ll even show you how to get started for the following feature. First, build Kate according to /get-it/.

Adding support for ctrl+w {left, right, up, down} to switch the active view.

Kate has a vi input mode. This way, vim users can still use their default work flow but still use Kate at the same time. What’s missing in the current vi input mode implementation is support for view navigation. In vim, to move between different windows, press ctrl-w to switch to the neighboring view. Implementing this is rather easy – the following steps need to be taken care of:

This year’s Google Summer of Code (GSoC) has started and the Kate project has been lucky to get two students who will work on improving Kate’s folding code and Vi input mode.

[][1]

Adrian will work on improving the folding code which is in need of an overhaul:

My last post mentioned Necessitas which provides the means to have Qt on Android.
Whereas still a early preview release, it already allows you to compile and run Qt applications on Android >= 1.6 without any big hassle and integrates that into QtCreator!

I tried out the SDK in the last days, it is really easy to use and setup, like seen here and here (with good video that shows the steps).

After the latest changes in Nokia, I was kind of scared that “Qt Everywhere!” like printed on my nice bathing towel won’t really happen any more, at least not as fast as thought.

Now I got my new phone, Android based, and tried out Necessitas. And I must say, I am impressed. Just downloaded Ministro from the Android Market (yes, just like that, no rooting, no hacking, nothing) and the hello world demo and it runs :P

Thanks to the massive work of sysadmin and others (like Ian Monroe), kdelibs and kdebase are now converted to Git.

In parallel, the move of all kate related code to the kate.git was done and announced. Kate Part / App + KWrite reside now in kate.git on git.kde.org and this is the central place for kate development, like it was already before, but now without the shadow-copies in three other repositories.

As Dominik already points out in his blog, Kate has made nice progress for KDE 4.6.

Some of the latest fixes, like for some nasty search bug didn’t make it in RC1, btw., I was too lame with Git -> SVN syncs.
Anyway, I have now synced and backported to KDE 4.6 branch all pending fixes.

For the next KDE SC release 4.7 (here you go, I wrote SC :)), I hope this syncing will no longer be necessary.
At least Kate app + part + KWrite should then be only in the kate.git.
I can live with ktexteditor remaining in kdelibs, if removing that and still keeping BC and SC would be too much work. But part and app are at most runtime dependencies anyway.