1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
|
/****************************************************************************
**
** Copyright (c) 2013 Digia Plc and/or its subsidiary(-ies).
** Contact: http://www.qt-project.org/legal
**
** This file is part of Qt Creator
**
**
** GNU Free Documentation License
**
** Alternatively, this file may be used under the terms of the GNU Free
** Documentation License version 1.3 as published by the Free Software
** Foundation and appearing in the file included in the packaging of this
** file.
**
**
****************************************************************************/
/*!
\page qtcreator-dev-wizards.html
\title Creating Wizards in Code
\section1 Introduction
If the functionality provided by template-based
\l{http://doc.qt.digia.com/qtcreator-snapshot/creator-project-wizards.html}{custom wizards}
is not sufficient for your case, you can write wizards in code.
A wizard in Qt Creator is an instance of a class implementing
the Core::IWizard interface that is registered with ExtensionSystem::PluginManager.
Implementing wizards requires:
\list
\o Deciding on a base class:
\list
\o Core::IWizard is a very generic interface that does
not make any assumption about what the wizard does and
what its UI looks like.
\o Core::BaseFileWizard should be used for wizards that
generate files using a UI based on Utils::Wizard.
\endlist
\o Providing a set of parameters that determine how the wizard shows up
in the list of wizards in the \gui{New File or Project} dialog.
When deriving from Core::IWizard, virtual functions returning the
values have to be implemented.
When deriving from Core::BaseFileWizard, a parameter class
Core::BaseFileWizardParameters needs to be passed to the constructor,
on which the parameters can be set. This allows for easy creation
of several wizard instances with slightly different parameters.
\o Implementing the wizard UI
Typically, this will be a class derived from Utils::Wizard.
Utils::Wizard extends QWizard with the functionality to show a progress
bar on the left.
\o Implementing the wizard functionality
When deriving from Core::BaseFileWizard, a list of Core::GeneratedFile
needs to be populated with the files and their contents.
\note The files are not actually written to the disk. This will be
done by Core::BaseFileWizard after performing overwrite checks and prompting
the user accordingly.
\endlist
\section2 Relevant Classes
\table
\header
\o Class
\o Description
\row
\o Core::IWizard
\o Qt Creator wizard interface, implementations of which are registered with
ExtensionSystem::PluginManager.
\row
\o Core::BaseFileWizard
\o Inherits Core::IWizard and provides a base class for generating files with a UI
based on QWizard.
\row
\o Core::BaseFileWizardParameters
\o Contains parameters for Core::BaseFileWizard.
\row
\o Core::GeneratedFile
\o A file as produced by Core::BaseFileWizard, containing name, contents and some
attributes.
\row
\o Utils::FileWizardPage
\o Introductory wizard page asking for file name and path.
\row
\o Utils::FileWizardDialog
\o A wizard dialog presenting a Utils::FileWizardPage, which can be extended
by custom pages.
\row
\o Utils::ProjectIntroPage
\o Introductory wizard page asking for project name and path.
\row
\o ProjectExplorer::BaseProjectWizardDialog
\o Base class for project wizard dialogs, presenting
a Utils::ProjectIntroPage.
\endtable
\section2 Parameters
The parameters listed below determine how the wizard shows up
in the list of wizards in the \gui{New File or Project} dialog.
Wizards in Qt Creator are grouped by categories.
\table
\header
\o Type
\o Parameter Name
\o Description
\row
\o Core::IWizard::WizardKind
\o kind
\o Enumeration value that indicates the type of the wizard (project, class, file).
\row
\o QIcon
\o icon
\o Icon to show.
\row
\o QString
\o description
\o Descriptive text.
\row
\o QString
\o displayName
\o Name to be shown in the list.
\row
\o QString
\o id
\o Unique identifier for the wizard. It also determines the order within a category.
\row
\o QString
\o category
\o Identifier of the category under which the wizard is to be listed. It also
determines the order of the categories.
\
\row
\o QString
\o displayCategory
\o Description of the category.
\endtable
\section1 Example
\section2 Introduction
In this example, we create a wizard
for writing HTML files consisting of a title and a paragraph,
making use of QXmlStreamWriter.
For the UI, we use Utils::FileWizardDialog and extend it by a page
letting the user enter title and contents.
In our BaseFileWizard implementation, we create the file contents
using QXmlStreamWriter.
\section2 The WebContentPageWizardPage Class
Let us start with the wizard page. We use a QLineEdit for the title
and a QPlainTextEdit for the content, arranged in a QGridLayout with
descriptive labels.
\note The QGridLayout was chosen to be able to accommodate the large
vertical span of the QPlainTextEdit. For standard controls, a
QFormLayout should be considered, which will lay out the labels
according to the platform guide lines.
On top of that, we implement validation logic to ensure content is entered.
We implement QWizardPage::isComplete() to return true when both input widgets
have contents, enabling the \gui{Next} button. For this to happen
as the user enters text, we need to connect to the changed() signal of the
controls and emit QWizardPage::completeChanged() once the complete status changes.
\snippet webpagewizard/webpagewizard.h 1
\snippet webpagewizard/webpagewizard.cpp 1
\section2 The WebContentWizardDialog Class
The wizard dialog extends Utils::FileWizardDialog, which presents an
introductory page asking for file name and path.
We add our WebContentPageWizardPage after that.
\snippet webpagewizard/webpagewizard.h 2
\snippet webpagewizard/webpagewizard.cpp 2
\section2 The WebContentWizard Class
In our implementation of Core::BaseFileWizard, we overwrite
createWizardDialog() to return an instance of our WebContentWizardDialog,
initially set to the path passed in. We also add the extension pages
we receive. Extension pages are for example the wizard pages asking for
a project to add the files to and whether to add the files to a version control
system.
In generateFiles(), we obtain the parameters from our wizard and populate
the list of Core::GeneratedFile with our file. To generate the contents,
we use QXmlStreamWriter.
\snippet webpagewizard/webpagewizard.h 3
\snippet webpagewizard/webpagewizard.cpp 3
\section2 Plugin Registration
In order for the wizard to be found by the \gui{New} dialog, we need to
register it with ExtensionSystem::PluginManager, which also takes care
of deleting it:
\snippet webpagewizard/webpagewizardplugin.cpp 0
\section2 Complete Example Code
Here is the complete code of \c webpagewizard.h:
\snippet webpagewizard/webpagewizard.h 0
The complete code of \c webpagewizard.cpp looks as follows:
\snippet webpagewizard/webpagewizard.cpp 0
The registration of the wizard in the \c initialize() method
of a plugin looks like:
\snippet webpagewizard/webpagewizardplugin.cpp 0
*/
|
