Chapter 4. Clients with Qt
Prev Wolframe Clients Next

Chapter 4. Clients with Qt

Table of Contents

4.1. Architecture
4.2. Artifacts
4.2.1. UI forms
4.2.2. UI form translations
4.2.3. Resources
4.3. Programming the interface
4.3.1. Mapping XML data
Starting position
First example
Another example
4.3.2. Switching UI forms
4.3.3. States and behaviour
Reserved private dynamic properties
Reserved public dynamic properties
Stearing of widget behaviour
User interface flow
Additional interface elements
Defining server request/answer
Variables and symbolic links
Widget states depending on data
Additional signals and slots
Drag and drop
4.3.4. Widget properties as dynamic property values
4.4. Programming server requests/answers
4.4.1. Adressing widget data
Biggest common ancestor path
Addressing atomic elements
Special path elements
Addressing the form widget
Widget links
4.4.2. Data structures
Example
4.4.3. Arrays
Description
Example
4.4.4. Indirection and recursion
Description
Example (arbitrary tree)
Example (binary tree)
4.5. Eliminating interface defects
4.5.1. Switch the developer mode on
4.5.2. Inspect errors and warnings and debug messages reported

This chapter describes the standard Wolframe client called wolfclient based on Qt and how a user interface is built with it.

4.1. Architecture

The Wolframe standard client wolfclient is a thin client which executes XML requests via the Wolframe protocol and presents XML answers. It is written in Qt and is cross-platform. Qt is currently available on http://doc.qt.digia.com/qt/index.html. User interfaces for wolfclient are defined as a set of forms using standard Qt widgets and are if ever possible defined using the Qt Interface Designer (see http://qt-project.org/doc/qt-4.8/designer-manual.html).

Prev Up Next
Chapter 3. Clients with .NET (C#) Home 4.2. Artifacts