In the last weeks, the homepage was sometimes down, as the server it is on is slowly dying. I just negotiate the transfer to a new one. That one will allow additional stuff to be run, guess we than even have nightly unit test runs (at least I hope so)
Therefor it may be, that the site is not reachable, as DNS transfer might always take some days.
kate-editor.org now contains all articles from the old page still applicable to Kate in KDE 4 and in addition all blog entries of Dominik which are Kate centric.
Beside that it will aggregate the blog entries of Milian for Kate
Still, a lot of work is needed. We already got an offer for help to beautify the page by a web designer, still content writers are missing. You have a nice short post about how to use Kate best? You have some howto? Just contact us or me in private. We can either give you an account on the page or just add your content if you like that more.
After some years of no real updates, beside the brave work of Dominik, a new kate-editor.org is launched.
It will be used to aggregate the blogs of the Kate developers and provide information about current development in Kate/KWrite/KatePart and guides for users.
Hope more people join the effort to once again provide a constant stream of up-to-date information.
I’ve added a new plugin to kdesdk/kate/plugin: a backtrace browser. It’s meant for developers and probably of no use for users. What does it do? It shows a backtrace delivered by gdb in a listview in a Kate toolview. Clicking on an item opens the selected file and jumps to the correct line number. It works for backtraces generated on your own machine, but it will also work for backtraces from other people, i.e. with /home/dummy/qt-copy/…/qwidget.cpp will still be found on other machines. For that to work, you have to index the directories where the source code is located.
Sometimes there are several files with the same name, e.g.
To pick the right choice, the plugin picks the last two parts of the url, in this case this would be
and then usually finds the correct one. Indexing trunk/KDE and branches/KDE/4.1 of course will lead to a clash, now way to fix it. Maybe I could present a list of valid files to the user and let the user pick the right one. I don’t think that’s necessary though for now.
How to configure
- Enable the plugin: go to Settings > Configure Kate > Application Plugins and enable ‘Kate Backtrace Browser’
- A config page appeared, so click on it and add the directories containing the source code
- Clicking OK will start indexing. It will take some time (the index of kdesupport + kdelibs + kdepimlibs + kdebase + kdesdk + playground/plasma + plasma-addons + kdevplatform + kdegraphics is about 6MB)
When indexing is finished, open the toolview “Backtrace Browser”. Now you can load a backtrace from the clipboard (e.g. when you clicked “Copy to Clipboard” in Dr. Konqi) or from a file.
Hope it’s useful