View | Details | Raw Unified | Return to bug 203553 | Differences between
and this patch

Collapse All | Expand All

(-)guide/projectTemplateEngine/Howtoregistertemplates.html (-12 / +24 lines)
Lines 65-71 Link Here
65 
<li>
 65 
<li>
66 
<p>
 66 
<p>
67 
Click <code>Add</code> to select
 67 
Click <code>Add</code> to select
68 
<code class="filename">org.eclipse.cdt.templateengine</code> plug-in from the list.
 68 
<code class="filename">org.eclipse.cdt.core</code> and
69 
<code class="filename">org.eclipse.cdt.ui</code>
70 
plug-ins from the list.
69 
</p>
 71 
</p>
70 
<li>
 72 
<li>
71 
<p>
 73 
<p>
Lines 79-107 Link Here
79 
<li>
 81 
<li>
80 
<p>
 82 
<p>
81 
Select the extension-point with ID
 83 
Select the extension-point with ID
82 
<code class="filename">org.eclipse.cdt.templateengine.templates</code> from the list of
 84 
<code class="filename">org.eclipse.cdt.core.templates</code> from the list of
83 
extensions-points.
 85 
extension-points.
84 
</p>
 86 
</p>
85 
<li>
 87 
<li>
86 
<p>
 88 
<p>
87 
Right-click on the newly added extension, and select
 89 
Right-click on the newly added extension, and select
88 
<code class="ProgramOutput">New</code> &gt;
90 
<code class="ProgramOutput">New</code> &gt;
89 
<code class="ProgramOutput">template</code> from the context menu.
 91 
<code class="ProgramOutput">template</code> from the context menu.
92 
The first one has already been added for you, <code class="ProgramOutput">"(template)"</code>.
90 
</p>
 93 
</p>
91 
<li>
 94 
<li>
92 
<p>
 95 
<p>
93 
Choose the new template added in step 6 from the <code class="ProgramOutput">All
 96 
Select the new template added in the previous step from the <code class="ProgramOutput">All
94 
Extensions</code> list.
 97 
Extensions</code> list.  Its name is initially <code class="ProgramOutput">"(template)"</code>.
95 
</p>
 98 
</p>
96 
<li>
 99 
<li>
97 
<p>
 100 
<p>
98 
Specify the <code class="ProgramOutput">wizardId</code> attribute of the template as
 101 
Specify the <code class="ProgramOutput">id</code> attribute of the template as
102 
(for example?)
99 
"<em>org.eclipse.cdt.project.ui.NewProjectWizard</em>". This
 103 
"<em>org.eclipse.cdt.project.ui.NewProjectWizard</em>". This
100 
attribute is mandatory.
 104 
attribute is mandatory.
105 
It will replace <code class="ProgramOutput">"(template)"</code> in the list.
101 
</p>
 106 
</p>
102 
<li>
 107 
<li>
103 
<p>
 108 
<p>
104 
Specify the location of the template relative to the plug-in created
 109 
Specify the location of the template XML file, relative to the plug-in created
105 
in step 1. This attribute is mandatory.
 110 
in step 1. This attribute is mandatory.
106 
</p>
 111 
</p>
107 
<li>
 112 
<li>
Lines 127-134 Link Here
127 
</p>
 132 
</p>
128 
<li>
 133 
<li>
129 
<p>
 134 
<p>
130 
Select an appropriate project type from the
 135 
Select an appropriate project type for the
131 
<code class="ProgramOutput">projectType</code> drop-down list. This is an optional attribute.
136 
<code class="ProgramOutput">projectType</code> entry.
137 
This is a required entry.
138 
For example, for an executable, you can use
139 
<code class="ProgramOutput">projectType="org.eclipse.cdt.build.core.buildArtefactType.exe"</code>.
140 
For more information about project types, see
141 
<a href="../cdt_build_system/whats_new/4.0/whats_new_CBS_40.html#_TocSectionUIModel_2">
142 
New project information in the What's New in CDT Build section</a>,
143 
especially the section "What are the general project type entries?".
132 
</p>
 144 
</p>
133 
<li>
 145 
<li>
134 
<p>
 146 
<p>
Lines 139-146 Link Here
139 
<a href="http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html">java.util.regex.Pattern</a>.
 151 
<a href="http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html">java.util.regex.Pattern</a>.
140 
</p>
 152 
</p>
141 
<p>
 153 
<p>
142 
The New Project wizard will list only those templates, which are
 154 
The New Project wizard will list only those templates which are
143 
relevant for the build Configurations choosen for the project. For a example, if the developer
 155 
relevant for the build Configurations chosen for the project. For a example, if the developer
144 
choose to create a <code class="ProgramOutput">C++ Application for Symbian OS</code>, the wizard
 156 
choose to create a <code class="ProgramOutput">C++ Application for Symbian OS</code>, the wizard
145 
will list all the templates with the relevant
 157 
will list all the templates with the relevant
146 
<code class="ProgramOutput">usageDescription</code>. Otherwise, for a standard <code class="ProgramOutput">CDT
 158 
<code class="ProgramOutput">usageDescription</code>. Otherwise, for a standard <code class="ProgramOutput">CDT
Lines 151-157 Link Here
151 
<p>
 163 
<p>
152 
Specify the <code class="ProgramOutput">pagesAfterTemplateSelectionProvider</code>,
 164 
Specify the <code class="ProgramOutput">pagesAfterTemplateSelectionProvider</code>,
153 
which is a fully qualified name of the class that implements
 165 
which is a fully qualified name of the class that implements
154 
<code class="filename">org.eclipse.cdt.templateengine.IPagesAfterTemplateSelectionProvider</code>
 166 
<code class="filename">org.eclipse.cdt.ui.templateengine.IPagesAfterTemplateSelectionProvider</code>
155 
interface. This is an optional attribute.
167 
interface. This is an optional attribute.
156 
</p>
 168 
</p>
157 
</li>
 169 
</li>

Return to bug 203553