Christoph just added an awesome and long awaited feature: on-the-fly spellchecking. ‘Kate’s xml highlighting files now have an additional attribute in the itemData section: spellChecking=”true/false”. C++ comments and strings can be spellchecked now Same for all other languages such as Latex. Really big thanks to Michel Ludwig for the patch, good work! Screenshot for latex highlighting:
This blog is mainly about documenting the process how to run Kate Part’s test regression suite and probably not much use for other developers.
Step I: Setup the environment
- create the file ~/.testkateregression. The content of this file is a single line pointing to the folder of the checkout of the test regression suite data. For me this is
- Create the folder where you checkout the suite
- Change to this folder
- Checkout the data:
svn co svn://anonsvn.kde.org/home/kde/trunk/tests/katetests
Now all the data is there for testing.
Step II: Run the test suite
- go to your build directory of kate (e.g. kdelibs/build/kate/tests/
- run the complete suite:
- run specific tests, e.g. for the c indenter:
./testkateregression.shell -t indent/csmart
Just a quicky: I wrote a little plugin for KTextEditor which supplies you with basic error checking when you save documents. Currently only PHP (via
- usual tools for compiling C++, e.g. gcc.
- Qt development packages, i.e. under Ubuntu:
sudo aptitude install libqt4-dev
- KDE 4.2 with development packages for kdelibs and kdebase, i.e. under Ubuntu:
sudo aptitude install kdebase-dev kdebase-workspace-dev kdelibs5-dev. Note: You’ll need the experimental KDE 4.2 packages activated as of now, see for example the Kubuntu news on KDE 4.2 RC1 for hints.
- proper setup of environment variables, read this techbase article for more information. the
.bashrclinked there should be enough for most people
- For PHP support: a PHP executable which supports the
-lswitch for linting
Get the sources for the linter plugin from KDE SVN and compile it, using e.g. the functions supplied via the
.bashrc mentioned above:
- # go to your development folder
- # checkout sources
- svn co svn://anonsvn.kde.org/home/kde/trunk/playground/devtools/kte_linter
- cd kte_linter
- # build base linter plugin
- cd linter
- # build php linter plugin
- cd ../phplinter
- cd ../jslinter
- # update sycoca
- # start editor and select the plugins - happy coding!
Support for more languages
If you know good linters drop me a note. But it would be even better if you could write your own linter plugin. It’s pretty easy, take a look at one of the existing plugins for a skeleton & documentation.
Right now each plugin returns a hardcoded list of highlighting-modes which it supports for linting. This should be made configurable so that custom highlighting modes are supported
- make error messages more pretty
Last year I’ve blogged about the missing system monitor with the three bars for the panel and about its port to Plasma. Meanwhile other developers also did a port called System Status. In a collaboration with them we finally have the applet back in KDE’s subversion, the name is now “System Load Viewer” and it uses the data engine “systemmonitor” that already exists in KDE 4.2.
So if you want to have the plasmoid for your KDE4.2 desktop, it should be straightforward to compile/install.
On the screenshot you can see the plasmoid in action. There are two instances, one on the panel and one on the desktop. The one on the left is the KDE3 one.
It’s worth to mention that the plasmoid already supports more featues than the KDE3 version. Features include:
- show all cpus (for computers with multicores)
- tooltip updates continuously
- nicer visualization (maybe needs some more tweaks)
As soon as the KDE 4.2 freeze is over we’ll have to see where we can put the plasmoid to make sure it’s available for KDE 4.3