Skip to Content

Changes for page Custom Project Templates

Last modified by Bastian Triller on 2009/04/11 21:03
From version 35.1
edited by Mike Schrag
on 2007/10/03 16:16
Change comment: There is no comment for this version
To version 36.1
edited by Mike Schrag
on 2007/10/03 16:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -28,8 +28,6 @@
28 28  
29 29  An example template.xml is below:
30 30  
31 -{{code value="xml"}}
32 -
33 33   <?xml version="1.0" encoding="UTF-8"?>
34 34   <template name = "Wonder Application">
35 35   <inputs>
... ... @@ -53,8 +53,6 @@
53 53   </inputs>
54 54   </template>
55 55  
56 -{{/code}}
57 -
58 58  The "name" attribute of the template node overrides the name of the folder the templates are in. For instance, you could have the above template.xml inside a folder named "Template 1" and the template system would consider the name of the template to be "Wonder Application."
59 59  
60 60  Within a template, you can declare a single "inputs" node that can contain multiple "input" nodes. Each input node corresponds to a variable that will be presented to the user on the second page of the wizard. Each input specifies a "name" attribute, which will become the variable name of the input for later reference in the Velocity templates; and a "type" attribute which can be one of Boolean, String, or Integer. The type value determines the control that will be used to display the input to the user (String = text field, Boolean = checkbox, Integer = spinner, etc). Each input also contains a "question" node, whose value corresponds to the label of the control when displayed to the user. In the above example, the "linkToWonderFrameworks" will display a checkbox to the user with the label "Link to Wonder Frameworks?". Additionally, you can provide a "default" node that defines the default value of the variable. If a default is not specified, the default value will be null for all input types.
... ... @@ -67,8 +67,6 @@
67 67  
68 68  As an example, the Wonder Application template's .classpath file is defined as:
69 69  
70 -{{code value="xml"}}
71 -
72 72   <?xml version="1.0" encoding="UTF-8"?>
73 73   <classpath>
74 74   <classpathentry kind="src" path="Sources"/>
... ... @@ -79,14 +79,12 @@
79 79   <classpathentry combineaccessrules="false" kind="src" path="/JavaWOExtensions"/>
80 80   #end
81 81   #if ($linkToWonderFrameworks)
82 - <classpathentry kind="con" path="org.objectstyle.wolips.WO_CLASSPATH/ERExtensions/ERJars/ERPrototypes/JavaWOExtensions/JavaEOAccess/JavaEOControl/JavaFoundation/JavaJDBCAdaptor/JavaWebObjects/JavaXML"/>
76 + <classpathentry kind="con" path="org.objectstyle.wolips.WO//CLASSPATH/ERExtensions/ERJars/ERPrototypes/JavaWOExtensions/JavaEOAccess/JavaEOControl/JavaFoundation/JavaJDBCAdaptor/JavaWebObjects/JavaXML"/>
83 83   #else
84 - <classpathentry kind="con" path="org.objectstyle.wolips.WO_CLASSPATH/JavaEOAccess/JavaEOControl/JavaFoundation/JavaJDBCAdaptor/JavaWebObjects/JavaXML"/>
78 + <classpathentry kind="con" path="org.objectstyle.wolips.WO//CLASSPATH/JavaEOAccess/JavaEOControl/JavaFoundation/JavaJDBCAdaptor/JavaWebObjects/JavaXML"/>
85 85   #end
86 - <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
80 + <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE//CONTAINER"/>
87 87   <classpathentry kind="output" path="bin"/>
88 - </classpath>
82 + </classpath>//
89 89  
90 -{{/code}}
91 -
92 92  Happy templating!