sourceCode_description = <HTML><BODY> \
On this page you can control a number of default behaviors and appearances that apply to the formatting of source code during forward and reverse engineering operations. In Source Code options you can: \
<ul> \
<li> \
Specify the relative position of Attribute declarations and Operation declarations within Class declarations (i.e., Attributes first or Operations first) \
<li> \
Control how link-attributes are handled when destination is deleted \
<li> \
Specify exactly how source code is formatted (indents, line breaks, spacing, etc.); also specify when code is reformatted \
<li> \
Specify the type of line separator for your OS \
<li> \
Control indentation characteristics \
<li> \
Specify exactly how source code and comments are formatted (in-line breaks, space preservation, separators, etc.) Includes JavaDoc comment formatting options for comments \
<li> \
Control optimization parameters for Name referencing and Import statements \
<li> \
Fully customize code construction and reverse engineering blueprints. \
Tip: This is where you can control the "Generated by" text at the head of source code files. \
</ul> \
</BODY></HTML>

order = Order
order_description = <HTML><BODY> \
	Order of members. \
	</BODY></HTML>

javaGroup = Java
javaGroup_description = <HTML><BODY> \
    Java source code options.<BR> \
    Expand this node to see source code formatting, optimization, and other options for Java.<BR> \
    Note that the Java "Blueprints" options from previous versions are now available as Source Code Templates. \
    Templates are used as defaults for code construction for such things as classes, interfaces, members, and links. \
    Source Code Templates are accessible from the Directory page of the Explorer pane. From there you can use speedmenus \
    to open them in the Editor for easy modification. \
	</BODY></HTML>


deleteLinksAttributes =Delete link-attributes when deleting destination
deleteLinksAttributes_description = <HTML><BODY> \
If you delete the class at the other end of an association, this option controls whether to delete any associations to that class: \
<ul> \
  <li> \
  <b>All</b> - all attributes representing association links to the deleted class will be deleted. \
  <li> \
  <b>No</b> - no attributes representing association links to the deleted class will be deleted. \
  <li> \
  <b>Automatic</b> - only attributes representing association links to the deleted class, with the names starting with "lnk",  \
  will be deleted. All other attributes representing association links to the deleted class will not be deleted.
  </ul> \
</BODY></HTML>

reformatCode = Reformat code
reformatCode_description = <HTML><BODY> \
Defines how Together will reformat the source code after a change has occurred (in Inspector, diagram etc.): \
<ul> \
<li> \
<b>Incremental</b>: new format settings impact only newly created code elements. \
<li> \
<b>Automatic</b>: new format settings impact all code elements in the file - on adding a new code element all code elements will be reformatted correspodingly. \
</ul> \
</BODY></HTML>

cpp_generated_header_file_ext = Extension of generated C++ header file
cpp_generated_header_file_ext_description = <HTML><BODY> \
Extension of generated C++ header file. \
</BODY></HTML>

cpp_generated_source_file_ext = Extension of generated C++ definition file
cpp_generated_source_file_ext_description = <HTML><BODY> \
Extension of generated C++ definition file. \
</BODY></HTML>


blueprints_FilePrologue = File prologue
blueprints_FilePrologue_description = File prologue

blueprints_FileEpilogue = File epilogue
blueprints_FileEpilogue_description = File epilogue

blueprints_DefaultClass = Default class
blueprints_DefaultClass_description= Default class

blueprints_DefaultClassName = Default class name
blueprints_DefaultClassName_description= Default class name

blueprints_DefaultInterface= Default interface
blueprints_DefaultInterface_description= Default interface

blueprints_cpp_DefaultInterface= Default interface
blueprints_cpp_DefaultInterface_description= <HTML><BODY> \
Default interface. Note that in C++ there are no interfaces, so we fake them by assigning a special property \
to the generated class. In is not recommended to edit this blueprint since it might cause some problems when \
working with C++ projects. \
</BODY></HTML>


blueprints_DefaultInterfaceName = Default interface name
blueprints_DefaultInterfaceName_description= Default interface name

blueprints_DefaultAttribute = Default attribute
blueprints_DefaultAttribute_description= Default attribute
                                                                                                                                                                           
blueprints_DefaultAttributeName = Default attribute name
blueprints_DefaultAttributeName_description= Default attribute name

blueprints_DefaultAttributeType = Default attribute type
blueprints_DefaultAttributeType_description= Default attribute type

blueprints_cpp_DefaultAttributeInInterface = Default attribute in interface
blueprints_cpp_DefaultAttributeInInterface_description= Default attribute in interface

blueprints_DefaultAttributeInInterfaceName = Default name of attribute in interface
blueprints_DefaultAttributeInInterfaceName_description= Default name of attribute in interface

blueprints_DefaultAttributeInInterfaceType = Default type of attribute in interface
blueprints_DefaultAttributeInInterfaceType_description= Default type of attribute in interface

blueprints_DefaultOperation = Default operation
blueprints_DefaultOperation_description= Default operation

blueprints_DefaultOperationName = Default operation name
blueprints_DefaultOperationName_description= Default operation name

blueprints_DefaultOperationType = Default operation return type
blueprints_DefaultOperationType_description= Default operation return type

blueprints_cpp_DefaultOperationInInterface = Default operation in interface
blueprints_cpp_DefaultOperationInInterface_description= Default operation in interface

blueprints_DefaultOperationInInterfaceName = Default name of operation in interface
blueprints_DefaultOperationInInterfaceName_description= Default name of operation in interface

blueprints_DefaultOperationInInterfaceType = Default return type of operation in interface
blueprints_DefaultOperationInInterfaceType_description= Default return type of operation in interface

blueprints_DefaultConstructor = Default constructor
blueprints_DefaultConstructor_description= Default constructor

blueprints_DefaultAssociation = Default association
blueprints_DefaultAssociation_description= Default association

blueprints_DefaultAggregation = Default aggregation
blueprints_DefaultAggregation_description= Default aggregation

blueprints_DefaultComposition = Default composition
blueprints_DefaultComposition_description= Default composition

positionMembers = Position Members
positionMembers_description = <HTML><BODY> \
  Defines the order of appearance of attributes and operations in a newly created class/interface. Note that \
this option controls the position of <b>only the first attribute/operation</b> (when it is added via popup \
menu or by shortcut) and <b>only in a newly created class/interface</b> (for example, if you have a class with some \
operations and attributes, changing this option will produce no effect, the order of members will remain as is): \
  <ul> \
  <li> \
  <b>Operations, then Attributes</b> - operations first, attributes after them. \
  <li> \
  <b>Attributes, then Operations</b> - attributes first, operations after them. \
  </ul> \
