Before everything else, I want to send a big “thank you” to our hard-working sysadmins who spent so much time and effort recently on fixing the git servers! It’s working nicely again.
kdev-python without modified Python fork
Until now, kdev-python’s repository contained a fork of Python. This fork was modified from the official version of Python to fix some issues which were counteracting its use as a parser in an IDE. Fortunately, a patch of mine now was accepted upstream which solves most of the issues, so in the future, the fork will not be necessary any more. Unfortunately tough, the patches changes are not binary compatible, and thus will only go into the next feature release of Python (3.4), and also cannot be backported. This means that the Python 2 version of kdev-python will have to stay with the fork.
This also means that plans for Python 3 in kdev-python support have changed: since I don’t want to maintain three versions (python2, python3 with fork, and python3 without fork) the official release of kdev-python3 will have to wait for the release of Python 3.4 (early 2014). I’m sorry. If you need it, either build the (now unmaintained) python3 branch, or build Python 3.4 from mercurial and build kdev-python’s python3-nofork branch against that. Alpha releases of Python 3.4 are going to happen soon-ish, you should also be able to build against those.
Apart from this local (in time) trouble however this is great news for kdev-python — it’ll make it much easier to maintain and adjust to future releases of Python, also it’ll be easier to package, use less memory, and less disk-space (one can question the relevance of the two latter points of course 😉
New features in kdev-qmljs
After all that dry and difficult hacking on python’s and kdev-python’s AST, I wanted to do something fancy. So, I made this:
|Inline color picker in kdev-qmljs|
It should be rather self-explaining what it does. It needs a slight change to kdevplatform, so you need to update that too if you want to try it. I also made similar popup widgets for a number of other things in QML too:
|Inline popup widget for modifying item spacing|
Those widgets always show a generic preview image and allow modifying a property with a slider or similar. They’re written in pure QML, so it’s easy to add more widgets for other properties (adding a new widget currently requires a one-line-change in C++ tough, this might be useful to change in the future to make it easy for users to add their own widgets).
I know that the usefulness of those is questionable. The color picker is useful for sure, but about the rest… I don’t know. It seemed like a good idea, so I tried it out — opinions, ideas and other feedback is welcome.
Oh, the color picker currently doesn’t work with alpha colors, I know, I’ll fix it some day.
New splash screen for kdevelop
Another thing which was a victim of my “I want to do something fancy” streak was kdevelop’s splash screen. It’s now also written in mainly QML, and gets progress info from kdevplatform. It looks like this:
|KDevelop’s new splash screen.|
The progress steps might need a bit of work. The timing is not accurate here, I had to pick few frames to get a reasonable file size.
Oh also, look what awesome old splash screens you can find in the current kdevelop repository: