Designed with Quanta
Welcome to KDE Web Dev FAQ's.
Welcome to the FAQ section. This thing is probably going to grow hugely in the near future, but for now here are the most frequently asked of frequently asked questions.

The most frequent fix to lots of problems is to Upgrade. Before submitting problems to the developer list please make sure that you have an up to data KDE and KDEWEBDEV package, as many problems people encounter with older versions have already been fixed. Making sure you are up to date can save a great deal of time and frustration all round.

Individual FAQs can be found for Quanta+ and Kommander on their respective sites.
What is the latest Quanta Plus?
The latest stable version is 3.5.0.

[return to top]
What is the deal with Quanta BE?
From time to time, if the KDE release schedule and the code base permits, we release snapshots of the current development version. We call this Bleeding Edge releases. You can imagine them as a preview version, so it's not so well tested as a stable release, and the functionality present in it might change, but we are taking care to release only a version which is usable.

[return to top]
Which one is newer, Quanta BE 3.3-X or Quanta 3.3.0?
As the BE can be called a preview of the next version, the version number indicates the stable version that will follow the BE release. In the above example Quanta 3.3.0 is the stable release and Quanta BE 3.3-X was the preview of the release. So the 3.3.0 is newer. Here is the history of the stable and BE releases since version 3.0, from oldest to newest:
3.0
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.2 BE-1
3.2.0
3.2.1
3.2.2
3.2.3
3.3 BE-2
3.3.0
3.3.1
3.3.2
3.4.0
3.4.1
3.4.2
3.4.3
3.5.0


[return to top]
Can I have two version of Quanta at the same time?
Yes, you can. If you want to run a BE version, but still keep your old (stable) version, follow the below instructions. Remember, this is possible only if you compile the second version of Quanta from source. Quanta BE can be installed also into the same directory as the stable Quanta, as it uses a different executable name (quanta_be) and different data directories, but the other kdewebdev applications are not, and they will upgrade your current version. Installing two version is a matter of using a different prefix for the new version and setting some environment variables. Before running the new one installed outside of the KDE tree, you should do:

export KDEDIRS=$prefix-of-second-instace:$KDEDIRS
export PATH=$prefix-of-second-instace/bin:$PATH
export LD_LIBRARY_PATH=$prefix-of-second-instace/lib:$LD_LIBRARY_PATH
export KDEHOME=home-for-second-version
and run "quanta".

An example would be:
./configure --prefix=/opt/new-quanta
make
make install
mkdir ~/.new-quanta
export KDEDIRS=/opt/new-quanta:$KDEDIRS
export PATH=/opt/new-quanta/bin:$PATH
export LD_LIBRARY_PATH=/opt/new-quanta/lib:$LD_LIBRARY_PATH
export KDEHOME=~/.new-quanta
quanta

You can put the lines starting with the first "export" into a separate file, call it "new-quanta", make it executable, put it in your PATH and when you run "new-quanta" the version installed into /opt/new-quanta will be run.

[return to top]
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]
How can I restore the layout of the toolview and editor widgets in Quanta?
Due to some bugs in the underlying libraries, it may happen that you undock the toolviews and the editor, but you cannot dock back. There are several solutions and I will give you the general one, and how you can do it in Quanta 3.3/3.4:
a) The general solution is to quit Quanta, locate the local quantarc file in you home folder and remove the complete [dock_settings_default] part. After you did it, restart Quanta.
b) In 3.3 in the Settings->Configure Quanta->User Interface check the Reset layout to the default on the next startup checkbox and restart Quanta.
c) In 3.4, in addition to the above, you can use the --resetlayout command line switch when starting Quanta