For example, suppose you have created a new class and this option is "Operations, then Attributes". When you \
create a new attribute and a new operation, the operation will be placed first. This will define the order of \
members in this class: all not manually created/added operations will be placed before attributes. \
  </BODY></HTML>


javaFormatMode = Format mode
javaFormatMode_description =   <HTML><BODY> \
  Defines what Together will format in the source code files: \
  <ul> \
  <li> \
  <b>None</b> - Do not format or optimize anything. \
  <li> \
  <b>Format only</b> - Together will format only code and comments according to the settings \
  in the <b>Format code</b> and <b>Format Comments</b> groups (they are subgroups of the <b>Formatting options</b> group). \
  Import statements and name references \
  will not be optimized. \
  <li> \
  <b>Optimize only</b> - Together will optimize import statements and \
  name references according to the settings \
  in the <b>Optimize import statements</b> and <b>Optimize name references</b> groups (they are subgroups of the <b>Optimization options</b> group). \
  Code and comments will not be formattted. \
  <li> \
  <b>Format & Optimize</b> - Together will format code and comments, and/or import statements and \
  name references. \
  <li> \
  <b>Comments only</b> - Together will format only comments according to the settings \
  in the <b>Format Comments</b> group. Import statements and name references \
  will not be optimized. \
  </ul> \
  </BODY></HTML>


javaSourceFormat_format = Formatting options
javaSourceFormat_format_description = <HTML><BODY> \
    Formatting options. \
    </BODY></HTML>

javaSourceFormat_optimize = Optimization options
javaSourceFormat_optimize_description = <HTML><BODY> \
     Optimization options. \
    </BODY></HTML>

javaSourceFormat_code = Format Code
javaSourceFormat_code_description = <HTML><BODY> \
    Format code. \
    </BODY></HTML>

javaSourceFormat_lineSeparator = Line separator
javaSourceFormat_lineSeparator_description =   <HTML><BODY> \
  Defines the <b>line separator</b> (depends on the OS) - which is the symbol \
  added to the end of each line to \
  indicate that the line is ended. \
  </BODY></HTML>

javaSourceFormat_rightMargin = Right margin
javaSourceFormat_rightMargin_description =   <HTML><BODY> \
  Allows you to specify the column number at which you want expressions to start wrapping to the next line. \
<p> \
  Sometimes it is impossible to wrap an expression <i>exactly</i> at this column \
  because of other formatting settings (they might have a higher priority). \
  </BODY></HTML>


javaSourceFormat_rightMarginToIndents = Do not indent after this column
javaSourceFormat_rightMarginToIndents_description =   <HTML><BODY> \
  It is useful when you have a lot of inner loops etc, and the indentation will just make it more difficult \
  to read.\
  </BODY></HTML>


 javaSourceFormat_preserveEmptyLines= Preserve empty lines
 javaSourceFormat_preserveEmptyLines_description =   <HTML><BODY> \
  Controls whether to preserve <b>empty lines</b> in the source code. \
  <ul> \
  <li> \
  If checked : all existing empty lines will be preserved untouched.  \
  <li> \
  If unchecked : Together may add or remove empty lines. \
  </ul> \
  </BODY></HTML>

javaSourceFormat_maxNumberEmptyLinesInGroup = Max number of empty lines per group
javaSourceFormat_maxNumberEmptyLinesInGroup_description =   <HTML><BODY> \
  Controls the maximum number of empty lines located one after another. For example, if the value of \
option is 3, and there are 5 empty lines located one after another, then only 3 of them will be left. \
  </BODY></HTML>


 javaSourceFormat_preserveLineBreaks = Preserve line breaks
 javaSourceFormat_preserveLineBreaks_description =  <HTML><BODY> \
  Controls whether to preserve <b>line breaks</b> in the source code. For example, if a line \
  break position is changed, then the rest of the line \
  after this line break will be displayed on the next line. \
  <ul> \
  <li> \
  If checked : lines will not be concatenated in the source code . \
  <li> \
  If unchecked : Together may concatenate lines. \
  </ul> \
  </BODY></HTML>

 javaSourceFormat_preserveSpaces = Preserve spaces
 javaSourceFormat_preserveSpaces_description =   <HTML><BODY> \
  Controls whether to preserve <b>spaces</b>. \
  <ul> \
  <li> \
  If checked : all existing spaces will be preserved untouched.  \
  <li> \
  If unchecked : Together may add or delete spaces. \
  </ul> \
  </BODY></HTML>

javaSourceFormat_indentation = Indentation
javaSourceFormat_indentation_description = <HTML><BODY> \
    Indentation options. \
    </BODY></HTML>

javaSourceFormat_indentStyle = Indent style
javaSourceFormat_indentStyle_description =  <HTML><BODY> \
  Controls the indent style for the java source code: \
  <ul> \
  <li> \
  <b>Compact</b>:<pre><code> \
      if (expr) { \n \
      \ \ body; \n \
      } </pre></code> \
  <li> \
  <b>Align braces</b>:<pre><code> \
      if (expr) \n \
      { \n \
      \ \ body; \n \
      } </pre></code> \
  <li> \
  <b>Indent braces</b>:<pre><code> \
      if (expr) \n \
      \ \ { \n \
      \ \ body; \n \
      \ \ } </pre></code> \
  <li> \
  <b>Indent braces and body</b>:<pre><code> \
      if (expr) \n \
      \ \ { \n \
      \ \ \ \ body; \n \
      \ \ } </pre></code> \
  </ul> \
  </BODY></HTML>

javaSourceFormat_indentSymbol = Indent symbol
javaSourceFormat_indentSymbol_description =  <HTML><BODY> \
Defines the character used to indent levels. \
  </BODY></HTML>

javaSourceFormat_indentWidth = Indentation width
javaSourceFormat_indentWidth_description =   <HTML><BODY> \
Defines the <b>indentation width</b> in spaces. \
  <ul> \
  <li> \
  For example, 8 means that each indentation level \
  will be shifted to the right by 8 spaces relative to the previous level. \
  <li> \
  <b>Editor</b> - Together will use the editor's tab size value. \
  </ul> \
  </BODY></HTML>

 javaSourceFormat_continuationPrefix = Continuation indent
 javaSourceFormat_continuationPrefix_description =   <HTML><BODY> \
  This &lt;string&gt will be added to the continuation lines of multiline operators:<pre><code> \
  \ \ \ \ c = a + b + c +\n \
  \ \ \ \ &lt;string&gt;d + e + f;</pre></code> \
  &lt;string&gt can be <code>"\\t"</code> (tab), <code>"  "</code> (two spaces) etc. \
  </BODY></HTML>

