Difference between revisions of "Kexi/Debugging"

Jump to: navigation, search
(General)
(Kexi Debug GUI)
Line 9: Line 9:
 
Isn't debug to standard output enough? The Debug GUI is richer and easier to follow.  
 
Isn't debug to standard output enough? The Debug GUI is richer and easier to follow.  
  
Currently supported features:
+
Currently supported features, each in own separate tool window:
*Logging SQL commands that are sent by Kexi to the database backends. This helps to track history of commands, helps to understand what happens regarding communication between the application and backends. The order is chronological.
+
*Logging SQL commands that are sent by Kexi to the database backends. This helps to track history of commands, helps to understand what happens regarding communication between the application and backends. The order is chronological. The window is always visible, and can be just minimized.
*Displaying definition of active Kexi form in XML format. Definition of original form (last saved version) and current form (after modification) is presented, so changes can be compared.
+
*Displaying definition of an active Kexi form in XML format. Definition of original form (last saved version) and current form (after modification) is presented, so changes can be compared. To display the window, in ''Form Design'' toolbar, click ''Show Form UI code'' or press ''Ctrl+U'' shortcut.
  
 
===Enabling Kexi Debug GUI===
 
===Enabling Kexi Debug GUI===

Revision as of 20:18, 25 April 2014

General

Common information collected by the KDE Community:

Kexi Debug GUI

Kexi Debug GUI is a graphical tool for tracking internals of running Kexi application.

Isn't debug to standard output enough? The Debug GUI is richer and easier to follow.

Currently supported features, each in own separate tool window:

  • Logging SQL commands that are sent by Kexi to the database backends. This helps to track history of commands, helps to understand what happens regarding communication between the application and backends. The order is chronological. The window is always visible, and can be just minimized.
  • Displaying definition of an active Kexi form in XML format. Definition of original form (last saved version) and current form (after modification) is presented, so changes can be compared. To display the window, in Form Design toolbar, click Show Form UI code or press Ctrl+U shortcut.

Enabling Kexi Debug GUI

The tool can be freely enabled or disabled. When enabled, each Kexi application displays additional window used for outputting debug information.

First, the tool has to be compiled. By default its compilation is disabled. To enable compilation, go to the builddir, then use the ccmake visual tool:

% ccmake .

Find the CALLIGRA_DEBUG_GUI variable. To do so press "/" key to search, type CALLIGRA_DEBUG_GUI, press Enter. When you find it, if it's set to OFF, press enter to switch it to ON.

Similarly, find the KEXI_DEBUG_GUI variable and set it to ON.

You need to reconfigure the project to apply changes. To do so, type "g" key and wait until the configuration step finishes and ccmake exists.

Then compile Kexi using:

% make -j{NUMBER} install".

Then, open the local Kexi configuration file to enable the Debug GUI:

% kate `kde4-config --localprefix`/share/config/kexirc

Content is available under Creative Commons License SA 4.0 unless otherwise noted.