Tag: kdevelop

Collaborative editing in KTE (prototype)

I had a bit of spare time, so I decided I’d try to implement collaborative editing in KTextEditor, and see how far I can get in a week. That week is over now — and this is how far I got: Your browser does not support the video tag. (If your browser doesn’t support HTML5 video, here’s a direct link) Technical implementation In the background, all this is based on […]

Continue Reading →

Various news in kdevelop, kdev-python, kdev-qmljs

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. Other than that, there’s various news in kdevelop-land: kdev-python now has a branch which builds against upstream python 3.4 (which is not released yet), there’s a few fancy new features in kdev-qmljs (QML / javascript language support for […]

Continue Reading →

Vienna kdev/kate sprint: kdevelop settings dialog and changes to kdev-python

In an effort to improve the overall quality of KDevelop’s user interface, Aleix and I polished the settings dialog of KDevelop. Since the Kate guys challenged us by showcasing their “awesome” gimp skills, I feel like I have to do that too: Comparison between the old and the new configuration dialog in KDevelop  There wasn’t really any changes to functionality, it’s just supposed to look better and be more understandable. […]

Continue Reading →

Vienna kdev/kate sprint: First kdev-python beta release and python3 support

This is the third day of the KDevelop / kate sprint in Vienna, and it’s really fun and productive so far! There’s several new things related to kdev-python which I’d like to write something about. Beta release First of all, there’s a first official beta release of the python plugin, which is to be used with the (new) 4.4 (resp. 1.4) stable versions of kdevelop / kdevplatform! You can download […]

Continue Reading →

Improved code completion in kdev-python and call for help

I recently rewrote most of kdev-python’s code completion code, as it was a huge mess (it relied largely on regular expression matching, which just isn’t powerful enough to do this properly). The result is less buggy, easier to maintain, and has unit tests (yay!). In the process, I also implemented quite a few features which I want to post a few screenshots of. There’s a second issue I want to […]

Continue Reading →

Debugging support in kdev-python

There’s now support for (graphically) debugging python applications from within KDevelop, like it works with C++. The implementation relies on communicating with the default python debugger, pdb, which is shipped with python. It aims to nicely map all of pdb’s features to buttons and tooltips / toolviews. kdev-python debugger in action Features Key features include: Step through code using the well-known “next”, “continue”, etc. buttons; KDevelop will automatically open up […]

Continue Reading →

About Python 3 support in kdev_python

Just a quick note about Python 3 support in the kdevelop python plugin: I will switch over to supporting Python 3 language features as soon as there’s a release of the Django web framework using Python 3 (as this plugin was originally intended for developing Django applications, this seems like a reasonable point in time to me). Most (all?) of the (syntactic) features Python 3 has so far are in […]

Continue Reading →

kdev-python: Argument type guessing, advanced list content type support and more

It has been a while since my last post about kdev-python, the python language support plugin for KDevelop; I have been quite busy recently. Neverthereless, I got quite a few cool features (almost) finished now. First, there’s support for argument type guessing. So whenever you call a function, KDevelop will try to find out the type of the parameters you passed, and add them to the possible types for that […]

Continue Reading →

Basic List content type support in KDevelop-Python

Hey, after dealing with a few difficult problems, I finally got a first prototype of the “list content type support” implemented: Doesn’t look very impressive? It isn’t, yet. But: The plugin now tracks which kind of data a list contains, and when accessing the list in one or another way, it uses that information to guess the type of the resulting objects. This is not very advanced yet, but it […]

Continue Reading →