javaSourceFormat_expandSourceTabsToSpaces = Expand tabs to spaces
javaSourceFormat_expandSourceTabsToSpaces_description =   <HTML><BODY> \
  Controls whether to expand tabs to spaces - when pressing a tab, spaces are entered to fill the space: \
  <ul> \
  <li> \
  <b>None</b> - Together will not expand tabs to spaces. \
  <li> \
  <b>Indent</b> - Together will expand tabs by the number of spaces specified in the <b>indent width</b> option. \
  <li> \
  <b>Editor</b> - Together will expand tabs by the number of spaces specified in the editor's (the Text Editor tab) <b>tab size</b> option. \
  </ul> \
  Please note that if some of the "Preserve spaces ..." options is off, then Together may change the \
  number of inserted spaces. For example, "<code>if      (true) return;</code>" it may \
  format to "<code>if (true) return;</code>".
  </BODY></HTML>

javaSourceFormat_keepShortBlocksOnSameLine = Locate short blocks on one line
javaSourceFormat_keepShortBlocksOnSameLine_description = <HTML><BODY> \
  Using this option you can format a block so that it will occupy a single \
  line (if its length does not exceed the value of <b>right margin</b> option). \
  For example: \
  <ul> \
  <li> \
   int[] a = { 1, 2, 3 }; // code \
  <li> \
   if (b &lt; 1) { b = 1; }  // code \
  <li> \
   int f() { return 0; }  // declaration  \
  </ul> \
