Designed with Quanta
Sponsored by Kitty Hooch
Welcome to the Kommander FAQ
This FAQ is extracted from our main FAQ and is specific to Kommander and common items such as install.
What is the KDE version the kdewebdev module relies on?
Quanta Plus, Kommander and the rest of kdewebdev usually require the latest or the second latest stable version of KDE. Quanta 3.4.0 will run on KDE 3.4.0 or KDE 3.3.x, Quanta 3.3.0 will run on KDE 3.3.0 or KDE 3.2.x. The newest KDE version is always recommended, as some things might miss in Quanta or will not work as expected if you use an older KDE version. This is especially true for the VPL mode, which heavily relies on the KHTML browser engine. The situation is a little bit different when we talk about major releases, as Quanta Plus 3.0 will not run on KDE 2, and Quanta Plus 4.0 will not work with any KDE 3.x releases either.

[return to top]
Where can I download the latest version of kdewebdev?
Quanta, Kommander and the rest of kdewebdev is released together with KDE, so you should find it on ftp.kde.org and its mirrors.

[return to top]
Where can I download the latest version of Kommander?
Kommander is released together with KDE in the kdewebdev module and also released separately as development releases. During the end of a release cycle for KDE check the dates on development releases as they may be older. After a major version or major point version of KDE look for Kommander development releases at kde-apps.org or on sourceforge.

[return to top]
Can I develop for users on a development version of Kommander?
Kommander development releases are designed with the idea that new widgets and features may be introduced, but primarily it is intended to be very easy to be backwards compatible with the last main release of the executor. Our release goals are to enable capabilities in the executor first so that we can release updates to the editor and those features can be used. We plan to have a feature list on site to help with this and we also have error testing to help users when something needed is not found. The best way we can help is if you join our Kommander users mailing list and ask questions.

[return to top]
How can I get the SVN version?
To have access to the latest (not-released) development version you can check out KDEWebDev from the KDE Subversion server.
The following instructions show you how to download and install the most up to date version of the stable KDEWebDev branch. These instructions will create a directory called kdewebdev as a subdirectory of whatever directory you run the svn command from.
To find a Subversion mirror check out the anonymous SVN page for a mirror close to you.
Checkout the kdewebdev module:
[~]$ svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdewebdev
[~]$

Compile Quanta and the other kdewebdev applications:
[~]$ cd kdewebdev
[~/kdewebdev]$ make -f Makefile.cvs
[~/kdewebdev]$ ./configure
[~/kdewebdev]$ make
[~/kdewebdev]$ su -c make install
[~/kdewebdev]$

Update the kdewebdev sandbox at a later date, and recompile.
[~]$ cd kdewebdev
[~/kdewebdev]$ svn update
[~/kdewebdev]$ make -f Makefile.cvs
[~/kdewebdev]$ ./configure
[~/kdewebdev]$ make
[~/kdewebdev]$ su -c make install
[~/kdewebdev]$

To get a the latest stable branch during the first checkout supply the branch path to the svn command. For example getting the latest 3.5.x version you must do:
[~]$ svn co svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kdewebdev
[~]$


To switch a checkout to another branch (for example trunk to 3.5) use:
[~]$ cd kdewebdev
[~]$ svn switch svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kdewebdev
[~]$


The latest development version from the 3.x series is in /home/kde/branches/KDE/3.5/kdewebdev.
NOTE:The current code under trunk will contain the upcoming Quanta4 release. It is unusable at this time, so please do not check out and try to compile.

[return to top]
Can I use a GUI tool to get Quanta from SVN?
There are some GUI frontends to Subversion. Google for the following applications:
  • kdesvn: KDE SVN client
  • eSvn: Qt SVN client
Cervisia, the current KDE CVS client will also have subversion support in the near future.

[return to top]
How do I use a Kommander dialog with Quanta?
Kommander dialogs are visually created with the Kommander editor (kmdr-editor) and executed with the Kommander executor (kmdr-executor [path/]dialog.kmdr). One very useful way to use Kommander dialogs with Quanta is to use Quanta's script-like Actions from the Configure->Actions menu. You can make the dialog echo text to stdout, which is how it would go to the command line in a shell. Using this technique you can select to output into the editor, for instance inserting at the cursor. This enables you to build highly complex extentions to Quanta.

[return to top]
Why aren't my dialog items resized when I resize the dialog?
It is a common mistake that the developer forgets to layout the widgets in a dialog correctly. Forgeting to do so has the consequence that the dialog elements do not fill up the dialog when the dialog is enlarged or they do not fit into when the dialog is shrinked. This also makes the dialog look bad for users who have different default font type or size on their system, resulting for example in button where the full text is not visible.
The solution is to layout the widgets inside the dialog correctly. The easiest is to use the group layout, by selecting the widgets and using Layout->Lay Out in a Grid. If all the widgets can be alyouted in the same way (all in a grid, for example), it is easiest to click on an empty area - instead of selecting all the widgets - and use the layouting command. Depending on the situation, horizontal and vertical layout can be also used.
In case of grouping widgets (ButtonGroup, GroupBox, TabWidget), first the widgets that are inside them should be layouted and later the grouping widget itself must be layouted to the dialog. If the grouping widget contains another grouping widget, the layouting must be done for the inlayed grouping widget as well.

[return to top]