viewManagement = View Management
viewManagement_description = <HTML><BODY> \
View Management options let you to control what your want to see and when. Specify how different kinds of elements display in diagrams, or even whether they show up at all. With the View Management page you can: \
<ul> \
<li> \
control the general level of detail shown in diagrams \
<li> \
control whether members in Classes display with UML or Java format (products with Java language support) \
<li> \
show or hide subpackages in diagrams \
<li> \
show or elide Java Beans in Class diagrams \
<li> \
control the display of dependencies \
<li> \
show or hide any of 9 pre-defined and 2 user-defined aggregations of diagram elements \
</ul> \
</BODY></HTML>



details = Diagram detail level
details_description = <HTML><BODY> \
    Defines how much of the element's information will be displayed in the diagrams: \
    <ul> \
    <LI><B>Default</B> - the default value for the current detail level : \
        <UL> \
        <LI>Analysis (for the Business Modeler role) \
        <LI>Design (for the Designer and Developer roles) \
        <LI>Implementation (for the Programmer role) \
        </UL> \
    <li><b>Analysis</b> - names only (no visibility signs)\
    <li><b>Design</b> - names and types (visibility signs are shown) \
    <li><b>Implementation</b> - names and types, parameters for operations, initial values of attributes (visibility signs are shown) \
    Initially the default detail level depends of the selected role choosed during installation. \
    </ul> \
    </BODY></HTML>

formatting = Member format
formatting_description =  <HTML><BODY> \
Controls the format of members in class diagrams: \
 <ul> \
 <li> \
<b>UML</b> format (default): <br> \
  Operations are displayed as &lt;name&gt; (parameters) : &lt;type&gt; <br> \
  Attributes are displayed as &lt;name&gt; : &lt;type&gt; \
 <li> \
<b>Java</b> format: <br> \
  Operations are displayed as &lt;type&gt; &lt;name&gt; (parameters)<br> \
  Attributes are displayed as &lt;type&gt; &lt;name&gt;<br> \
 </ul> \
 </BODY></HTML>



showPackageContents = Show subpackage contents
showPackageContents_description =   <HTML><BODY> \
  Defines how much of a subpackage's contents will be shown in the diagram: \
  <ul> \
  <li> \
  If checked - Together will show subpackage as a package icon \
  with a list of all classes, interfaces, and subpackages within the subpackage \
  <li> \
  If unchecked - Together will show subpackage as a package icon without classes, interfaces, or subpackages \
  within the subpackage. \
  </ul> \
  </BODY></HTML>

showShortcutsInPackage = Show shortcuts
showShortcutsInPackage_description = <HTML><BODY> \
   Specifies whether to show shortcuts to classes from other packages. \
   </BODY></HTML>

beanSupport = Show beans
beanSupport_description = <HTML><BODY> \
    Together is able recognize JavaBean properties and event sets in your source code. \
    It is beyond the scope of this document to describe these fully. \
    You can find detailed information and documentation at Sun's website. \
    <UL> \
    <LI>if checked : any class or interface that satisfies the Java Bean pattern will be shown with a small \
        rectangle on the left side, and all properties and event sets will be shown in a separate compartment below \
        the operations compartment. \
    <LI>if unchecked : Together will not try to recognize Java Beans in classes or interfaces. \
    </UL> \
    Here is a very brief explanation of how a bean property/event set is defined: \
    <P> \
    <B>Simple properties</B><BR>  \
    By default, Together uses design patterns to locate properties by looking for methods of the form: \
    <UL> \
        <LI>public &LT;PropertyType&GT; get&LT;PropertyName&GT;(); \
        <LI>public void set&LT;PropertyName&GT;( &LT;PropertyType&GT; a ); \
    </UL> \
    If it finds a matching pair of "get&LT;PropertyName&GT; " and "set&LT;PropertyName&GT;" methods that take and return the same type, \
    then it regards these methods as defining a read-write property whose name will be "&LT;propertyName&GT;". \
    If it finds only one of these methods, then it regards it as defining either a read-only or a write-only property \
    called "propertyName" So a simple read-write property "foo" might be represented by a pair of methods: \
    <UL> \
        <LI>public Wombat getFoo(); \
        <LI>public void setFoo(Wombat w); \
    </UL> \
    </P> \
    <P> \
    <B>Event sets</B><BR> \
    By default, Together uses the following design pattern to determine which events a bean multicasts. \
    It looks for a pair of methods having the form: \
    <UL> \
        <LI>public void add&LT; EventListenerType&GT; ( &LT; EventListenerType&GT; a) \
        <LI>public void remove&LT; EventListenerType&GT;(&LT; EventListenerType&GT; a) \
    </UL> \
    So for example: \
    <UL> \
        <LI>public void addFredListener(FredListener t); \
        <LI>public void removeFredListener(FredListener t); \
    </UL> \
    </P> \
    <P> \
    <B>Special note for C++ users : </B><BR> \
    The recognition of JavaBeans in the source code is controlled by the Recognize JavaBeans configuration option \
    (there's a toggle on the Main toolbar for this as well). Remember that his option controls bean recognition in Java \
    classes only, since the JavaBeans specification naturally cannot be applied to C++ classes. \
    Thus, regardless of the state of this option, a pair of C++ get/set methods won't be shown as a property. \
    </P> \
</BODY></HTML>