Options: \
  <ul> \
  <li> \
  <b>Never</b> - blocks formatting is defined by <b>Indent Style</b> option \
  <li> \
  <b>Always</b> - All short blocks whose length does not exceed <b>right margin</b> option value, will be \
      formatted to occupy one line (<b>Indent Style</b> option will be ignored). If the length of a block \
      is more than the <b>right margin</b>, it will be formatted according to the <b>Indent Style</b> \
      option. \
      This option applies only to inner blocks (i.e. to "{a=1;}" , but not \
      to the external blocks like in "do {if (a&lt;1) {a=1;}}..." \
  <li> \
  <b>In code</b> - In operations, short blocks whose length does not exceed <b>right margin</b> option value, \
      will be formatted to occupy one line. \
      For example, "if (i&gt;0) {j=0;}", "int[] a = {1,2,3};". (Second example with initialization \
      will be formatted this way only if <b>Keep array initialization</b> is "No"). \
       If the length of a block \
      is more than the <b>right margin</b>, it will be formatted according to the <b>Indent Style</b> \
      option. \
      <b>Indent Style</b> option will be ignored. This option applies only to inner blocks \
  <li> \
  <b>In declarations</b> - In declarations, short blocks whose length does not exceed <b>right margin</b> option value, \
      will be formatted to occupy one line. \
      For example, "int f() {return 0;}". <b>Indent Style</b> option will be ignored. \
If the length of a block \
      is more than the <b>right margin</b>, it will be formatted according to the <b>Indent Style</b> \
      option. \
      This option applies only to inner blocks. \
  <li> \
  <b>Keep</b> - This option works almost like <b>Always</b> - if a block \
   <i>originally</i> occupies exactly one line, then after formatting Together will try \
to keep on one line, but if it fails (for example, indentation required to insert a lot of spaces before the \
control expression) the block will be formatted according to the <b>Indent Style</b> option. \
      This option applies only to inner blocks. \
  </ul> \
  </BODY></HTML>

javaSourceFormat_keepArrayInitialization = Keep array initialization
javaSourceFormat_keepArrayInitialization_description = <HTML><BODY> \
  Using this option you can save the original formatting of array assignments such as: \
<p> \
   <code> int[][] a = { {1,1}, {2,2}, {3,3} }; </code><br> \
   <code> char[][] words = { </code> <br> \
   <code> /* 0 */ {'c','l','a','s','s'}, </code><br> \
   <code> /* 1 */ {'e','x','a','m','p','l','e'}} </code><br> \
  <ul> \
  <li> \
  <b>No</b> - Formatting using <b>Indent Style</b> option. Original formatting will not be saved. \
  <li> \
  <b>Keep but indent</b> - All source text in the array initialization will not \
      be formatted, but text lines will be indented. References can be optimized, if it is allowed. \
  <li> \
  <b>Yes</b> - All text in the array initialization braces \
   will be not formatted. References can be optimized, if it is allowed. \
  </ul> \
  </BODY></HTML>

javaSourceFormat_alignAssignments = Align initialization
javaSourceFormat_alignAssignments_description = <HTML><BODY> \
  Using this option you can align assignments in sequences of three or more lines containing initialization \
  of variables.\
  <ul> \
  <li> \
  <b>Yes</b> - Position of "=" in all the initializations (when there are three or more lines) \
  will be aligned, i.e. \
<pre><code> \
     int i     = 5; // aligned \n \
     int iiiii = 5; // aligned \n \
     int a     = 34; // aligned \n \
     k = t * r; // not aligned because it is not an initialization</pre></code> \
  <li> \
  <b>Attributes only</b> - works like <b>Yes</b> but only for initializations of class attributes (i.e. \
  all the initializations in the code blocks will be skipped). This will not work for attributes in the inner classes. \
  <p> \
  Note that in C++ this mode will also align initializations of global variables. \
  <li> \
  <b>No</b> - This feature will be not used \
  </HTML></BODY>

javaSourceFormat_statements = Statements and Blocks
javaSourceFormat_statements_description = <HTML><BODY> \
    Statements and blocks options. \
    </HTML></BODY>

  
 javaSourceFormat_placeStatementsOnNewLine= Locate statement on new line
 javaSourceFormat_placeStatementsOnNewLine_description =   <HTML><BODY> \
  Defines how Together will treat statements: \
  <ul> \
  <li> \
  <b>Always</b> - Together will always put each statement on a new line. \
  <li> \
  <b>Never</b> - Together will try to put as many statements on the same line as possible. \
  <li> \
  <b>As is</b> - Together will leave statements where they are. If there are several statements \
on the same line, and after formatting this line takes more space than the right margin allows, \
the last statement will be placed on a new line (if needed, two last statements etc.). \
  </ul> \
  </BODY></HTML>

javaSourceFormat_placeSimpleBodyOnSameLine = Place simple body on the same line
javaSourceFormat_placeSimpleBodyOnSameLine_description =   <HTML><BODY> \
  Defines how Together will treat a simple body in control expressions. (A simple body is not \
  surrounded by curly braces. For example, <code>if (true) processAccount(); </code>) \
  <ul> \
  <li> \
  <b>Always</b> - Together always tries to put a simple body on the same line where the control expression is located. \
  <li> \
  <b>Never</b> - Together never tries to put a simple body on the same line where the control expression is located. \
  <li> \
  <b>As is</b> - Together leaves a simple body where it is. \
  </ul> \
  </BODY></HTML>

javaSourceFormat_forceBodyBraces = Surround simple body by curly braces
javaSourceFormat_forceBodyBraces_description =   <HTML><BODY> \
  Defines how Together will treat a simple body in control expressions. (A simple body is not \
  surrounded by curly braces. For example, <code>if (true) processAccount(); </code>) \
  <ul> \
  <li> \
  <b>Always</b> - Together will always surround a simple body by curly braces. \
  <li> \
  <b>Never</b> - Together will never surround a simple body by curly braces. \
  <li> \
  <b>If on the next line</b> - Together will surround a simple body by curly braces only if it is located on \
  a new line (see <b>Place simple body on the same line</b>). \
  </ul> \
  </BODY></HTML>

javaSourceFormat_placeLabels = Place labels (for labeled breakes)
javaSourceFormat_placeLabels_description =  <HTML><BODY> \
  Defines how Together will treat labels (used in labeled breakes): \
  <ul> \
  <li> \
  <b>Normal</b> - Together will place labels at the same level as normal operators: \
<pre><code> \
\ \ public void a() { \n \
\ \ \ \ a: \n \
\ \ \ \ for (int i = 0; i &lt; 3; i++) { \n \
\ \ \ \ \ \ break a; \n \
\ \ \ \ } \n \
\ \ } </code></pre>\
  <li> \
  <b>Deindent</b> - Together will deindent labels to the left to one level: \
<pre><code> \
\ \ public void a() { \n \
\ \ a: \n \
\ \ \ \ for (int i = 0; i &lt; 3; i++) { \n \
\ \ \ \ \ \ break a; \n \
\ \ \ \ } \n \
\ \ } </code></pre>\
  <li> \
  <b>At line start</b> - Together will place labels at the beginning of a line: \
<pre><code> \
\ \ public void a() { \n \
a: \n \
\ \ \ \ for (int i = 0; i &lt; 3; i++) { \n \
\ \ \ \ \ \  break a; \n \
\ \ \ \ } \n \
\ \ } </code></pre>\
  </ul> \
  </BODY></HTML>


javaSourceFormat_placeLabeledStatements = Place labeled statements on new line
javaSourceFormat_placeLabeledStatements_description =  <HTML><BODY> \
  Defines how Together will treat labeled statements: \
  <ul> \
  <li> \
  <b>Always</b> - Together will always place a labeled statement on a new line. \
  <li> \
  <b>Never</b> - Together will never place a labeled statement on a new line. \
  <li> \
  <b>As is</b> - Together will leave a labeled statement where it is. \
  </ul> \
  </BODY></HTML>

javaSourceFormat_brakeInSwitch = Location of break operator in switch
javaSourceFormat_brakeInSwitch_description =  <HTML><BODY> \
  Defines how Together will treat a <code>break</code> operator in a <code>switch</code> statement: \
  <ul> \
  <li> \
  <b>Normal</b> - Together will always place a <code>break</code> operator at the same level as other operators.\
  <li> \
  <b>Deindent</b> - Together will deindent a <code>break</code> operator to the <code>case</code> label level. \
  </ul> \
  </BODY></HTML>

javaSourceFormat_binaryOperatorBreak = Break binary operator
javaSourceFormat_binaryOperatorBreak_description = <HTML><BODY> \
If there is a large expression with a binary operator (for example, the length of  \
this expression is greater than the <b>right margin</b> value), \
Together will try to place this expression on several lines: \
  <ul> \
  <li> \
  <b>After</b> - Together will try to break an expression after a binary operator. \
  <li> \
  <b>Before</b> - Together will try to break an expression before a binary operator. \
  </ul> \
  </BODY></HTML>

javaSourceFormat_elseOnNewLine = Place 'else' on new line
javaSourceFormat_elseOnNewLine_description = <HTML><BODY> \
Defines where Together will place keywords <code>else, catch, finally, while</code> (in <code>do {} while</code> statement): \
  <ul> \
  <li> \
  <b>Always</b> - Together will always put these keywords on the next line. \
  <li> \
  <b>Never</b> - Together will never put these keywords on the next line. \
  <li> \
  <b>As is</b> - Together will leave these keywords where they are. \
  </ul> \
  </BODY></HTML>

javaSourceFormat_placeVisModifiers = Place visiblity modifiers
javaSourceFormat_placeVisModifiers_description =  <HTML><BODY> \
  Defines how Together will treat visiblity modifiers ("public:", "private:", "protected:"): \
  <ul> \
  <li> \
  <b>Normal</b> - Together will place visiblity modifiers at the same level as normal operators: \
<pre><code> \
\ \ public class a { \n \
\ \ \ \ public: \n \
\ \ \ \ int i; \n \
\ \ \ \ private: \n \
\ \ \ \ int j; \n \
\ \ } </code></pre>\
  <li> \
  <b>Deindent</b> - Together will deindent visiblity modifiers to the left to one level: \
<pre><code> \
\ \ public class a { \n \
\ \ public: \n \
\ \ \ \ int i; \n \
\ \ private: \n \
\ \ \ \ int j; \n \
\ \ } </code></pre>\
  <li> \
  <b>At line start</b> - Together will place visiblity modifiers at the beginning of a line: \
<pre><code> \
\ \ public class a { \n \
public: \n \
\ \ \ \ int i; \n \
private: \n \
\ \ \ \ int j; \n \
\ \ } </code></pre>\
  </ul> \
  </BODY></HTML>





javaSourceFormat_emptyLines = Empty lines around declarations
javaSourceFormat_emptyLines_description = <HTML><BODY> \
    Empty lines around declarations. \
    </BODY></HTML>
    
 javaSourceFormat_numOfEmptyLinesBeforeClass = Number of empty lines before class
 javaSourceFormat_numOfEmptyLinesBeforeClass_description =   <HTML><BODY> \
  Defines the number of <b>empty lines</b> inserted before a class \
  </BODY></HTML>

 javaSourceFormat_numOfEmptyLinesBeforeOperation = Number of empty lines before operation
 javaSourceFormat_numOfEmptyLinesBeforeOperation_description =   <HTML><BODY> \
  Defines the number of <b>empty lines</b> inserted before an operation \
  </BODY></HTML>

 javaSourceFormat_numOfEmptyLinesBeforeAttribute  = Number of empty lines before attribute
 javaSourceFormat_numOfEmptyLinesBeforeAttribute_description =   <HTML><BODY> \
  Defines the number of <b>empty lines</b> inserted before an attribute. \
  </BODY></HTML>

 javaSourceFormat_numOfEmptyLinesAfterClass = Number of empty lines after class
 javaSourceFormat_numOfEmptyLinesAfterClass_description =   <HTML><BODY> \
  Defines the number of <b>empty lines</b> inserted after a class \
  </BODY></HTML>

 javaSourceFormat_numOfEmptyLinesAfterOperation = Number of empty lines after operation
 javaSourceFormat_numOfEmptyLinesAfterOperation_description =   <HTML><BODY> \
  Defines the number of <b>empty lines</b> inserted after an operation \
  </BODY></HTML>

 javaSourceFormat_numOfEmptyLinesAfterAttribute  = Number of empty lines after attribute
 javaSourceFormat_numOfEmptyLinesAfterAttribute_description =   <HTML><BODY> \
  Defines the number of <b>empty lines</b> inserted after an attribute. \
  </BODY></HTML>



javaSourceFormat_spaces = Spaces in expressions
javaSourceFormat_spaces_description = Spaces in expressions

 javaSourceFormat_spaceBeforeControlExpression= Space before control expression
 javaSourceFormat_spaceBeforeControlExpression_description =   <HTML><BODY> \
  Controls whether to put a space before a <b>control expression</b>: \
  <ul> \
  <li> \
  <pre>If checked : <code>if (expr) {body;}</code></pre> \
  <li> \
  <pre>If unchecked : <code>if(expr) {body;}</code></pre> \
  </ul> \
  </BODY></HTML>

 javaSourceFormat_spacesAroundBinaryOperator = Spaces around binary operator
 javaSourceFormat_spacesAroundBinaryOperator_description =   <HTML><BODY> \
  Controls whether to put spaces around a <b>binary operator</b>: \
  <ul> \
  <li> \
  <pre>If checked : <code>c = a + b</code></pre> \
  <li> \
  <pre>If unchecked : <code>c=a+b</code></pre> \
  </ul> \
  </BODY></HTML>

 javaSourceFormat_spacesWithinParentheses = Spaces within parentheses
 javaSourceFormat_spacesWithinParentheses_description =   <HTML><BODY> \
  Controls whether to put spaces within <b>parentheses</b>: \
  <ul> \
  <li> \
  <pre>If checked : <code>( expression )</code></pre> \
  <li> \
  <pre>If unchecked : <code>(expression)</code></pre> \
  </ul> \
  Note that this option does not affect empty parentheses <code>()</code>. \
  </BODY></HTML>

 javaSourceFormat_spacesWithinSquareBrackets = Spaces within square brackets
 javaSourceFormat_spacesWithinSquareBrackets_description =   <HTML><BODY> \
  Controls whether to put spaces within <b>square brackets</b>: \
  <ul> \
  <li> \
  <pre>If checked : <code>[ expression ]</code></pre> \
  <li> \
  <pre>If unchecked : <code>[expression]</code></pre> \
  </ul> \
  Note that this option does not affect empty square brackets <code>[]</code>. \
  </BODY></HTML>



javaSourceFormat_comments = Format Comments
javaSourceFormat_comments_description = Format Comments

 javaSourceFormat_commentsKeepSpaces = Preserve spaces in comments
 javaSourceFormat_commentsKeepSpaces_description = <HTML><BODY> \
  Controls whether to preserve <b>spaces</b> in comments. \
  <ul> \
  <li> \
  If checked : all spaces in the comments will be preserved untouched.  \
  <li> \
  If unchecked : Together may insert or delete spaces in the comments. \
  </ul> \
  </BODY></HTML>

javaSourceFormat_cStyleCommentsAutoformat_NODE = Format C-style comments
javaSourceFormat_cStyleCommentsAutoformat_NODE_description = <HTML><BODY> \
    Controls whether to format <b>C-style</b> comments <code>/* ... */</code>. \
    </BODY></HTML>

 javaSourceFormat_cStyleCommentsAutoformat = Format C-style comments
 javaSourceFormat_cStyleCommentsAutoformat_description =   <HTML><BODY> \
  Controls whether to format <b>C-style</b> comments <code>/* ... */</code>. \
  <ul> \
  <li> \
  If checked they may be split into two lines (depending on the <b>Right margin</b> value) etc. \
  <li> \
  If unchecked they will be preserved untouched. \
  </ul> \
  </BODY></HTML>

 javaSourceFormat_cCommentsPreserveLineBreaks = Preserve line breaks
 javaSourceFormat_cCommentsPreserveLineBreaks_description = <HTML><BODY> \
  Controls whether to preserve <b>line breaks</b> in C-style comments. \
  For example, if a line break position is changed, then the rest of the line \
  after this line break will be displayed on the next line. \
  <ul> \
  <li> \
  If checked : lines will not be concatenated in C-style comments. \
  <li> \
  If unchecked : Together may concatenate lines in C-style comments. \
    </ul> \
  </BODY></HTML>

  javaSourceFormat_cCommentsPreserveEmptyLines = Preserve empty lines
  javaSourceFormat_cCommentsPreserveEmptyLines_description =   <HTML><BODY> \
  Controls whether to preserve <b>empty lines</b> in C-style comments. \
  <ul> \
  <li> \
  If checked : all empty lines in C-style comments will be preserved untouched. \
  <li> \
  If unchecked : Together may insert or delete empty lines in C-style comments. \
  </ul> \


 javaSourceFormat_cCommentsForceShortOneLine = Format short comments to occupy one line
 javaSourceFormat_cCommentsForceShortOneLine_description = <HTML><BODY> \
  <ul> \
  <li> \
  If checked : Together will try to format a comment so that it will occupy a single \
  line (if its length does not exceed the value of <b>right margin</b> option). \
  For example, this comment: \
  <pre> <code> \
    /*  \n \
    comment \n \
    */ </pre></code> \
  will be formatted to <pre><code>\
    /* comment */ </pre></code> \
  <li> \
  If unchecked : Together will not try to format comments in the manner described above. \
  </ul> \
  </BODY></HTML>


javaSourceFormat_cStyleCommentsNumLinesBefore = Number of empty lines before
javaSourceFormat_cStyleCommentsNumLinesBefore_description = <HTML><BODY> \
  Defines the number of <b>empty lines</b> inserted before a C-style comment. Special cases: \
  <ul> \
  <li> \
  If the number is 0 then the comment will be placed on the next line.\
  <li> \
  If the number is less than 0 then the comment will be merged with the end of the previous line. \
  </ul> \
  </BODY></HTML>

javaSourceFormat_cStyleCommentsNumLinesAfter = Number of empty lines after
javaSourceFormat_cStyleCommentsNumLinesAfter_description = <HTML><BODY> \
  Defines the number of <b>empty lines</b> inserted after a C-style comment. Special cases: \
  <ul> \
  <li> \
  If the number is 0 then no empty lines will be inserted.\
  <li> \
  If the number is less than 0 then the next line after the comment will be merged with the end of the comment. \
  </ul> \
  </BODY></HTML>

javaSourceFormat_inlineCommentsAutoformat_NODE = Format inline comment
javaSourceFormat_inlineCommentsAutoformat_NODE_description = <HTML><BODY> \
    Controls whether to format <b>inline comment</b> <code>// ...</code>. \
    </BODY></HTML>

 javaSourceFormat_inlineCommentsAutoformat = Format inline comment
 javaSourceFormat_inlineCommentsAutoformat_description =   <HTML><BODY> \
  Controls whether to format <b>inline comment</b> <code>// ...</code>. \
  <ul> \
  <li> \
  If checked they may be split into two lines (depending on the <b>Right margin</b> value) or \
  may be merged with the previous line etc. \
  <li> \
  If unchecked they will be preserved untouched. \
  </ul> \
  </BODY></HTML>

 javaSourceFormat_inlineCommentsSeparator = Inline comment separator
 javaSourceFormat_inlineCommentsSeparator_description =   <HTML><BODY> \
  Defines the inline comment <b>separator</b>: \
  <code>expression;&lt string &gt//...</code> \
  </BODY></HTML>

 javaSourceFormat_locateOnNewLine = Locate on new line
 javaSourceFormat_locateOnNewLine_description =   <HTML><BODY> \
 Defines how Together treats inline comments <code>//...</code> : \
  <ul> \
  <li> \
  <b>Always</b> - inline comments will always be located on a new line. \
  <li> \
  <b>As is</b> - Together will leave inline comments where they are. Note: inline comments in "import" \
statements are always formatted "As is". If "Optimize import statements" option is on, then all inline comments \
in "import" statements will be deleted. \
  </ul> \
  </BODY></HTML>

javaSourceFormat_docCommentsAutoformat_NODE = Format Javadoc comments
javaSourceFormat_docCommentsAutoformat_NODE_description = <HTML><BODY> \
    Controls whether to format <b>Javadoc comments</b> <code>/** ... */</code>. \
    </BODY></HTML>

 javaSourceFormat_docCommentsAutoformat = Format Javadoc comments
 javaSourceFormat_docCommentsAutoformat_description =   <HTML><BODY> \
  Controls whether to format <b>Javadoc comments</b> <code>/** ... */</code>. <br> \
  For COM IDL this option is applied to comments with info for compiler <code> [ ... ] </code> \
  <ul> \
  <li> \
  If checked they may be split into two lines (depending on the <b>Right margin</b> value) etc. \
  <li> \
  If unchecked they will be preserved untouched. \
  </ul> \
  </BODY></HTML>

 javaSourceFormat_docCommentsPreserveLineBreaks = Preserve line breaks
 javaSourceFormat_docCommentsPreserveLineBreaks_description = <HTML><BODY> \
  Controls whether to preserve <b>line breaks</b> in Javadoc comments. \
  For example, if a line break position is changed, then the rest of the line \
  after this line break will be displayed on the next line. \
  <ul> \
  <li> \
  If checked : lines will not be concatenated in Javadoc comments. \
  <li> \
  If unchecked : Together may concatenate lines in Javadoc comments. \
  </ul> \
  </BODY></HTML>

  javaSourceFormat_docCommentsPreserveEmptyLines = Preserve empty lines
  javaSourceFormat_docCommentsPreserveEmptyLines_description =   <HTML><BODY> \
  Controls whether to preserve <b>empty lines</b> in Javadoc comments. \
  <ul> \
  <li> \
  If checked : all empty lines in the Javadoc comments will be preserved untouched.  \
  <li> \
  If unchecked : Together may insert or delete empty lines in Javadoc comments. \
  </ul> \

  </BODY></HTML>

  javaSourceFormat_docCommentsCharToFillFirstLine = Char to fill in the first line
  javaSourceFormat_docCommentsCharToFillFirstLine_description =   <HTML><BODY> \
  Defines the character to fill in the <b>first line</b> in Javadoc comments. For example, "*" will \
  cause the first line to contain only "*" characters. \
  </BODY></HTML>

  javaSourceFormat_docCommentsCharToFillLastLine = Char to fill in the last line
  javaSourceFormat_docCommentsCharToFillLastLine_description =   <HTML><BODY> \
  Defines the character to fill in the <b>last line</b> in Javadoc comments. For example, "*" will \
  cause the last line to contain only "*" characters. \
  </BODY></HTML>

  javaSourceFormat_docCommentsForceShortOneLine = Format short comments to occupy one line
  javaSourceFormat_docCommentsForceShortOneLine_description = <HTML><BODY> \
  <ul> \
  <li> \
  If checked : Together will try to format a comment so that it will occupy a single \
  line (if its length does not exceed the value of <b>right margin</b> option). Note that this \
  option ignores the characters defined in the <b>Char to fill first/last line</b> option. \
  For example, this comment: \
  <pre><code>\
   /** ***************** \n \
    *comment \n \
    ******************** */ </pre></code> \
  will be formatted to <pre><code> \
   /** comment */ </pre></code>\
  <li> \
  If unchecked : Together will not try to format comments in the manner described above. \
  </ul> \
  </BODY></HTML>


javaSourceFormat_docCommentsNumLinesBefore = Number of empty lines before
javaSourceFormat_docCommentsNumLinesBefore_description =   <HTML><BODY> \
  Defines the number of <b>empty lines</b> inserted before a JavaDoc comment. Special cases: \
  <ul> \
  <li> \
  If the number is 0 then the comment will be placed on the next line.\
  <li> \
  If the number is less than 0 then the comment will be merged with the end of the previous line. \
  </ul> \
  </BODY></HTML>


javaSourceFormat_docCommentsNumLinesAfter = Number of empty lines after
javaSourceFormat_docCommentsNumLinesAfter_description =<HTML><BODY> \
  Defines the number of <b>empty lines</b> inserted after a JavaDoc comment. Special cases: \
  <ul> \
  <li> \
  If the number is 0 then no empty lines will be inserted.\
  <li> \
  If the number is less than 0 then the next line after the comment will be merged with the end of the comment. \
  </ul> \
  </BODY></HTML>

javaSourceFormat_optimizeReferencesEnabled = Optimize name references
javaSourceFormat_optimizeReferencesEnabled_description =   <HTML><BODY> \
  Controls whether Together may optimize <b>name references</b>. For example, whether it may convert fully qualified names  \
  into simple names. \
  </BODY></HTML>


javaSourceFormat_optimizeDontChangeNames = Do not change these names on optimization
javaSourceFormat_optimizeDontChangeNames_description =   <HTML><BODY> \
  <b>Do not</b> change these names on optimization.<p> \
  Names of classes must be separated with a space (for example, "java.beans.Beans java.awt.* org.omg.CORBA/r" \
  <ul> \
  <li> \
  * means Java-style names wildcard. \
  <li> \
  /r means a recursive option (for example, "java/r" means "java","java.awt","java.awt.color" etc.) \
  </ul> \
  </BODY></HTML>

javaSourceFormat_optimizeReferencesToSimpleReferences = Use simple reference names
javaSourceFormat_optimizeReferencesToSimpleReferences_description =   <HTML><BODY> \
  Try to use <b>simple</b> reference names instead of fully qualified names (if it is possible). For example, \
  <code>"String("ex").length()"</code> instead of <code>"java.lang.String("ex").length()"</code> \
  </BODY></HTML>

javaSourceFormat_optimizePackageNames = Optimize only these packages
javaSourceFormat_optimizePackageNames_description =   <HTML><BODY> \
  Together will analyze <b>only</b> these packages, others will be ignored. \
  Names of packages must be separated with a space (for example, "java.awt org.omg.CORBA/r" \
  <ul> \
  <li> \
  * means all packages. \
  <li> \
  /r means a recursive option (for example, "java/r" means "java","java.awt","java.awt.color" etc.) \
  <li> \
  Do <b>not</b> use Java-style names such as "java.*" \
  </ul> \
  </BODY></HTML>

javaSourceFormat_optimizeReferencesToFQ = Use fully qualified names for classes in these packages
javaSourceFormat_optimizeReferencesToFQ_description =   <HTML><BODY> \
  For classes in these these packages use <b>fully qualified</b> names. <p> \
  Names of packages must be separated with a space (for example, "java.awt org.omg.CORBA/r" \
  <ul> \
  <li> \
  * means all packages. \
  <li> \
  /r means a recursive option (for example, "java/r" means "java","java.awt","java.awt.color" etc.) \
  <li> \
  You can use Java-style names such as "java.*" \
  </ul> \
  Note that this option will not work for packages specified in the  \
  <b>Do not change these names on optimize</b> option.
  </BODY></HTML>


javaSourceFormat_optimizeImportsEnabled = Optimize import statements
javaSourceFormat_optimizeImportsEnabled_description =   <HTML><BODY> \
  Controls whether Together may optimize <b>import statements</b>. For example, \
  whether it may remove unused import statements etc. \
  </BODY></HTML>

javaSourceFormat_optimizeAddImports = Add import statements
javaSourceFormat_optimizeAddImports_description =   <HTML><BODY> \
  Controls whether to <b>add</b> import statements trying to use simple names. For example, \
  whether to transform <code>java.util.TimeZone.getDefault();</code> into<code><pre> \
  import java.util.TimeZone; \n \
  ... \n \
  TimeZone.getDefault();</code></pre> \
  </BODY></HTML>

javaSourceFormat_optimizeRemoveUnusedImports = Remove unused import statements
javaSourceFormat_optimizeRemoveUnusedImports_description =   <HTML><BODY> \
  Controls whether to <b>remove</b> unused import statements. \
  </BODY></HTML>

javaSourceFormat_optimizeRemoveUnusedOndemandImports = Remove 'unused' imports on demand
javaSourceFormat_optimizeRemoveOndemandImports_description =  <HTML><BODY> \
    While optimizing, the formatter may detect packages imported on demand \
    by statements "import name.*;" for which there appear to be no classes \
    referenced in the code. This may happen because there are in fact no such \
    references, but it can also happen because a correspondent library is not \
    available in the current project. Therefore, by default, Together removes \
    such on-demand Import statements only if any class is found in the package. \
    Otherwise it checks settings for this option which are: \
  <ul> \
  <li> \
  <b>Never</b> - formatter will keep corresponding import statements. \
  <li> \
  <b>Always</b> - formatter will remove corresponding import statements \
  and inform you about it by messages in Message pane. <br> \
  Important! Select this value only if you are absolutely \
  sure that all required imported classes/packages are added \
  to project. Otherwise you may "break" your code. \
  <li> \
  <b>Warn only</b> - formatter will warn you about existence of \
  imports on demand that seem to be unused. You then decide \
  whether they are necessary or not. \
  </ul> \
  </BODY></HTML>


javaSourceFormat_optimizeMaxNumberOfClassesToImportOnDemand = Max number of class import statements
javaSourceFormat_optimizeMaxNumberOfClassesToImportOnDemand_description =   <HTML><BODY> \
  Defines the maximum number of import statements of classes from the same package. For example, 2 means that \
  if there are two class import statements:<pre><code> \
  import java.io.Reader; \n \
  import java.io.Writer;</pre></code> \
  Together will replace these lines \
  with <code>import java.io.*;</code> \
  instead of trying to add <code>import java.io.File;</code>   </BODY></HTML>

javaSourceFormat_optimizeImportsOrder = Order of import statements
javaSourceFormat_optimizeImportsOrder_description = <HTML><BODY> \
  Defines the order of import statements.<p> \
  This string may contain names of classes and/or options separated by spaces. An option placed as \
  a suffix of a group applies to this group only. An option placed separately applies to all following \
  groups. Available options are: \
  <ul> \
  <li> \
  /r  - all classes from all subpackages (recursive) \
  <li> \
  /!r - non-recursive \
  <li> \
  /a  - alphabetical sorting in the group (otherwise "as is") \
  <li> \
  /i  - "as is" - non-alphabetical sorting \
  <li> \
  * - asterisk lack of a package name means "all other required imports except the specified ones here". \
  If you haven't put * in the string, it is added automatically at the end. \
  <li> \
  /e  - put an empty line between groups \
  <li> \
  /d  - always use the * wildcard in import statements - if present this option overrides the state of \
  the corresponding check boxes. \
  <li> \
  /s  - do not to use the * wildcard in import statements if the number of imported classes from the same \
  package is less than the value of the "Max number of class import statements" option \
  </ul> \
  Default options are /!r, /i, /s <p> \
  For example, "/a /d java/r/d javax.e javax /e * java.util" means:<pre> \
        /a        - sort alphabetical in all next groups \n \
        /d        - use the * wildcard in all required import statements \n \
        java/r/d  - all used classes java.* with subpackages \n \
                    use the * wildcard in required import statements (i.e. java.*, java.awt.* etc.) \n \
        javax.e   - import javax.e class (or package) \n \
        javax     - all other (not javax.e) classes from javax package \n \
        /e        - add an empty line \n \
        *         - all other requierd imports \n \
        java.util - import all classes from java.util package \n \
                    (but not from subpackages)</pre> \
  </BODY></HTML>

cppGroup = C++
cppGroup_description = <HTML><BODY> \
    C++ source code options.<BR> \
    Expand this node to see source code formatting, optimization, and other options for C++.<BR> \
    Note that the C++ "Blueprints" options from previous versions are now available as Source Code Templates. \
    Templates are used as defaults for code construction for such things as classes, members, and links. \
    Source Code Templates are accessible from the Directory page of the Explorer pane. \
    From there you can use speedmenus to open them in the Editor for easy modification. \
</BODY></HTML>

cppFormatMode = Format mode
cppFormatMode_description =   <HTML><BODY> \
  Defines what Together will format in the source code files: \
  <ul> \
  <li> \
  <b>None</b> - Do not format or optimize anything. \
  <li> \
  <b>Format only</b> - Together will format code and comments according to the settings \
  in the <b>Format code</b> and <b>Format Comments</b> groups (they are subgroups of the <b>Formatting options</b> group). \
  </ul> \
  </BODY></HTML>

Includes_kind_description = <HTML><BODY> \
   Defines which kind of include statements Together will generate: \  <ul> \
  <li> \
  <b>Quotes</b> - #include "somefile.ext". \
  <li> \
  <b>Angles</b> - #include &lt;somefile.ext&gt;. \
  <li> \
  <b>Automatic</b> - Filename will be in quotes or in angles depending on the location of the file in relation to the project. \
  Files located under project roots are specified in quotes, while the files located under search roots are in angles.\
  </ul> \
  </BODY></HTML>

cppDefines_description = <HTML><BODY> \
Macro names to be defined while parsing.<br><br> \
  Following macronames have special meaning for Together. \
  Some of them are used in <b>preinclide.inc</b> file to turn on/off preloading \
  sets of macro definitions related some popular c++ IDEs/libraries. \
  <ul> \
  <li> \
  <b>_TCPP_</b> - This macro definition was always on in Together/Professional. \
    It is recommended to keep it defined. \
    It is necessary for proper work of OLE/COM Interface Extractor (from Together/Pro). \
  <li> \
  <b>TS_KEYWORDS_ISO646</b> - for processing all new keywords of ISO 646 standard. \
  <li> \
  <b>TS_KEYWORDS_VC</b> - for processing all new keywords in the VC++(6.0). \
  <li> \
  <b>TS_PREINCLUDE_MICROSOFT_WINDOWS</b> - MS-Windows related macro definitions. \
  <li> \
  <b>TS_PREINCLUDE_MICROSOFT_COM</b> - Microsoft COM related macro definitions \
  <li> \
  <b>TS_PREINCLUDE_MICROSOFT_VISUAL_C</b> - Microsoft C++ and MFC related macro definitions \
  <ul> \
  Following macros can be used to change result of MFC macros expading. \
  <li> \
  <b>MFC_MACROS_SHOW_EXPANDED</b> - macros expaneded as originally defined in MFC \
  <li> \
  <b>MFC_MACROS_SHOW</b> - macros expaneded as operations \
  <li> \ If none of these two defined macros expanded to nothing. \
  </ul> \
  <li> \
  <b>TS_PREINCLUDE_ATL</b> - ATL related macro definitions \
  <li> \
  <b>TS_PREINCLUDE_BORLAND_CPP_BUILDER</b> - Borland C++ Builder related macro definitions \
  <li> \
  <b>TS_PREINCLUDE_BORLAND_CPP</b> - Borland C++ 5.0 related macro definitions \
  </ul> \
  </BODY></HTML>

cppSkipStd_description = <HTML><BODY> \
Controls whether parser will try to search and process standard include directives \
(here standard means include directive in angle-bracket form "#include &lt;someFilePath.h&gt;"). \
  </BODY></HTML>


idlGroup = CORBA IDL
idlGroup_description = <HTML><BODY> \
    CORBA IDL source code options.<BR> \
    Expand this node to see source code formatting options for CORBA IDL.<BR> \
    Note that Source Code Templates are used as defaults for code construction for such things as classes, members, and links. \
    Source Code Templates are accessible from the Directory page of the Explorer pane. \
    From there you can use speedmenus to open them in the Editor for easy modification. \
</BODY></HTML>

comidlGroup = COM IDL
comidlGroup_description = <HTML><BODY> \
    COM IDL source code options.<BR> \
    Expand this node to see source code formatting options for COM IDL.<BR> \
    Note that Source Code Templates are used as defaults for code construction for such things as classes, members, and links. \
    Source Code Templates are accessible from the Directory page of the Explorer pane. \
    From there you can use speedmenus to open them in the Editor for easy modification. \
</BODY></HTML>
