Skip to content

Adymo 

Kyzis + KDevelop

Sunday, 22 August 2004
Today I've finished KTextEditor::CodeCompletion and PopupMenu interfaces for Kyzis text editor (those who don't know about the editor should visit http://www.yzis.org). Now the editor works like a charm with KDevelop. Vi(m) fans should check for a first IDE with vi-like text editor ;) Editor is still in development but it's in a good shape now, everyone interested is welcome to try it out and help the development of an editor itself and a kdevelop integration process ;) Read More

KDevelop Assistant

Friday, 7 May 2004
Every time I wanted to look at documentation, I started Qt Assistant for Qt API and Konqueror for KDE API. This annoyed me for quite a long time. I always dreamed about a program like Qt Assistant capable of browsing KDE API and indexing it. KDevelop had something like that for ages, it was an old documentation plugin. But it has two problems - it's index was really slow and unusable and the viewer could not be run standalone. Eventually I decided to fix that problems and now I'm proud to present KDevelop Assistant (kdevassistant). It is the only documentation viewer that is capable of browsing, indexing and full text searching various types of API docs in your system. Currently it supports Qt API, KDE API and Devhelp (GTK/GNOME) docs, support for new types can be added in a hour by creating a documentation plugin. Check out KDevelop CVS HEAD to get not only the best IDE in the world but also the best API documentation viewer ;). Screenshot: [image:458] Read More

The generic approach to property editing

Monday, 16 February 2004
Last time I worked on Kugar Report Designer I've noticed that I need to have a property editor similar to what Qt Designer have. Further I've discovered that such a property editor can also be usefull in KDevelop. Existing implementations were too tied with Kugar Designer and Qt Designer and Qt Designer's version was GPL'ed. So I decided to wrote my own "generic" property editing library (partially based on my property editing classes from Kugar) which I'm happy to present. The core of the library is formed by Property, PropertyList and PropertyEditor classes. Property has name, value (stored in QVariant), description and a list of possible values. Library supports (i.e. provides facilities to edit them visually) several property types by default: String, Integer, Double, Boolean, StringList, Color, List, Map, ValueFromList, Symbol and FontName. Class PropertyList is a way to store properties together. It is worth to mention that properties can also be grouped into a smaller lists within property list. For example, such properties as "x", "y", "width" and "height" can be grouped into "Geometry" group. Your object should include a PropertyList. This way it is simple to pass the list to PropertyEditor and display them in GUI. PropertyEditor cares about displaying a grouped list of properties and creating property editor widgets when necessary. Sometimes there is a selection of objects in program and you want to display properties of those objects. You can't simply pass a list of properties to a property editor, you should "intersect" them first and pass only properties that are common to all objects. Property editing library takes care about this too. Property lists can be intersected and the result of intersection can be passed to PropertyEditor. The use of properties and lists can be illustrated by this example: Read More