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.
Last but not least, I wish you all a good start into a happy new year 😉
Some days ago KDE 4.6 was branched. So what will Kate in KDE 4.6 bring?
- The new tree view as “Documents” sidebar completely replaces the old file list. It supports the simple list mode as well as a pseudo-intelligent tree view to group files. The “Documents” tab is now implemented as plugin (always loaded), meaning that it brought a code cleanup as well. We hope you like it!
- Swap file support, meaning that you can recover all your unsaved data for local files on the next Kate startup.
- Ability to always load plugins.
- New SQL Query plugin. The day we blogged about it had the most visits in the entire kate-editor.org history. So it seems the the SQL plugin is a really nice addon for web developers!
- New GNU Debugger (GDB) Plugin!
- New Highlight Selected Text Plugin.
- Ability to add scripts to the menu and bind shortcuts.
- Kate got a new homepage on http://www.kate-editor.org featuring WordPress.
- Lots of bugs fixed since the KDE 4.5.0 release.
- SmartCursors and SmartRanges are gone, resulting in more stable and clean code. MovingCursors and MovingRanges replace the old classes and work reliable. For instance, KDevelop is already ported leading to less crashes.
- Christoph found the emails of the early days of Kate again. A funny read!
- Daily unit test runs. We have more and more unit tests, securing the correct behavior of e.g. search&replace, the text buffer, encoding detection or indenters.
- Kate development mostly moved to KDE’s git infrastructure, resulting in very easy build instructions.
- The default settings of a session are now stored in the katerc file again, rendering the default.katesession obsolete. This means you will have to configure your default session again (sorry!). On the other hand, this fixed quite some bugs with regard to the session handling.
Credit where credit is due!
There were lots of developers involved who helped to improve Kate. Thanks a lot to every one of you! Without your contribution, Kate would not be what it is Keep it up!
Goodbye to Gitorious, welcome to git.kde.org.
You can find the Kate project here.
The “Get It!” page on the homepage is updated, too.
Push access is still restricted, but that will not last for ever 😉
Thanks to the sysadmin team of KDE, thanks guys, for all the work you put into the new infrastructure (and to help me with my faults 😉
And thanks to Gitorious, it was a nice time there, and I learned to appreciate Git, like many Kate developers (some appreciated it even before).
Like before, all changes in SVN and Git will be synced by me, as Kate is still released with KDE SC from SVN.
For the future I would like (and most kate devs, too) to develop solely in the Kate repository and have Kate released from there with KDE SC (instead spread over several modules).
But this must still be discussed with the release team after 4.6.
Beside, this means no split off from KDE, but it makes contributing to Kate that much easier, given atm you would need to checkout/clone kdelibs + kdebase + kdesdk and try to build there the Kate relevant parts, which is just no fun, if you just want to hack on some small bug or feature :/
We tried to move weeks ago already, but in our current repository some small glitches occured during the SVN => Git transition.
I have redone the conversion now and soon we will be on git.kde.org (if I not screw that again, thanks already to sysadmin for all help, now and in past!).
Still some small stuff will then need to be ported, which I will do after the initial repository is up there.
After this, the repository on Gitorious will vanish.
I will keep syncing KDE SVN and the repository, until KDE has migrated, too.
But please, if you work on features rather than simple oneliner fixes, use the git repository on git.kde.org after it is announced to be available.
You have automagically a git account and it makes merges for me much easier, if there are not too many conflicts from SVN -><- Git.
I hope the Kate team can keep the kate repository then as sole workspace, as working on the kate part/app is much easier for all contributors if you don’t have to get whole kdelibs/kdesdk. But that is still not discussed out I think, release team has a say here, as I would rather like to stay in KDE release cycle.