|→||1.3 Software development|
Create new project using DK libs and wxWidgets
|Options to show help text, version, and license|
|Example / Tutorial|
|Run the wizard|
|[Linux/Unix] Build process|
|[Windows] Build process|
|How to continue|
|Program information (copyright owner and license, program name...)|
|Remove idle processing if no idle event processing required.|
|Add further members to the TestApp class|
|Set exit status code|
|Add further members to the top-level window class|
|Check for unsaved data before closing a window|
|Futher methods in the top-level window|
|GUI elements and localized texts|
|Further events in the top-level window class|
|Better "About" dialog box|
|Create additional files|
|How do I create resource files (*.ico, *.xpm, *.chm, *.htb)?|
dkwxwiz [options] program application frame
All three names are used in C identifiers, so they must be valid C identifiers theirselves (character or underscore, optionally followed by a sequence of character, underscore or digits).
The dkwxwiz program produces a code skeleton for an application
using the wxWidgets libraries and the DK tools libraries.
You can use this wizard to start a new project.
0 on success, all other values indicate errors.
The following files are used by dkwxwiz:
The reverse search order for configuration files (see Administration → File search) is used, application name ``dkwxwiz'', application group name ``dktools''.
This program uses DK libraries version 3.
Prepare a new empty directory and run:
dkwxwiz testprog TestApp TestFrame
dkct -l autoconf ./configure make
to build the initial version.
The dkct command generates TestApp.h and TestApp.cpp from
TestApp.cpt and TestFrame.h and TestFrame.cpp from
Additionally it creates the testprog.str file containing a string table in English. The file is re-generated on each run of dkct.
The autoconf command generates a configure script from configure.ac.
The configure script uses ``wx-config'' to find the libraries to use and the library paths. Additionally it sets up some C/C++ compiler options.
The final make command builds the testprog application. You can run it using:
Edit the makefile.vc file and apply modifications if necessary.
Edit the testprog.rc file and apply modifications if necessary.
In a cmd.exe window set up the paths for Visual Studio and/or platform SDK and run:
dkct -l nmake -f makefile.vc
Places of interest are marked by __CHANGE__ number comments.
It is a good idea to edit all the files just created directly after running dkwxwiz. Use your editors search feature to visit all places marked by __CHANGE__.
I recommend to place all texts visible to the end user in the textprog_texts array. Each time you run the ``dkct'' command a file ``testprog.str'' is generated. You can use this file as a starting point for translations. In the string table you should write the index and purpose in comments. If you place testprog in /usr/bin, you must place localized versions of testprog.str in /usr/share/application/language or /usr/share/applicationgroup/language (applicationgroup is the group name set up in __CHANGE__ 006; application would be testprog in this example).
You should create the following files:
To configure all settings via command line would require many options. So you should edit all the files generated by dkwxwiz and apply changes to places marked by __CHANGE__ if necessary before doing the first build.
See Resource files.