[jbosstools-commits] JBoss Tools SVN: r6273 - trunk/jbpm/docs/reference/en/modules.

Author: ochikvina Date: 2008-02-12 12:12:28 -0500 (Tue, 12 Feb 2008) New Revision: 6273 Modified: trunk/jbpm/docs/reference/en/modules/Quick_Howto_Guide.xml trunk/jbpm/docs/reference/en/modules/Test_Drive_Proc.xml trunk/jbpm/docs/reference/en/modules/The_JBoss_jBPM_Int_Mech.xml trunk/jbpm/docs/reference/en/modules/guided_tour_jboss_jbpmgpd.xml trunk/jbpm/docs/reference/en/modules/jboss_jbpm_runtime_installation.xml trunk/jbpm/docs/reference/en/modules/the_views.xml Log: http://jira.jboss.com/jira/browse/JBDS-155- adding "scale" attribute to the necessary images; putting fullstops and commas in proper positions. Modified: trunk/jbpm/docs/reference/en/modules/Quick_Howto_Guide.xml =================================================================== --- trunk/jbpm/docs/reference/en/modules/Quick_Howto_Guide.xml 2008-02-12 17:09:45 UTC (rev 6272) +++ trunk/jbpm/docs/reference/en/modules/Quick_Howto_Guide.xml 2008-02-12 17:12:28 UTC (rev 6273) @@ -36,8 +36,7 @@ <mediaobject> <imageobject> - <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_1.png" - scalefit="1"/> + <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_1.png"/> </imageobject> </mediaobject> </figure> @@ -51,14 +50,14 @@ <para> You can add Tasks to Task nodes and then configure them in a similar manner as the Action configuration mechanism. Let&apos;s consider the process definition similar to the previous one that contains three nodes: Start state, Task node and End state. The - Properties view for selected Task node includes several tabs. </para> + <property>Properties view</property> for selected Task node includes several tabs. </para> <figure> <title>The Properties View of the selected Task Node</title> <mediaobject> <imageobject> <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_2.png" - scalefit="1"/> + scale="75"/> </imageobject> </mediaobject> </figure> @@ -71,25 +70,25 @@ <mediaobject> <imageobject> <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_3.png" - scalefit="1"/> + scale="80"/> </imageobject> </mediaobject> </figure> <para>Every added Task has its own configuration possibilities. You can access them through - the Properties view as well.</para> + the <property>Properties view</property> as well.</para> <figure> <title>The Task properties</title> <mediaobject> <imageobject> <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_4.png" - scalefit="1"/> + scale="80"/> </imageobject> </mediaobject> </figure> - <para>The <property>General</property> page is a place where you can specify the name of a + <para>The <property>General page</property> is a place where you can specify the name of a Task and its description. For instance, let it be <emphasis> <property>approve oder</property> </emphasis> with appropriate description that you can see in the figure below.</para> @@ -99,7 +98,7 @@ <mediaobject> <imageobject> <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_5.png" - scalefit="1"/> + scale="80"/> </imageobject> </mediaobject> </figure> @@ -120,7 +119,7 @@ <mediaobject> <imageobject> <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_6.png" - scalefit="1"/> + scale="80"/> </imageobject> </mediaobject> </figure> @@ -132,19 +131,19 @@ <property>Notify</property> </emphasis> attributes. It means that the Task should be accomplished in 2 business days and the assignee will be notified by email when the task is assigned. To specify how the - Task should be assigned switch on to the <property>Assignment</property> page.</para> + Task should be assigned switch on to the <property>Assignment page</property>.</para> <figure> <title>The Task Assignment Page</title> <mediaobject> <imageobject> <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_7.png" - scalefit="1"/> + scale="80"/> </imageobject> </mediaobject> </figure> - <para>On the Reminder page you can specify whether the assignee will be reminded of the task + <para>On the <property>Reminder page</property> you can specify whether the assignee will be reminded of the task that awaits him.</para> <figure> @@ -152,7 +151,7 @@ <mediaobject> <imageobject> <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_8.png" - scalefit="1"/> + scale="80"/> </imageobject> </mediaobject> </figure> @@ -165,7 +164,7 @@ <mediaobject> <imageobject> <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_9.png" - scalefit="1"/> + scale="80"/> </imageobject> </mediaobject> </figure> Modified: trunk/jbpm/docs/reference/en/modules/Test_Drive_Proc.xml =================================================================== --- trunk/jbpm/docs/reference/en/modules/Test_Drive_Proc.xml 2008-02-12 17:09:45 UTC (rev 6272) +++ trunk/jbpm/docs/reference/en/modules/Test_Drive_Proc.xml 2008-02-12 17:12:28 UTC (rev 6273) @@ -27,7 +27,7 @@ Library container and the most important of them is the <emphasis> <property>.jar</property> </emphasis> file containing the core jBPM classes. While working on the project you could - find them all in the Package Explorer.</para> + find them all in the <property>Package Explorer</property>.</para> <figure> <title>The jBPM Libraries</title> @@ -99,7 +99,7 @@ <mediaobject> <imageobject> - <imagedata fileref="images/Test_Drive_Proc/test_driv_proc_2b.png" scale="75"/> + <imagedata fileref="images/Test_Drive_Proc/test_driv_proc_2b.png"/> </imageobject> </mediaobject> </figure> Modified: trunk/jbpm/docs/reference/en/modules/The_JBoss_jBPM_Int_Mech.xml =================================================================== --- trunk/jbpm/docs/reference/en/modules/The_JBoss_jBPM_Int_Mech.xml 2008-02-12 17:09:45 UTC (rev 6272) +++ trunk/jbpm/docs/reference/en/modules/The_JBoss_jBPM_Int_Mech.xml 2008-02-12 17:12:28 UTC (rev 6273) @@ -32,15 +32,15 @@ signalling. </para> <para> To make things a little bit more concrete, let&apos;s create a new class called <emphasis> - <property>HelloActionHandler</property> - </emphasis>. For that firstly we&apos;ll create a new package <emphasis> + <property>HelloActionHandler</property>. + </emphasis> For that firstly we&apos;ll create a new package <emphasis> <property>com.jbay.action</property> </emphasis> in the <emphasis> <property>src/java/main</property> </emphasis> folder of our project. Then, we should call New Class Creation wizard as usual by right-clicking and navigating <emphasis> - <property>New > Class</property> - </emphasis>. </para> + <property>New > Class</property>. + </emphasis> </para> <figure> <title>Creating HelloActionHendler Class</title> @@ -81,8 +81,7 @@ <mediaobject> <imageobject> - <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_2.png" - scale="75"/> + <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_2.png" scale="75"/> </imageobject> </mediaobject> </figure> @@ -127,8 +126,8 @@ transition from the start state to the auction state. So after the signal, the process should be in the auction state as in the previous scenario. But moreover, the <emphasis> <property>greeting</property> - </emphasis> variable should exist and contain the string &quot;Hello from - ActionHandler&quot;. That&apos;s what we assert in the last lines of the test + </emphasis> variable should exist and contain the string <emphasis>&quot;Hello from + ActionHandler&quot;</emphasis>. That&apos;s what we assert in the last lines of the test method.</para> @@ -160,7 +159,7 @@ <mediaobject> <imageobject> - <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_5.png"/> + <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_5.png" scale="80"/> </imageobject> </mediaobject> </figure> @@ -172,7 +171,7 @@ <mediaobject> <imageobject> - <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_6.png"/> + <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_6.png" scale="80"/> </imageobject> </mediaobject> </figure> @@ -187,8 +186,7 @@ <mediaobject> <imageobject> - <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_7.png" - scale="75"/> + <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_7.png" scale="80"/> </imageobject> </mediaobject> </figure> @@ -220,7 +218,7 @@ <mediaobject> <imageobject> <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_10.png" - scale="75"/> + scale="70"/> </imageobject> </mediaobject> </figure> Modified: trunk/jbpm/docs/reference/en/modules/guided_tour_jboss_jbpmgpd.xml =================================================================== --- trunk/jbpm/docs/reference/en/modules/guided_tour_jboss_jbpmgpd.xml 2008-02-12 17:09:45 UTC (rev 6272) +++ trunk/jbpm/docs/reference/en/modules/guided_tour_jboss_jbpmgpd.xml 2008-02-12 17:12:28 UTC (rev 6273) @@ -136,7 +136,7 @@ <mediaobject> <imageobject> <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour6.png" - scale="75"/> + scale="60"/> </imageobject> </mediaobject> </figure> @@ -147,8 +147,8 @@ with two .xml files : <emphasis> <property>gpd.xml</property> </emphasis> and <emphasis> - <property>processdefinition.xml</property> - </emphasis>.</para> + <property>processdefinition.xml</property>. + </emphasis></para> <para>The <emphasis> <property>gpd.xml</property> </emphasis> contains the graphical information used by the process @@ -171,8 +171,8 @@ <?dbhtml filename="adding_the_nodes.html"?> <title>Adding the Nodes</title> <para>At first select respectively <emphasis> - <property>Start</property> - </emphasis>, <emphasis> + <property>Start</property>, + </emphasis> <emphasis> <property>State</property> </emphasis> and <emphasis> <property>End</property> @@ -182,8 +182,8 @@ <title>A Simple Process With Three Nodes</title> <mediaobject> <imageobject> - <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour7.png" - scale="75"/> + <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour7.png" + scale="60"/> </imageobject> </mediaobject> </figure> @@ -208,7 +208,7 @@ <mediaobject> <imageobject> <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour8.png" - scale="75"/> + scale="60"/> </imageobject> </mediaobject> </figure> Modified: trunk/jbpm/docs/reference/en/modules/jboss_jbpm_runtime_installation.xml =================================================================== --- trunk/jbpm/docs/reference/en/modules/jboss_jbpm_runtime_installation.xml 2008-02-12 17:09:45 UTC (rev 6272) +++ trunk/jbpm/docs/reference/en/modules/jboss_jbpm_runtime_installation.xml 2008-02-12 17:12:28 UTC (rev 6273) @@ -23,8 +23,8 @@ some situations with Sun-based VMs.</para></note> <para>Navigate to <emphasis> - <property>Window &gt; Preferences &gt; JBoss jBPM &gt; Runtime Locations</property> - </emphasis>. Here you can add, edit and remove JBoss jBPM installation locations. Click <emphasis> + <property>Window &gt; Preferences &gt; JBoss jBPM &gt; Runtime Locations</property>. + </emphasis> Here you can add, edit and remove JBoss jBPM installation locations. Click <emphasis> <property>Add</property> </emphasis> button. In the dialog that appeared enter a name for a newly added jBPM runtime and point to the correct location of this package on your harddrive. Click <emphasis> Modified: trunk/jbpm/docs/reference/en/modules/the_views.xml =================================================================== --- trunk/jbpm/docs/reference/en/modules/the_views.xml 2008-02-12 17:09:45 UTC (rev 6272) +++ trunk/jbpm/docs/reference/en/modules/the_views.xml 2008-02-12 17:12:28 UTC (rev 6273) @@ -13,33 +13,34 @@ <para>The views are used for representation and navigation the resources you are working on at the moment. One of the advantages of all the views is that all modifications made in the currant-active file are immediately displayed in them. Let’s get acquainted more closely - with those that the jPDL perspective provides. </para> + with those that the <property>jPDL perspective</property> provides. </para> <figure> <title>The jPDL Perspective Views and Editors</title> <mediaobject> <imageobject> - <imagedata fileref="images/the_views/the_views.png" scale="75"/> + <imagedata fileref="images/the_views/the_views.png" scale="60"/> </imageobject> </mediaobject> </figure> - <para>As you can see in the picture above, the jPDL perspective contains a complete set of + <para>As you can see in the picture above, the <property>jPDL perspective</property> contains a complete set of functionality that&apos;s necessary for working on the jBPM project.</para> <section id="the_outline_view"> <?dbhtml filename="the_outline_view.html"?> <title>The Outline View</title> - <para>To have a way to quickly see an outline of the process use the Outline view that is + <para>To have a way to quickly see an outline of the process use the <emphasis> + <property>Outline view</property></emphasis> that is presented as the classical tree. If it is not visible select <emphasis> - <property>Window &gt; Show view &gt; Outline</property> - </emphasis>.</para> + <property>Window &gt; Show view &gt; Outline</property>. + </emphasis></para> <figure> <title>The Overview View</title> <mediaobject> <imageobject> - <imagedata fileref="images/the_views/the_views1.png" scale="75"/> + <imagedata fileref="images/the_views/the_views1.png"/> </imageobject> </mediaobject> </figure> @@ -49,14 +50,15 @@ <?dbhtml filename="the_outline_view.html"?> <title>The Overview</title> <para>The main advantage of this view is that it gives visual representation of the whole - currant-developing process. Besides, the Overview comes as a scrollable thumbnail which + currant-developing process. Besides, the <emphasis> + <property>Overview</property></emphasis> comes as a scrollable thumbnail which enables a better navigation of the process structure if it&apos;s too large.</para> <figure> <title>The Overview</title> <mediaobject> <imageobject> - <imagedata fileref="images/the_views/the_views2.png" scale="75"/> + <imagedata fileref="images/the_views/the_views2.png"/> </imageobject> </mediaobject> </figure> @@ -67,8 +69,8 @@ <title>The Properties View</title> <para> Here, we dwell on the JBDS <property>Properties view</property>.</para> <para>Notice if it&apos;s not visible you can access it by navigating <emphasis> - <property>Window &gt; Show view &gt; Properties</property> - </emphasis>.</para> + <property>Window &gt; Show view &gt; Properties</property>. + </emphasis></para> <para>The view shows the relevant properties of the selected item in the tabbed form. Every item has its own set of properties, which can be directly editable in the Properties view or by brining up the context menu.</para> @@ -84,11 +86,11 @@ <para>For example, on the picture above the Properties view displays all the properties for a selected transition. Its name has been changed to <emphasis> - <property>to_auction</property> - </emphasis>. We&apos;ve done it directly in active General tab of the view. The same + <property>to_auction</property>. + </emphasis> We&apos;ve done it directly in active General tab of the view. The same way let&apos;s change the name for the second transition to <emphasis> - <property>to_end</property> - </emphasis>.</para> + <property>to_end</property>. + </emphasis></para> <para>If no one item is selected, the view represents the properties of the whole process definition. </para> @@ -102,17 +104,17 @@ </figure> <para>In this case, it contains six tabs. The first one is the <emphasis> - <property>General</property></emphasis>. It allows to specify + <property>General</property>.</emphasis> It allows to specify a process name and add necessary description. To illustrate let&apos;s change the process definition name to <emphasis> - <property>jbay</property> + <property>jbay</property>. </emphasis></para> </section> <section id="jbpm_gpd_editor"> <?dbhtml filename="direct_editing.html"?> <title>The jBPM Graphical Process Designer editor.</title> - <para>The jBPM GPD editor includes four modes: Diagram, Deployment, Design and Source, which + <para>The <property>jBPM GPD editor</property> includes four modes: Diagram, Deployment, Design and Source, which are available as switchable tabs at the bottom of the editor. Let&apos;s dwell on each of them.</para> @@ -130,14 +132,14 @@ </mediaobject> </figure> - <para>Besides, some properties can be directly edited in the Diagram mode of the + <para>Besides, some properties can be directly edited in the <property>Diagram mode</property> of the graphical editor. One example of this is the <emphasis> <property>name</property> </emphasis> property of nodes. You can edit this directly by selecting the node of which you want to change the name and then click once inside this node. This enables an editor in the node. We change the name of the node to <emphasis> - <property>auction</property> - </emphasis>.</para> + <property>auction</property>. + </emphasis></para> </section> <section id="source_mode"> @@ -155,7 +157,7 @@ </imageobject> </mediaobject> </figure> - <para>The Source mode enables to easily manipulate our XML. That is manually inserting + <para>The <property>Source mode</property> enables to easily manipulate our XML. That is manually inserting and editing necessary elements or attributes. In addition, here you can take advantage of content assist.</para> </section> @@ -180,8 +182,8 @@ directly edited in the second column of the Design mode table.</para> <para>For instance, let’s add a comment on the second transition. For that, you should bring up the context menu for it and choose <emphasis> - <property>Add Before > Comment</property> - </emphasis>.</para> + <property>Add Before > Comment</property>. + </emphasis></para> <figure> <title>Adding a Comment</title> @@ -209,7 +211,7 @@ <?dbhtml filename="the_deployment_view.html"?> <title>The Deployment Mode</title> <para>Finally, to adjust the deployment settings of the project you should switch on to - the tab that opens the Deployment mode. On the picture below the Deployment mode is + the tab that opens the <property>Deployment mode</property>. On the picture below the <property>Deployment mode</property> is performed with default settings. Here, you can easily modify them or, if the settings won&apos;t match your needs, to reset defaults. </para> <figure> @@ -229,5 +231,5 @@ </section> - <para>Now that we&apos;ve seen how to work with jPDL perspective, let's pass on to the project testing.</para> + <para>Now that we&apos;ve seen how to work with <property>jPDL perspective</property>, let's pass on to the project testing.</para> </chapter>