[return to top]
How can I reuse the same Quanta instance when opening a new file associated with Quanta in Konqueror (or from other application)?
If you start Quanta with the --unique command line switch, it will reuse the existing instance to load the files given as the parameter. To make use of this switch when opening Quanta from Konqueror (as an application associated with some file types), open the KDE Control Center->KDE Components->File Associations, find the file type you want to change (for example text/html), select Quanta Plus and press Edit. In the Properties dialog box switch to the Application tab and change the Command entry so it reads: "quanta --unique %U".

[return to top]
Quanta does not recognize my file and treats it like HTML. What can I do?
If you file is a script, or CSS with a non-standard extension, Quanta will not recognize it, and instead it will treat as the default DTD you have selected in the global or project settings. But you can teach Quanta to recognize your files. If for example you have CSS files with the extension of .tpl, you should do the following:
1) create a new "x-tpl" mimetype under the "text" group in the KDE Control Center->KDE Components->File Associations, which is valid for *.tpl files.
2) find the global $KDEDIR/share/apps/quanta/dtep/css/description.rc file and add the text/x-tpl to the MimeTypes list:
MimeTypes = text/css,text/x-tpl
3) restart Quanta. From now on *.tpl files will be treated as CSS inside Quanta.
4) to use the CSS syntax highlighting for .tpl files, use Settings->Configure Editor->Highlighting and for the Markup/CSS highlight add the text/x-tpl mimetype: text/css;text/x-tpl (or use the wizard button to pick up the tpl mimetype).

[return to top]
Quanta does not recognize my files and says they are binary file, altough they are not?
This is again a problem in your mimetype configuration, meaning that the mimetype of the file you try to open is not in the text group. This was valid (and maybe still is) for many distributions, as they put the PHP mimetype under "application/x-php". In order for Quanta to recognize PHP files, the mime type needs to exist in the "text" category. All you need to do is open the KDE Control Center->KDE Components, and under the File Associations menu, add a new mime type for text/x-php. Add the extensions *.php, *.php3 and *.php4 and Quanta will be able to open PHP files without a problem.

[return to top]
Where can I configure the preview?
In Settings->Configure Preview you have access to the KHTML browser engine's configuration module. It's important to realize that changes made in this dialog affects all application using KHTML, including, but not limited to the Konqueror web browser.

[return to top]
Where can I configure the remote access (like FTP) settings?
Quanta uses the global KDE settings and they are configurable in KDE Control Center->Internet & Network. Important pages are the Connection Preferences and the Proxy configuration dialog.

[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 to see hidden files in files tree view?
I remember some people asking about this so I'll just make a little note here.
If you don't want to see hidden files in your file tree then go to.
Settings->Configure Quanta->User Interface and uncheck the 'Show hidden files in files tree'. Yep it's that simple.

[return to top]
Is it possible to do multi-file Find and Replace?
Oddly this seems to get asked quite a bit. KFileReplace is your friend here.
You access it quite simply within Quanta with Ctrl-Alt-f. You can also find it on the plugins toolbar or in the 'Edit" menu (Replace in files).

KFileReplace is implemented as a plugin by Quanta, but it is available as a stand-alone application as well.

[return to top]
What is the difference between Quanta Plus and Quanta Gold?
Quanta Gold is a commercial product developed at the Kompany by the original authors of the Quanta Plus. They abandoned the GPL'd version of Quanta Plus before the 2.0 release appeared. Since then the GPL'd Quanta Plus is developed by a new team, only the project leader is the same. The real answer for the question is: they are completely different products, so the difference is huge.

[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]
Is it possible to turn off the detailed tooltips for files in the treeviews?
Yes, it is, altough there is no GUI option for it. In order to turn them off for the Project treeview do the following:
  • exit Quanta (very important, otherwise your changes will be lost)
  • open ~/.kde/share/config/quantarc
  • search for the line [ProjectTreeView]
  • add after this line a new line: ShowToolTips=false
  • save the file and restart Quanta
Of course you can do the same thing for the other treeviews, just use the corresponding entry from [ScriptTreeView], [TemplatesTreeView] and [FilesTreeView].

[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]