KDE-Forum.org

Not with ui.h but with the subclass approach.

It is too long ago that I used it. But I have no high opinion about Gideon. KDEStudio was very complete, everything worked, no ghostbuttons etc. Due the plugininterface of Gideon, Gideon lacks on useablity in my opinion.

I used KDEStudio in the KDE 2.x aera and that time it was much better, more finished than KDevelop. You can easily have subprojects and all open in the same workspace. The con is that it costs some money.

There are some karamba-applets on kde-look that do something like this in python.

Do you link against any KDE-library?

Dou you use these autoconf/automake-stuff? In this case you have to remove the file from Makefile.am and rebuild your automake/autoconf stuff. By the way: I REALY hate autoconf/automake. I think someone cannot make a buildsystem which is more stupid/complicated. I hate it a lot and suggest to use another buildsystem for example QMake. But it is not important which system you use instead of automake: Everything is better.

I have two different strategies: For certain dialogs I use a static function to show them for example in my custem QFileDialog. These dialogs are created in the static function and they are deleted after use. I create other dialogs for example a settings window in demand: I set them to null in the constructor and check before showing the dialog if the pointer is still null: If yes I create the dialog, if no I show the already cerated dialog. This is the recommend strategy for Qt/Embedd to gain s...

This cannot work because your icon is not in the app-icon-dir of kate but in one of the plugins dirs.

This is the way to do if you want to load icons for a KDE application that should follow the currently selected iconstyle. http://developer.kde.org/documentation/l…IconLoader.html

I think your version of Qt does not find the KDE-styles. You can set the directories in which Qt should search for plugins using the tool qtconfig. There you can also set the default style.