Menu
▾
▴
[Scstudio-commits] SF.net SVN: scstudio:[661] trunk/doc/help
|
From: <ag...@us...> - 2010-03-05 15:32:21
|
Revision: 661
http://scstudio.svn.sourceforge.net/scstudio/?rev=661&view=rev
Author: agmy
Date: 2010-03-05 15:32:12 +0000 (Fri, 05 Mar 2010)
Log Message:
-----------
Resolution of pictures in documentation (acyclic, nonlocal choice, fifo) changed to 80 px/inch
Modified Paths:
--------------
trunk/doc/help/acyclic/acyclic.html
trunk/doc/help/acyclic/pictures/acyclic.png
trunk/doc/help/acyclic/pictures/cyclic_result.png
trunk/doc/help/acyclic/pictures/cyclic_simple.png
trunk/doc/help/fifo/fifo.html
trunk/doc/help/fifo/pictures/fifo1.png
trunk/doc/help/fifo/pictures/fifo2.png
trunk/doc/help/fifo/pictures/label_channel_fifo.png
trunk/doc/help/fifo/pictures/nonfifo1.png
trunk/doc/help/fifo/pictures/simple_non_fifo.png
trunk/doc/help/localchoice/localchoice.html
trunk/doc/help/localchoice/pictures/simple_nonlocal.png
trunk/doc/help/localchoice/pictures/simple_nonlocal_MSCA.png
trunk/doc/help/localchoice/pictures/simple_nonlocal_MSCB.png
trunk/doc/help/localchoice/pictures/simple_nonlocal_implied.png
trunk/doc/help/localchoice/pictures/simple_nonlocal_result.png
Modified: trunk/doc/help/acyclic/acyclic.html
===================================================================
--- trunk/doc/help/acyclic/acyclic.html 2010-03-05 12:21:53 UTC (rev 660)
+++ trunk/doc/help/acyclic/acyclic.html 2010-03-05 15:32:12 UTC (rev 661)
@@ -9,10 +9,10 @@
<BODY>
<H1>Acyclic property</H1>
<P> Acyclic property ensures that there is no cyclic dependency among events in a MSC. Such an dependency is erroneous, because it requires to wait with sending a message until it is received. An example of such MSC design can be seen on the following figure:</P>
-<IMG SRC="pictures/cyclic_simple.png" WIDTH="187" HEIGHT="293" BORDER="0" ALT="Cyclic MSC" TITLE="Cyclic MSC">
+<IMG SRC="pictures/cyclic_simple.png" BORDER="0" ALT="Cyclic MSC" TITLE="Cyclic MSC">
<P> Sending message <I>m2</I> may not be done until message <I>m1</I> is received, but message <I>m1</I> may not be send until message <I>m2</I> is received.</P>
<P> Result of SCStudio on such design highlights the cyclic dependency:</P>
-<IMG SRC="pictures/cyclic_result.png" WIDTH="187" HEIGHT="293" BORDER="0" ALT="SCStudio result" TITLE="SCStudio result">
+<IMG SRC="pictures/cyclic_result.png" BORDER="0" ALT="SCStudio result" TITLE="SCStudio result">
<P> A more tricky example of an acyclic design:</P>
-<IMG SRC="pictures/acyclic.png" WIDTH="187" HEIGHT="293" BORDER="0" ALT="Acyclic MSC" TITLE="Acyclic MSC">
-</BODY>
\ No newline at end of file
+<IMG SRC="pictures/acyclic.png" BORDER="0" ALT="Acyclic MSC" TITLE="Acyclic MSC">
+</BODY>
Modified: trunk/doc/help/acyclic/pictures/acyclic.png
===================================================================
(Binary files differ)
Modified: trunk/doc/help/acyclic/pictures/cyclic_result.png
===================================================================
(Binary files differ)
Modified: trunk/doc/help/acyclic/pictures/cyclic_simple.png
===================================================================
(Binary files differ)
Modified: trunk/doc/help/fifo/fifo.html
===================================================================
--- trunk/doc/help/fifo/fifo.html 2010-03-05 12:21:53 UTC (rev 660)
+++ trunk/doc/help/fifo/fifo.html 2010-03-05 15:32:12 UTC (rev 661)
@@ -24,7 +24,7 @@
instance <I>q</I> receives message <I>m2</I> before <I>m1. </I>Because
we are having a FIFO channel between instances <I>p</I> and <I>q</I>,
this is not possible and leads to a deadlock.</P>
-<img src="pictures/simple_non_fifo.png" width="304" height="180" border="0" alt="Example of a non-fifo design" title="Example of a non-fifo design">
+<img src="pictures/simple_non_fifo.png" border="0" alt="Example of a non-fifo design" title="Example of a non-fifo design">
<P>A more formal definition follows:</P>
<P>BMSC is FIFO if for all receive events c, d and their matching send events
@@ -33,16 +33,16 @@
to the same channel.</P>
<P>Tricky examples of FIFO MSCs:</P>
-<img src="pictures/fifo1.png" width="228" height="304" border="0" alt="FIFO MSC design" title="FIFO MSC design">
-<img src="pictures/fifo2.png" width="228" height="304" border="0" alt="FIFO MSC design" title="FIFO MSC design">
+<img src="pictures/fifo1.png" border="0" alt="FIFO MSC design" title="FIFO MSC design">
+<img src="pictures/fifo2.png" border="0" alt="FIFO MSC design" title="FIFO MSC design">
<P>An example of a non-FIFO design can be seen on the following figure:</P>
-<img src="pictures/nonfifo1.png" width="228" height="304" border="0" alt="non-FIFO MSC design" title="non-FIFO MSC design">
+<img src="pictures/nonfifo1.png" border="0" alt="non-FIFO MSC design" title="non-FIFO MSC design">
<H3>FIFO channel for every pair of instances and labels</H3>
<P>In this case we can have more than one FIFO channel between two processes. For every label there is one channel. Everything what has satisfied FIFO property in the previous case, will satisfy also in this case. The difference can be seen on the following FIFO example:</P>
-<img src="pictures/label_channel_fifo.png" width="304" height="180" border="0" alt="FIFO MSC design" title="FIFO MSC design">
+<img src="pictures/label_channel_fifo.png" border="0" alt="FIFO MSC design" title="FIFO MSC design">
<P>Messages <I>m2</I> and <I>m1</I> are not in the same channel, therefore they may arrive in
any order.</P>
Modified: trunk/doc/help/fifo/pictures/fifo1.png
===================================================================
(Binary files differ)
Modified: trunk/doc/help/fifo/pictures/fifo2.png
===================================================================
(Binary files differ)
Modified: trunk/doc/help/fifo/pictures/label_channel_fifo.png
===================================================================
(Binary files differ)
Modified: trunk/doc/help/fifo/pictures/nonfifo1.png
===================================================================
(Binary files differ)
Modified: trunk/doc/help/fifo/pictures/simple_non_fifo.png
===================================================================
(Binary files differ)
Modified: trunk/doc/help/localchoice/localchoice.html
===================================================================
--- trunk/doc/help/localchoice/localchoice.html 2010-03-05 12:21:53 UTC (rev 660)
+++ trunk/doc/help/localchoice/localchoice.html 2010-03-05 15:32:12 UTC (rev 661)
@@ -11,15 +11,15 @@
<P>is a property of an HMSC node, that has more than one successor, occurring when multiple different behaviors (branches MSC A or MSC B) are possible and the branches are initiated by different instances (MSC A is initiated by instance p, MSC B is initiated by instance q). Therefore the resulting behavior of the system may contain a combination of both branches, resulting in a nonspecified implied behavior. </P>
<DIV class="gallery vary">
<table><caption align="bottom">HMSC</caption><tr><td>
-<IMG SRC="pictures/simple_nonlocal.png" WIDTH="492" HEIGHT="246" BORDER="0" ALT="HMSC specification with a branching node" title="HMSC specification with a branching node">
+<IMG SRC="pictures/simple_nonlocal.png" BORDER="0" ALT="HMSC specification with a branching node" title="HMSC specification with a branching node">
</tr></td></table>
<table><caption align="bottom">MSC A</caption><tr><td>
-<IMG SRC="pictures/simple_nonlocal_MSCA.png" WIDTH="264" HEIGHT="297" BORDER="0" ALT="MSC A" TITLE="MSC A">
+<IMG SRC="pictures/simple_nonlocal_MSCA.png" BORDER="0" ALT="MSC A" TITLE="MSC A">
</tr></td></table>
<table><caption align="bottom">MSC B</caption><tr><td>
-<IMG SRC="pictures/simple_nonlocal_MSCB.png" WIDTH="264" HEIGHT="297" BORDER="0" ALT="MSC B" TITLE="MSC B">
+<IMG SRC="pictures/simple_nonlocal_MSCB.png" BORDER="0" ALT="MSC B" TITLE="MSC B">
</tr></td></table>
</DIV>
@@ -34,10 +34,10 @@
<DIV class="gallery vary">
<table><caption align="bottom">Result of SCStudio</caption><tr><td>
-<IMG SRC="pictures/simple_nonlocal_result.png" WIDTH="330" HEIGHT="200" BORDER="0" ALT="Result of SCStudio" TITLE="Result of SCStudio">
+<IMG SRC="pictures/simple_nonlocal_result.png" BORDER="0" ALT="Result of SCStudio" TITLE="Result of SCStudio">
</tr></td></table>
<DIV class="gallery vary">
<table><caption align="bottom">Implied behavior</caption><tr><td>
-<IMG SRC="pictures/simple_nonlocal_implied.png" WIDTH="240" HEIGHT="297" BORDER="0" ALT="Implied behavior" TITLE="Implied behavior">
+<IMG SRC="pictures/simple_nonlocal_implied.png" BORDER="0" ALT="Implied behavior" TITLE="Implied behavior">
</tr></td></table>
-</BODY>
\ No newline at end of file
+</BODY>
Modified: trunk/doc/help/localchoice/pictures/simple_nonlocal.png
===================================================================
(Binary files differ)
Modified: trunk/doc/help/localchoice/pictures/simple_nonlocal_MSCA.png
===================================================================
(Binary files differ)
Modified: trunk/doc/help/localchoice/pictures/simple_nonlocal_MSCB.png
===================================================================
(Binary files differ)
Modified: trunk/doc/help/localchoice/pictures/simple_nonlocal_implied.png
===================================================================
(Binary files differ)
Modified: trunk/doc/help/localchoice/pictures/simple_nonlocal_result.png
===================================================================
(Binary files differ)
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