beanAccessors = Show attributes and accessors
beanAccessors_description =  <HTML><BODY> \
If <b>Show beans</b> option is on, this controls whether the bean methods defining bean properties or events will \
be shown in the class icon. If a bean has an attribute with the same name as a property, then such attribute \
is considered a part of a property, and this option also controls whether to show a property's attribute. \
</BODY></HTML>

beanConstructors = Recognize classes without public/default constructor
beanConstructors_description =  <HTML><BODY> \
If this option is off, only classes with none or at least one public constructor will be recongized as JavaBeans \
(if they define bean properties/event sets). \
<p> \
If this options is on, no restrictions on the constructors are applied.
</BODY></HTML>


recognizeInterfaces = Recognition of properties/event sets in interfaces
recognizeInterfaces_description =  <HTML><BODY> \
JavaBeans specification declares that only classes can be JavaBeans. This option provides a fine-grained \
interface recognition control, because sometimes it is handy to see bean properties/event sets recognized \
in interfaces: \
<ul> \
  <li> \
  <b>Do not recognize anything</b> - interfaces will be shown as usual, without recognition of bean properties/event sets in them. \
  <li> \
  <b>Recognize but don't show as a bean</b> - if an interface contains methods defining bean properties/event sets, then they will be recognized \
and shown in the separate compartments in the interface's icon; but the icon itself will be drawn as a regular interface \
icon, without a Bean symbol on the left. \
  <li> \
  <b>Recognize and show as a bean</b> - works like the previos option, except that if an interface defines properties/even sets \
the interface's icon will be shown with a Bean symbol on the left. \
  </ul> \
</BODY></HTML>

recognizeInEJB = Recognize in EJB
recognizeInEJB_description = <HTML><BODY> \
    If checked then Together will recognize get/set and add/remove methods inside of an EJB. \
    </BODY></HTML>

classes_referenced = Referenced Classes
classes_referenced_description =   <HTML><BODY> \
 Defines whether the names of referenced classes are displayed in the diagram. \
  <ul> \
  <li><b>Hide</b> - names of referenced classes are not displayed in the diagram. \
  <li><b>Show name</b> - when a class extends some other class that is not shown in the diagram, \
 the name of the extended class is shown right-aligned under the name of the extending class \
  </ul> \
  </BODY></HTML>


dependencies = Dependencies
dependencies_description =  <HTML><BODY> \
     Options for dependencies between classes or interfaces. \
     </BODY></HTML>

dependenciesCheck = Check
dependenciesCheck_description = <HTML><BODY> \
If dependency check between classes is on, this defines what Together will analyze while searching for dependencies between \
classes or interfaces: \
  <ul> \
  <li> \
  <b>Declarations only</b> - Together will analyze only declarations of attributes, return values of methods and types of \
  parameters. \
  <li> \
  <b>All usages</b> - Together will also analyze bodies of methods and initial values. \
  </ul> \
<b>WARNING:</b> Choosing this setting could result in slow performance or large diagrams. 
</BODY></HTML>

dependenciesBetweenClasses = Show between classes
dependenciesBetweenClasses_description  = <HTML><BODY> \
Controls whether Together will check for dependencies between classes or interfaces, and then display \
the dependency links on the screen. \
<b>WARNING:</b> Choosing this setting could result in slow performance or large diagrams. \
    </BODY></HTML>


sequenceDiagram = Sequence diagram
sequenceDiagram_description = <HTML><BODY> \
    Options for a sequence diagram. \
    </BODY></HTML>

showClassBelowObject = Show classname below objectname
showClassBelowObject_description = <HTML><BODY> \
    Specifes whether to show class name below object name, or to the right from it. \
    </BODY></HTML>

showMessageNumbers = Show message numbers
showMessageNumbers_description = <HTML><BODY> \
    Specifes whether to show message numbers. \
    </BODY></HTML>

maxCallNestingNum = When generating, max. number of call nesting
maxCallNestingNum_description = <HTML><BODY> \
    During source code parsing the number of call nesting is increased by 1 before processing of each method definition. \
    The maximum number of call nesting is used to terminate the parsing. \
    The more this value, the more degree of complexity of the generated Sequence Diagram. \
    </BODY></HTML>

includeSelfMessages = When generating, include messages to self
includeSelfMessages_description = <HTML><BODY> \
    Suppress/Show messages to self on the generated Sequence Diagram. \
    </BODY></HTML>

EJB_Home = EJB Home interfaces
EJB_Home_description = Specifies whether to show EJB home interfaces on diagram.

EJB_Remote = EJB Remote interfaces
EJB_Remote_description = Specifies whether to show EJB remote interfaces on diagram.

EJB_Bean = EJB implementation classes
EJB_Bean_description = Specifies whether to show EJB implementation classes on diagram.

EJB_PK = EJB primary key classes
EJB_PK_description = Specifies whether to show EJB primary key classes on diagram.

