Chapter two, Creating a Main Window Application, introduces TQt Designer and takes you step by step through the creation of a small but fully functional application. Along the way you will learn how to create a main window with menus, toolbars and a status bar. Most of the application's implementation will be covered, but the custom dialogs are deferred until chapter three. In the course of this chapter you will use the form and property editors to customize the application. You'll also learn how to use TQt's signals and slots mechanism and TQt Designer's built-in code editor to make the application functional. We will also explain how to use qmake to generate a Makefile so that you can compile and run the application.
In chapter three, Creating Dialogs, we will create the custom dialogs required by the main window application created in chapter two. In addition to demonstrating various ways of creating dialogs, you will also learn how to lay out forms using the layout tools.
Chapter four, The Designer Approach, provides information on the TQt Designer approach to developing applications, and explains some of the rationale behind TQt Designer.
-Chapter five, Subclassing and Dynamic Dialogs, will show you how to subclass a form; this allows you to clearly separate the user interface from the underlying code that implements its functionality. Additional information on qmake and uic is included in this chapter. This chapter will also explain how you can dynamically load dialogs from .ui files into your application using TQWidgetFactory and how to access the widgets and sub-widgets of these dialogs.
+Chapter five, Subclassing and Dynamic Dialogs, will show you how to subclass a form; this allows you to clearly separate the user interface from the underlying code that implements its functionality. Additional information on qmake and tquic is included in this chapter. This chapter will also explain how you can dynamically load dialogs from .ui files into your application using TQWidgetFactory and how to access the widgets and sub-widgets of these dialogs.
Chapter six, Creating Custom Widgets, explains how you can create your own custom widgets. Both the simple method, that was introduced with the first version of TQt Designer, and the new more powerful method using plugins, are explained.
Chapter seven, Creating Database Applications introduces TQt's SQL classes and takes you through an example that demonstrates how to execute SQL queries and how to set up master-detail relationships, perform drilldown and handle foreign keys.
Chapter eight, Customizing and Integrating TQt Designer, focuses on TQt Designer itself, showing you how to customize Designer, how to integrate Designer with Visual Studio and how to create Makefiles.
diff --git a/doc/html/designer-manual-13.html b/doc/html/designer-manual-13.html index 19f2fb74..26509a68 100644 --- a/doc/html/designer-manual-13.html +++ b/doc/html/designer-manual-13.html @@ -59,7 +59,7 @@ body { background: #ffffff; color: black; }The 'Insert Into' drop-down combobox lists the open projects, defaulting to the current project. New files are added to the project displayed in this combobox. To add a new file to a different project, choose the project you want to use in the 'Insert Into' combobox.
The 'Dialog' file type is highlighted by default when the New File dialog pops up. Click on the file type you want to use and click OK to create it. Click Cancel to leave the dialog without creating a new file. Note that if you select C++ Project, the 'Insert Into' combobox will be disabled, since it is not possible to insert a new C++ Project into an existing project.
C++ Project Files
-Click C++ Project to start a new project. This option invokes the Project Settings Dialog. C++ projects are saved as .pro files, which include the information TQt Designer needs to manage projects. When you add a form to your project in TQt Designer, it is automatically added to the FORMS section of the project file. The .pro file contains the list of forms (.ui files) used in the project. TQt Designer reads and writes .ui files, e.g. form.ui. The uic (user interface compiler) creates both a header file, e.g. form.h, and an implementation file, e.g. form.cpp, from the .ui file.
+Click C++ Project to start a new project. This option invokes the Project Settings Dialog. C++ projects are saved as .pro files, which include the information TQt Designer needs to manage projects. When you add a form to your project in TQt Designer, it is automatically added to the FORMS section of the project file. The .pro file contains the list of forms (.ui files) used in the project. TQt Designer reads and writes .ui files, e.g. form.ui. The tquic (user interface compiler) creates both a header file, e.g. form.h, and an implementation file, e.g. form.cpp, from the .ui file.
Dialog Forms
Click Dialog to create a plain dialog form. Typically, this type of form is used to present the user with configuration options, or to present related sets of choices, for example, printer setting dialogs and find and replace dialogs.
Wizard Forms
@@ -144,7 +144,7 @@ body { background: #ffffff; color: black; }Settings
In the Settings section, you can change or add the name of the class that will be created by typing in the 'Class Name' line edit. Note that the default name is the form name, but it can be changed. You can also enter text to the 'Comment' and 'Author' line edits or leave them blank, since they are not required.
Pixmaps
-The default (for projects) is 'Project Imagefile'. This is the recommended option. Images are handled automatically, with TQt Designer storing the images in a subdirectory, and uic producing code that contains the images and the necessary supporting code. Each image is stored just once, no matter how many forms it is used in.
+The default (for projects) is 'Project Imagefile'. This is the recommended option. Images are handled automatically, with TQt Designer storing the images in a subdirectory, and tquic producing code that contains the images and the necessary supporting code. Each image is stored just once, no matter how many forms it is used in.
If you do not want TQt Designer to handle the images, (or are not using a project) choose either 'Save Inline' or 'Use Function'. 'Save Inline' saves the pixmaps in the .ui files. The disadvantage of this approach is that it stores images in the forms in which they're used, meaning that images cannot be shared across forms. Click 'Use Function' to use your own icon-loader function for loading pixmaps. Type the function's name (with no signature) in the 'Use Function' line edit. This function will be used in the generated code for loading pixmaps. Your function will be called with the text you put in the pixmap property (e.g. the image name) whenever an image is required.
Layouts
Click the 'Default Margin' spinbox or the 'Default Spacing' spinbox to change the default layout settings of the current form.
diff --git a/doc/html/designer-manual-16.html b/doc/html/designer-manual-16.html index 4d6b536a..a480fc70 100644 --- a/doc/html/designer-manual-16.html +++ b/doc/html/designer-manual-16.html @@ -185,7 +185,7 @@ body { background: #ffffff; color: black; }If you have a class that requires some Windows-specific export macro, e.g. for classes in a DLL that need to be declared like this: class win_specific_declaration_goes_here Class, you can use the <exportmacro> tag. (In standard TQt we use the TQ_EXPORT macro, e.g. class TQ_EXPORT TQWidget.) If you use this tag you must also:
include the file which contains the macro definition;
add the export macro to the form -- this is achieved by entering the macro's name in the 'export macro' sub-property of the form's name property.
-
Following these steps will ensure that uic will create the correct class YOUR_MACRO Form declarations.
+Following these steps will ensure that tquic will create the correct class YOUR_MACRO Form declarations.
<exportmacro>EDITOR_EXPORT</exportmacro>diff --git a/doc/html/designer-manual-5.html b/doc/html/designer-manual-5.html index cc669704..e617f70c 100644 --- a/doc/html/designer-manual-5.html +++ b/doc/html/designer-manual-5.html @@ -32,7 +32,7 @@ body { background: #ffffff; color: black; }
[Prev: Creating Dialogs] [Home] [Next: Subclassing and Dynamic Dialogs]
The Designer Approach
Introduction
-In TQt 2.x, TQt Designer was a visual form designer for editing files in the .ui file format. TQt Designer's primary goal was to turn the most tedious part of GUI programming -- dialog design -- into a pleasant experience. From an architectural point of view, TQt Designer in 2.x is a fairly simple program. It reads and writes .ui files. Each .ui file contains an XML description of a single dialog form. A second utility -- the user interface compiler uic -- is used during the build process of an application to generate C++ code from those XML descriptions.
+In TQt 2.x, TQt Designer was a visual form designer for editing files in the .ui file format. TQt Designer's primary goal was to turn the most tedious part of GUI programming -- dialog design -- into a pleasant experience. From an architectural point of view, TQt Designer in 2.x is a fairly simple program. It reads and writes .ui files. Each .ui file contains an XML description of a single dialog form. A second utility -- the user interface compiler tquic -- is used during the build process of an application to generate C++ code from those XML descriptions.
For TQt 3.0 our ambitions for TQt Designer have grown beyond single dialog editing. In addition to many new design features like the ability to creating main windows and actions, the new version introduces:
project management for the user interface part of your application;
code in forms TQt Designer provides a code editor so that you can code your slots directly; the code is stored in .ui.h files and eliminates the need for sub-classing (although you can still subclass if you prefer);
@@ -58,35 +58,35 @@ body { background: #ffffff; color: black; }When you've opened or created a project you can set up its database connections using the Edit Database Connections dialog (invoked by the Project|Database Connections menu option). The connections you make are stored in a .db file. When you reload a project you can reconnect by going to the Edit Database Connections dialog, clicking a connection in the list and clicking the Connect button.
In most non-trivial database applications you will want to access the database from more than one form. This is why the .db file is part of a project, not just part of a single form.
.pro files
-TQt Designer needs to store information on projects, for example, the list of forms, the image collection and information about available databases and how to access them. The majority of TQt users already use a project file format to create multiplatform makefiles: tmake (and with TQt 3.0 qmake) project .pro files. These files already contain the list of forms, .ui files, used in the project for uic.
+TQt Designer needs to store information on projects, for example, the list of forms, the image collection and information about available databases and how to access them. The majority of TQt users already use a project file format to create multiplatform makefiles: tmake (and with TQt 3.0 qmake) project .pro files. These files already contain the list of forms, .ui files, used in the project for tquic.
We've extended the sections in the .pro file to include the extra information that TQt Designer needs to manage projects. For example, when you add a form to your project in TQt Designer, it is automatically added to the FORMS section of the project file, and thus qmake will generate the required build rules without any further work. Similarly, the images are added to the IMAGES section and thus gets automatically compiled into your executable.
We don't force you to use qmake; if you prefer another build system, for example automake/autoconf or jam, you can still continue to use it. Look upon the .pro file as a file that describes the GUI part of your application. All you need to do -- as previously -- is add the .ui files and the images collection to your own Makefiles.
Extending the functionality of a form
First let us look at a small figure that shows the relationship between .ui files, generated code and application code:
-
TQt Designer reads and writes .ui files, e.g. form.ui. The user interface compiler, uic, creates both a header file, e.g. form.h, and an implementation file, e.g. form.cpp, from the .ui file. The application code in main.cpp #includes form.h. Typically main.cpp is used to instantiate the TQApplication object and start off the event loop.
-While this approach is simple, it isn't sufficient for more complex dialogs. Complex dialogs tend to have quite a lot of logic attached to the form's widgets, more logic than can usually be expressed with predefined signals and slots. One way of handling this extra logic is to write a controller class in the application code that adds functionality to the form. This is possible because uic generated classes expose a form's controls and their signals to the public space. The big disadvantage of this method is that it's not exactly TQt-style. If you were not using TQt Designer, you would almost always add the logic to the form itself, where it belongs.
-This is why the capability of adding custom slots and member variables to a form was added to TQt Designer early on. The big additional benefit with this approach is that you can use TQt Designer to connect signals to those custom slots, in the same elegant graphical way that is used to connect signals to predefined slots. The uic then adds an empty stub for each custom slot to the generated form.cpp implementation file.
-The big question now is how to add custom implementation code to those custom slots. Adding code to the generated form.cpp is not an option, as this file gets recreated by the uic whenever the form changes -- and we don't want a combination of generated and handwritten code. There are two possible solutions, which we'll cover next.
+TQt Designer reads and writes .ui files, e.g. form.ui. The user interface compiler, tquic, creates both a header file, e.g. form.h, and an implementation file, e.g. form.cpp, from the .ui file. The application code in main.cpp #includes form.h. Typically main.cpp is used to instantiate the TQApplication object and start off the event loop.
+While this approach is simple, it isn't sufficient for more complex dialogs. Complex dialogs tend to have quite a lot of logic attached to the form's widgets, more logic than can usually be expressed with predefined signals and slots. One way of handling this extra logic is to write a controller class in the application code that adds functionality to the form. This is possible because tquic generated classes expose a form's controls and their signals to the public space. The big disadvantage of this method is that it's not exactly TQt-style. If you were not using TQt Designer, you would almost always add the logic to the form itself, where it belongs.
+This is why the capability of adding custom slots and member variables to a form was added to TQt Designer early on. The big additional benefit with this approach is that you can use TQt Designer to connect signals to those custom slots, in the same elegant graphical way that is used to connect signals to predefined slots. The tquic then adds an empty stub for each custom slot to the generated form.cpp implementation file.
+The big question now is how to add custom implementation code to those custom slots. Adding code to the generated form.cpp is not an option, as this file gets recreated by the tquic whenever the form changes -- and we don't want a combination of generated and handwritten code. There are two possible solutions, which we'll cover next.
The subclassing approach
A very clean way to implement custom slots for generated forms is via C++ inheritance as shown in the next figure:
-
Here the user wrote an additional class FormImpl, which is split into the header file formimpl.h and the implementation file formimpl.cpp. The header file includes the uic generated form.h and reimplements all the custom slots. This is possible because uic generated custom slots are virtual. In addition to implementing custom slots, this approach gives the user a way to do extra initialization work in the constructor of the subclass, and extra cleanups in the destructor.
+Here the user wrote an additional class FormImpl, which is split into the header file formimpl.h and the implementation file formimpl.cpp. The header file includes the tquic generated form.h and reimplements all the custom slots. This is possible because tquic generated custom slots are virtual. In addition to implementing custom slots, this approach gives the user a way to do extra initialization work in the constructor of the subclass, and extra cleanups in the destructor.
Because of these benefits and its flexibility, this approach became the primary way of using TQt Designer in TQt 2.x.
Note: To keep the namespace clean, most users did not follow the Form and FormImpl naming scheme shown in the figure, but instead named their TQt Designer forms FormBase and their subclasses Form. This made a lot of sense, because they always subclassed and were using those subclasses in application code.
The ui.h extension approach
Despite its flexibility and cleanness, the subclassing approach has some disadvantages:
Subclassing is not natural and easy for everybody. Newcomers to object-oriented techniques may feel uneasy about being forced to subclass for such a simple and natural thing like the implementation of a custom slot.
-Inheriting generated classes is an additional possible source of programming mistakes, especially if the number of reimplemented functions is high and the signatures change often during the design process. To make the development process smoother, uic generates empty stubs for custom slots rather than pure virtual functions. While this approach keeps the code compiling and running, programmers can find themselves in a situation where they miss a runtime warning message and lose time before they find a small spelling error in their subclass.
+Inheriting generated classes is an additional possible source of programming mistakes, especially if the number of reimplemented functions is high and the signatures change often during the design process. To make the development process smoother, tquic generates empty stubs for custom slots rather than pure virtual functions. While this approach keeps the code compiling and running, programmers can find themselves in a situation where they miss a runtime warning message and lose time before they find a small spelling error in their subclass.
In larger projects with hundreds of forms, the additional subclasses can make a noticeable difference in terms of compilation speed and code size.
There may be more disadvantages, but these were reason enough for us to investigate alternative solutions. For TQt 3.0, we came up with a new concept, the ui.h extension.
This is how it works:
In addition to the .ui file, form.ui, TQt Designer reads and writes another associated file form.ui.h. This .ui.h file is an ordinary C++ source file that contains implementations of custom slots. The file gets included from the generated form implementation file form.cpp and thus can be totally ignored by other user code. The reason we use a .h extension for the .ui.h file even though it contains C++ code is because it is always included, and because it is easier to integrate into the build process with a .h extension.
-The form.ui.h file has a special position among all other files. It is a shared source file that gets written and read by both the user and TQt Designer. As such it is an ordinary revision controlled source file and not generated by uic. TQt Designer's responsibility is to keep the file in sync with the custom slot definitions of the associated form:
+The form.ui.h file has a special position among all other files. It is a shared source file that gets written and read by both the user and TQt Designer. As such it is an ordinary revision controlled source file and not generated by tquic. TQt Designer's responsibility is to keep the file in sync with the custom slot definitions of the associated form:
Whenever the users adds a new slots to the form, TQt Designer adds a stub to the .ui.h file.
Whenever the user changes a custom slot's signature, TQt Designer updates the corresponding implementation.
Whenever the user removes a custom slot, TQt Designer removes it from the .ui.h file.
diff --git a/doc/html/designer-manual-6.html b/doc/html/designer-manual-6.html index efb9b353..1b2e796d 100644 --- a/doc/html/designer-manual-6.html +++ b/doc/html/designer-manual-6.html @@ -35,7 +35,7 @@ body { background: #ffffff; color: black; }Subclassing
We'll start with a general description of how to subclass a form and follow with a short example. Note that subclassing has some disadvantages compared with putting your code into a form directly; see Extending the functionality of a form in The Designer Approach chapter for details.
Generating Source Code from TQt Designer .ui Files
-TQt Designer reads and writes qmake .pro (project) files which are used to record the files used to build the application and from which Makefiles are generated. TQt Designer also reads and writes .ui (user interface) files. These are XML files that record the widgets, layouts, source code and settings you've used for a form. Every .ui file is converted by the uic (user interface compiler) into a C++ .h file and a C++ .cpp file. These C++ files are then read by tqmoc (meta object compiler), and finally compiled by your compiler into a working application.
+TQt Designer reads and writes qmake .pro (project) files which are used to record the files used to build the application and from which Makefiles are generated. TQt Designer also reads and writes .ui (user interface) files. These are XML files that record the widgets, layouts, source code and settings you've used for a form. Every .ui file is converted by the tquic (user interface compiler) into a C++ .h file and a C++ .cpp file. These C++ files are then read by tqmoc (meta object compiler), and finally compiled by your compiler into a working application.
If you create applications wholly within TQt Designer you only need to create a main.cpp.
If you create the main.cpp file within TQt Designer, it will automatically be added to your project file by TQt Designer. If you create the main.cpp file outside of TQt Designer you must add it to the project file manually by adding the following line at the end of your project's .pro file:
diff --git a/doc/html/designer-manual-7.html b/doc/html/designer-manual-7.html index f01f5ff1..70b9555a 100644 --- a/doc/html/designer-manual-7.html +++ b/doc/html/designer-manual-7.html @@ -107,7 +107,7 @@ DBFILE = vcr.db
Incorporating custom widgets that have their own slots and properties is achieved in a similar way to adding signals. All the required information is in our custom widget's header file.
Creating Custom Widgets with Plugins
This section will show you how to write a custom widget and how to embed the custom widget into a plugin. There are no restrictions or special considerations that must be taken into account when creating a widget that is destined to become a plugin. If you are an experienced TQt programmer you can safely skip the section on creating a custom widget and go directly to Creating a Plugin.
-Be aware that if you use the plugin approach to custom widgets, the plugin needs to be available not only to TQt Designer but also to uic at compile-time.
+Be aware that if you use the plugin approach to custom widgets, the plugin needs to be available not only to TQt Designer but also to tquic at compile-time.
Creating a Custom Widget
A custom widget is often a specialization (subclass) of another widget or a combination of widgets working together or a blend of both these approaches. If you simply want a collection of widgets in a particular configuration it is easiest to create them, select them as a group, and copy and paste them as required within TQt Designer. Custom widgets are generally created when you need to add new functionality to existing widgets or groups of widgets.
We have two recommendations that you should consider when creating a custom widget for a plugin:
diff --git a/doc/html/designer-manual-9.html b/doc/html/designer-manual-9.html index fb8c8781..9e3bab8f 100644 --- a/doc/html/designer-manual-9.html +++ b/doc/html/designer-manual-9.html @@ -111,20 +111,20 @@ body { background: #ffffff; color: black; }If you wish to delete the add-in remove it from the toolbar then delete the qmsdev.dll file from the add-ins directory.
Creating Makefiles without qmake
The qmake tool provided with TQt can create Makefiles appropriate to your platform based on .pro project files. This section describes the dependencies involved in building a TQt application and gives a couple of simple example Makefiles. This section assumes that you have a good understanding of Makefiles.
-TQt Designer produces .ui files which are used to generate .h and .cpp files for the compiler to compile. The .ui files are processed by uic. Classes which inherit from TQObject, e.g. those which use slots and signals, require an additional .cpp file to be generated. These files are generated by tqmoc and are named 'tqmoc_file.cpp' where the original .cpp file is called 'file.cpp'. If your .cpp file contains the TQ_OBJECT macro an additional file 'file.moc' should be generated which must be #included in the .cpp, normally at the end. This requires an extra dependency being created.
-Processing .ui files with uic is done twice:
+TQt Designer produces .ui files which are used to generate .h and .cpp files for the compiler to compile. The .ui files are processed by tquic. Classes which inherit from TQObject, e.g. those which use slots and signals, require an additional .cpp file to be generated. These files are generated by tqmoc and are named 'tqmoc_file.cpp' where the original .cpp file is called 'file.cpp'. If your .cpp file contains the TQ_OBJECT macro an additional file 'file.moc' should be generated which must be #included in the .cpp, normally at the end. This requires an extra dependency being created.
+Processing .ui files with tquic is done twice:
-uic myform.ui -o myform.h -uic myform.ui -i myform.h -o myform.cpp +tquic myform.ui -o myform.h +tquic myform.ui -i myform.h -o myform.cpp
-The first execution creates the header file, the second creates the .cpp file. If you wish to subclass a form you can use uic to generate subclass skeletons:
+The first execution creates the header file, the second creates the .cpp file. If you wish to subclass a form you can use tquic to generate subclass skeletons:
-uic formbase.ui -o formbase.h -uic formbase.ui -i formbase.h -o formbase.cpp -uic -subdecl Form formbase.h formbase.ui -o form.h -uic -subimpl Form form.h formbase.ui -o form.cpp +tquic formbase.ui -o formbase.h +tquic formbase.ui -i formbase.h -o formbase.cpp +tquic -subdecl Form formbase.h formbase.ui -o form.h +tquic -subimpl Form form.h formbase.ui -o form.cpp
-First we generate the header and implementation file for our base class. Then we generate the header and implementation skeletons for our subclass. Note that the use of uic to generate skeletons is not something that would be done in a Makefile, we mention it here because it can be useful for command line users. Note also that the command line for -subdecl and for -subimpl are subtly different.
+First we generate the header and implementation file for our base class. Then we generate the header and implementation skeletons for our subclass. Note that the use of tquic to generate skeletons is not something that would be done in a Makefile, we mention it here because it can be useful for command line users. Note also that the command line for -subdecl and for -subimpl are subtly different.
For implementation files that contain classes which inherit from TQObject we must create tqmoc files:
tqmoc myform.h -o tqmoc_myform.cpp @@ -147,12 +147,12 @@ myform.o: myform.cpp g++ -o myform.o myform.cpp myform.cpp: myform.h myform.ui - uic myform.ui -i myform.h -o myform.cpp + tquic myform.ui -i myform.h -o myform.cpp myform.h: myform.ui - uic myform.ui -o myform.h + tquic myform.ui -o myform.h-Note that you may need to include the full path to the commands in your Makefile, and under Windows the filenames are tqmoc.exe and uic.exe.
+Note that you may need to include the full path to the commands in your Makefile, and under Windows the filenames are tqmoc.exe and tquic.exe.
In Unix/Linux environments the make command may be able to do more for us, so we should be able to use a simpler Makefile like this:
myapp: tqmoc_myform.o myform.o main.o @@ -165,10 +165,10 @@ tqmoc_%.cpp: %.h tqmoc $^ -o $@ myform.cpp: myform.h myform.ui - uic myform.ui -i myform.h -o myform.cpp + tquic myform.ui -i myform.h -o myform.cpp myform.h: myform.ui - uic myform.ui -o myform.h + tquic myform.ui -o myform.hTo see more sophisticated Makefiles simply generate them using qmake on any of your TQt projects or any of the examples supplied with TQt.
Importing Foreign File Formats
diff --git a/doc/html/distributor-example.html b/doc/html/distributor-example.html index 78f39ab2..c5794404 100644 --- a/doc/html/distributor-example.html +++ b/doc/html/distributor-example.html @@ -54,7 +54,7 @@ distributed with TQt.
Implementation:
/**************************************************************************** -** ui.h extension file, included from the uic-generated form implementation. +** ui.h extension file, included from the tquic-generated form implementation. ** ** If you wish to add, delete or rename functions or slots use ** TQt Designer which will update this file, preserving your code. Create an diff --git a/doc/html/extension-dialog-example.html b/doc/html/extension-dialog-example.html index 50a59bc9..b51c9797 100644 --- a/doc/html/extension-dialog-example.html +++ b/doc/html/extension-dialog-example.html @@ -59,7 +59,7 @@ DBFILE = extension.db
Implementation:
/**************************************************************************** -** ui.h extension file, included from the uic-generated form implementation. +** ui.h extension file, included from the tquic-generated form implementation. ** ** If you wish to add, delete or rename functions use TQt Designer which will ** update this file, preserving your code. Create an init() function in place @@ -107,7 +107,7 @@ void MainForm::quit()
/**************************************************************************** -** ui.h extension file, included from the uic-generated form implementation. +** ui.h extension file, included from the tquic-generated form implementation. ** ** If you wish to add, delete or rename functions use TQt Designer which will ** update this file, preserving your code. Create an init() function in place @@ -133,7 +133,7 @@ void DialogForm::toggleDetails()
/**************************************************************************** -** ui.h extension file, included from the uic-generated form implementation. +** ui.h extension file, included from the tquic-generated form implementation. ** ** If you wish to add, delete or rename functions use TQt Designer which will ** update this file, preserving your code. Create an init() function in place diff --git a/doc/html/ftpclient-example.html b/doc/html/ftpclient-example.html index fed20eb5..1488b35a 100644 --- a/doc/html/ftpclient-example.html +++ b/doc/html/ftpclient-example.html @@ -49,7 +49,7 @@ commands. The GUI parts are done in the Designer. /**************************************************************************** ** -** ui.h extension file, included from the uic-generated form implementation. +** ui.h extension file, included from the tquic-generated form implementation. ** ** The init() function is used in place of a constructor. ** The destroy() function is used in place of a destructor. diff --git a/doc/html/index b/doc/html/index index 7b350474..4f94b156 100644 --- a/doc/html/index +++ b/doc/html/index @@ -7806,7 +7806,7 @@ "Trademarks" trademarks.html "Transformed Graphics Demo" xform-example.html "Tutorial #2" tutorial2.html -"User Interface Compiler (uic)" uic.html +"User Interface Compiler (tquic)" tquic.html "Using menus" menu-example.html "Using the Meta Object Compiler" tqmoc.html "Walkthrough: A Simple Application" simple-application.html diff --git a/doc/html/keyfeatures30.html b/doc/html/keyfeatures30.html index df56420a..74006dae 100644 --- a/doc/html/keyfeatures30.html +++ b/doc/html/keyfeatures30.html @@ -281,7 +281,7 @@ to read and edit *.pro files, add and remove files to/from the project and do some global operations on the project. You can now open the project file and have one-click access to all the *.ui forms in the project. -
In addition to generating code via uic, TQt Designer now supports the +
In addition to generating code via tquic, TQt Designer now supports the dynamic creation of widgets directly from XML user interface description files (*.ui files) at runtime. This eliminates the need of recompiling your application when the GUI changes, and could be used diff --git a/doc/html/process-example.html b/doc/html/process-example.html index ccf76102..f9d36bb7 100644 --- a/doc/html/process-example.html +++ b/doc/html/process-example.html @@ -34,7 +34,7 @@ body { background: #ffffff; color: black; }
This example shows you how to start other processes with TQt and how -IO redirection is done. The example tries to start the uic (a tool +IO redirection is done. The example tries to start the tquic (a tool that comes with the TQt Designer) on a certain ui file and displays the output of the command.
@@ -91,8 +91,8 @@ private: // Set up the command and arguments. // On the command line you would do: - // uic -tr i18n "small_dialog.ui" - proc->addArgument( "uic" ); + // tquic -tr i18n "small_dialog.ui" + proc->addArgument( "tquic" ); proc->addArgument( "-tr" ); proc->addArgument( "i18n" ); proc->addArgument( "small_dialog.ui" ); @@ -106,7 +106,7 @@ private: // error handling TQMessageBox::critical( 0, tr("Fatal error"), - tr("Could not start the uic command."), + tr("Could not start the tquic command."), tr("Quit") ); exit( -1 ); } diff --git a/doc/html/qmake-manual-8.html b/doc/html/qmake-manual-8.html index 6b26c1ea..ce478a8e 100644 --- a/doc/html/qmake-manual-8.html +++ b/doc/html/qmake-manual-8.html @@ -156,7 +156,7 @@ HEADERS = myclass.h \ INCLUDEPATH = c:\msdev\include d:\stl\includeFORMS
-This variable specifies the .ui files (see TQt Designer) to be processed through uic before compiling. All dependencies, headers and source files required to build these .ui files will automatically be added to the project.
+This variable specifies the .ui files (see TQt Designer) to be processed through tquic before compiling. All dependencies, headers and source files required to build these .ui files will automatically be added to the project.
For example:
FORMS = mydialog.ui \ @@ -192,21 +192,21 @@ unix:OBJECTS_DIR = ../myproject/tmp win32:OBJECTS__DIR = c:\myproject\tmp
UI_DIR
-This variable specifies the directory where all intermediate files from uic should be placed. This variable overrides both UI_SOURCES_DIR and UI_HEADERS_DIR.
+This variable specifies the directory where all intermediate files from tquic should be placed. This variable overrides both UI_SOURCES_DIR and UI_HEADERS_DIR.
For example:
unix:UI_DIR = ../myproject/ui win32:UI_DIR = c:\myproject\ui
UI_HEADERS_DIR
-This variable specifies the directory where all declaration files (as generated by uic) should be placed.
+This variable specifies the directory where all declaration files (as generated by tquic) should be placed.
For example:
unix:UI_HEADERS_DIR = ../myproject/ui/include win32:UI_HEADERS_DIR = c:\myproject\ui\include
UI_SOURCES_DIR
-This variable specifies the directory where all implementation files (as generated by uic) should be placed.
+This variable specifies the directory where all implementation files (as generated by tquic) should be placed.
For example:
unix:UI_SOURCES_DIR = ../myproject/ui/src @@ -500,10 +500,10 @@ app {QMAKE_TARGET
This variable contains the name of the project target. The value of this variable is typically handled by qmake or qmake.conf and rarely needs to be modified.
QMAKE_UIC
-This variable contains the location of uic if it is not in the path. The value of this variable is typically handled by qmake or qmake.conf and rarely needs to be modified.
-It can be used to specify arguments to uic as well, such as additional plugin paths. For example:
+This variable contains the location of tquic if it is not in the path. The value of this variable is typically handled by qmake or qmake.conf and rarely needs to be modified.
+It can be used to specify arguments to tquic as well, such as additional plugin paths. For example:
- QMAKE_UIC = uic -L /path/to/plugin + QMAKE_UIC = tquic -L /path/to/plugin
RC_FILE
This variable contains the name of the resource file for the application. The value of this variable is typically handled by qmake or qmake.conf and rarely needs to be modified.
@@ -518,7 +518,7 @@ app {TARGET_x.y.z
This variable specifies the target's extension with version number. The value of this variable is typically handled by qmake or qmake.conf and rarely needs to be modified.
UICIMPLS
-This variable contains a list of the generated implementation files by UIC. The value of this variable is typically handled by qmake or qmake.conf and rarely needs to be modified.
+This variable contains a list of the generated implementation files by TQUIC. The value of this variable is typically handled by qmake or qmake.conf and rarely needs to be modified.
UICOBJECTS
This variable is generated from the UICIMPLS variable. The extension of each file will have been replaced by .o (Unix) or .obj (Win32). The value of this variable is typically handled by qmake or qmake.conf and rarely needs to be modified.
VER_MAJ
diff --git a/doc/html/qt.dcf b/doc/html/qt.dcf index f4e2cae3..0f08678e 100644 --- a/doc/html/qt.dcf +++ b/doc/html/qt.dcf @@ -9796,8 +9796,8 @@Tutorial #2 - User Interface Compiler (uic) ++ User Interface Compiler (tquic) Using menus diff --git a/doc/html/titleindex b/doc/html/titleindex index 11243041..5e2f9628 100644 --- a/doc/html/titleindex +++ b/doc/html/titleindex @@ -1001,7 +1001,7 @@ Toplevel Widgets | toplevel-example.html Trademarks | trademarks.html Transformed Graphics Demo | xform-example.html Tutorial #2 | tutorial2.html -User Interface Compiler (uic) | uic.html +User Interface Compiler (tquic) | tquic.html Using menus | menu-example.html Using the Meta Object Compiler | tqmoc.html Walkthrough: A Simple Application | simple-application.html diff --git a/doc/html/tools-list.html b/doc/html/tools-list.html index 52f0711f..18dbc748 100644 --- a/doc/html/tools-list.html +++ b/doc/html/tools-list.html @@ -47,7 +47,7 @@ help you need simple platform-independent project files- qembed - convert data, e.g. images, into C++ code
- tqmoc - the Meta Object Compiler -
- uic - the User Interface Compiler +
- tquic - the User Interface Compiler
- qtconfig - a Unix-based TQt configuration tool with online help
diff --git a/doc/html/tqprocess.html b/doc/html/tqprocess.html index 4a33ff03..517b1466 100644 --- a/doc/html/tqprocess.html +++ b/doc/html/tqprocess.html @@ -131,14 +131,14 @@ program's process identifier is available from use tryTerminate(), but note that the program may ignore this. If you really want to terminate the program, without it having any chance to clean up, you can use kill(). -
As an example, suppose we want to start the uic command (a TQt +
As an example, suppose we want to start the tquic command (a TQt command line tool used with TQt Designer) and perform some -operations on the output (the uic outputs the code it generates +operations on the output (the tquic outputs the code it generates to standard output by default). Suppose further that we want to run the program on the file "small_dialog.ui" with the command line options "-tr i18n". On the command line we would write:
- uic -tr i18n small_dialog.ui
+ tquic -tr i18n small_dialog.ui
@@ -148,7 +148,7 @@ this:
UicManager::UicManager()
{
proc = new TQProcess( this ); -
proc->addArgument( "uic" ); +
proc->addArgument( "tquic" ); proc->addArgument( "-tr" ); proc->addArgument( "i18n" ); proc->addArgument( "small_dialog.ui" ); diff --git a/doc/html/uic.html b/doc/html/tquic.html similarity index 81% rename from doc/html/uic.html rename to doc/html/tquic.html index 58f20744..500e7d0c 100644 --- a/doc/html/uic.html +++ b/doc/html/tquic.html @@ -1,9 +1,9 @@ - + -User Interface Compiler (uic) +User Interface Compiler (tquic)