Documentation styling harmonized (issue #782) (#805)

* Documentation: formatting fixed.

* Documentation: PRO contents copied here.

* Documentation: SCTunit documentation excluded for now.

* Documentation: build process fixed.

* Documentation restructuring (issue #781)
* Restructuring done
* Changes for Eclipsehelp done

* Documentation restructuring (issue #781)
* Changes for Hubspot done
* Minor text changes

* Documentation: Hubspot footer change incorporated.

* Documentation: website-specific stuff renamed.

* Documentation: bootstrap updated from v2.1.1 to v3.0.3.

* Documentation: incorporated Alexander Hannweg's CSS changes.

* Documentation: CSS cleaned up (issue #782).

* Documentation: website tweaks

plugins/org.yakindu.sct.doc.user/.settings/org.eclipse.core.resources.prefs

@@ -1,4 +1,3 @@
 eclipse.preferences.version=1
-encoding//css/custom.css=UTF-8
 encoding//model/state_initial_final.sct=UTF-8
 encoding/<project>=UTF-8

plugins/org.yakindu.sct.doc.user/build.xml

@@ -24,7 +24,7 @@
 
     <!-- Target directories for various output formats: -->
     <property name="help.dir" value="help" />
-    <property name="html.dir" value="html" />
+    <property name="website.dir" value="website" />
     <property name="pdf.dir" value="pdf" />
     <property name="epub.dir" value="epub" />
 
@@ -59,10 +59,11 @@
         <delete includeemptydirs="true" failonerror="false">
             <fileset dir="${basedir}" defaultexcludes="false">
                 <include name="${help.dir}/**" />
-                <include name="${html.dir}/**" />
+                <include name="${website.dir}/**" />
                 <include name="${pdf.dir}/**" />
                 <include name="${epub.dir}/**" />
             </fileset>
+            <fileset dir="${src-merged.dir}" />
         </delete>
     </target>
 
@@ -116,7 +117,7 @@
     <!-- Generates the documentation in all supported formats. -->
     <target name="generate.all"
             description="Generates the documentation in all supported formats."
-            depends="generate.eclipsehelp" />
+            depends="generate.eclipsehelp, generate.website" />
 
 
     <!-- Generates the documentation as Eclipse help. -->
@@ -128,6 +129,27 @@
             <taskdef classpathref="wikitext.classpath"
                      resource="org/eclipse/mylyn/wikitext/core/ant/tasks.properties" />
 
+            <!-- Textile source files to turn into HTML: -->
+            <fileset id="fileset.eclipsehelp" dir="${src.dir}">
+                <include name="installation/installation.textile" />
+                <include name="tutorials/tutorials.textile" />
+                <include name="user-guide/overview.textile" />
+                <include name="user-guide/editing_statecharts.textile" />
+                <include name="user-guide/simulating_statecharts.textile" />
+                <include name="user-guide/advanced_simulation.textile" />
+                <include name="user-guide/c-domain.textile" />
+                <include name="user-guide/statechart_language.textile" />
+                <include name="user-guide/generating_code.textile" />
+                <!-- <include name="user-guide/sctunit.textile" /> -->
+            </fileset>
+
+            <!-- Check whether we have all the expected textile source files – no more, no less: -->
+            <fail message="Number of textile source file(s) doesn't match.">
+                <condition>
+                    <resourcecount refid="fileset.eclipsehelp" when="ne" count="9" />
+                </condition>
+            </fail>
+
             <!-- Convert textile source files to HTML: -->
             <wikitext-to-eclipse-help markupLanguage="Textile"
                                       multipleOutputFiles="false"
@@ -135,12 +157,11 @@
                                       formatoutput="true"
                                       validate="true"
                                       failOnValidationError="true"
-                                      failOnValidationWarning="false"
-                                      title="YAKINDU Statechart Tools – Open Source Edition"
+                                      failOnValidationWarning="true"
+                                      sourceEncoding="UTF-8"
+                                      title="YAKINDU Statechart Tools"
                                       helpPrefix="${help.dir}">
-                <fileset dir="${src.dir}">
-                    <include name="**/*.textile" />
-                </fileset>
+                <fileset refid="fileset.eclipsehelp" />
                 <stylesheet url="../${css.dir}/${css.root.file}" />
             </wikitext-to-eclipse-help>
 
@@ -153,6 +174,21 @@
                 </fileset>
             </move>
 
+            <!-- Fix "pro-feature" DIV elements -->
+            <replaceregexp byline="false"
+                           flags="g"
+                           match='&lt;p&gt;&lt;div class="pro-feature"&gt;&lt;/p&gt;'
+                           replace='&lt;div class="pro-feature"&gt;'>
+                <fileset dir="${help.dir}">
+                    <include name="**/*.html" />
+                </fileset>
+            </replaceregexp>
+            <replaceregexp byline="false" flags="g" match='&lt;p&gt;&lt;/div&gt;&lt;/p&gt;' replace='&lt;/div&gt;'>
+                <fileset dir="${help.dir}">
+                    <include name="**/*.html" />
+                </fileset>
+            </replaceregexp>
+
             <!-- Copy the CSS files to the destination directory: -->
             <copy todir="${help.dir}/${css.dir}">
                 <fileset dir="${css.dir}">
@@ -170,4 +206,274 @@
         </sequential>
     </target>
 
-</project>
+    <!-- Generates the documentation as various HTML files, each being composed of selected sections. Each part has a
+         name and a title, and consists of a set of source files. The generated documentation structure looks like this:
+
+         website
+             YCST-installation.html
+             YCST-user-guide.html
+             YCST-tutorials.html
+             css/style.css
+                 …
+             images/…
+    -->
+
+    <target name="generate.website"
+            description="Generates the documentation as various HTML files for the website, each being composed of selected sections."
+            depends="init.wikitext">
+
+        <sequential>
+            <taskdef classpathref="wikitext.classpath"
+                     resource="org/eclipse/mylyn/wikitext/core/ant/tasks.properties" />
+
+            <!-- Installation Guide -->
+            <create-website-part name="YSCT-installation" title="YAKINDU Statechart Tools Installation Guide">
+                <textile-files>
+                    <filelist dir="${src.dir}">
+                        <file name="installation/installation.textile" />
+                    </filelist>
+                </textile-files>
+                <image-files>
+                    <fileset dir="${src.dir}">
+                        <include name="installation/images/**/*" />
+                    </fileset>
+                </image-files>
+            </create-website-part>
+
+            <!-- Tutorials -->
+            <create-website-part name="YSCT-tutorials" title="YAKINDU Statechart Tools Tutorials">
+                <textile-files>
+                    <filelist dir="${src.dir}">
+                        <file name="tutorials/tutorials.textile" />
+                    </filelist>
+                </textile-files>
+                <image-files>
+                    <fileset dir="${src.dir}">
+                        <include name="tutorials/images/**/*" />
+                    </fileset>
+                </image-files>
+            </create-website-part>
+
+            <!-- User Guide -->
+            <create-website-part name="YSCT-user-guide" title="YAKINDU Statechart Tools User Guide">
+                <textile-files>
+                    <filelist dir="${src.dir}">
+                        <file name="user-guide/overview.textile" />
+                        <file name="user-guide/editing_statecharts.textile" />
+                        <file name="user-guide/simulating_statecharts.textile" />
+                        <file name="user-guide/advanced_simulation.textile" />
+                        <file name="user-guide/c-domain.textile" />
+                        <file name="user-guide/statechart_language.textile" />
+                        <file name="user-guide/generating_code.textile" />
+                        <!-- <file name="user-guide/sctunit.textile" /> -->
+                    </filelist>
+                </textile-files>
+                <image-files>
+                    <fileset dir="${src.dir}">
+                        <include name="user-guide/images/**/*" />
+                    </fileset>
+                </image-files>
+            </create-website-part>
+
+        </sequential>
+    </target>
+
+
+
+    <!-- Creates a certain part of the HTML documentation for the website. -->
+    <macrodef name="create-website-part" description="Creates a certain part of the HTML documentation for the website.">
+        <attribute name="name" />
+        <attribute name="title" />
+        <element name="textile-files" />
+        <element name="image-files" />
+
+        <sequential>
+
+            <!-- The directory for this particular part of the HTML documentation: -->
+            <local name="work.dir" />
+            <property name="work.dir" location="${website.dir}" />
+
+            <!-- The names of the concatenated documentation files: -->
+            <local name="index.textile" />
+            <property name="index.textile" value="@{name}.textile" />
+            <local name="index.html" />
+            <property name="index.html" value="@{name}.html" />
+
+            <!-- Append those source files that make up the particular piece of documentation: -->
+            <mkdir dir="${work.dir}" />
+            <concat destfile="${work.dir}/${index.textile}"
+                    append="false"
+                    overwrite="true"
+                    encoding="UTF-8"
+                    outputencoding="UTF-8"
+                    fixlastline="true"
+                    binary="false"
+                    ignoreempty="true">
+                <textile-files />
+            </concat>
+
+            <!-- Convert textile source files to HTML: -->
+            <wikitext-to-html markupLanguage="Textile"
+                              multipleOutputFiles="false"
+                              navigationImages="true"
+                              formatoutput="true"
+                              validate="true"
+                              xhtmlStrict="true"
+                              overwrite="true"
+                              failOnValidationError="true"
+                              failOnValidationWarning="false"
+                              sourceEncoding="UTF-8"
+                              title="@{title}">
+                <fileset dir="${work.dir}">
+                    <include name="${index.textile}" />
+                </fileset>
+                <stylesheet url="${css.dir}/${css.root.file}" />
+            </wikitext-to-html>
+
+            <!-- Load website fragments: -->
+            <sequential unless:set="website.local.files">
+                <loadfile property="website.header" srcFile="${src.dir}/website/header.htmlf" encoding="UTF-8" />
+                <loadfile property="website.footer" srcFile="${src.dir}/website/footer.htmlf" encoding="UTF-8" />
+                <loadfile property="website.calltoaction.download"
+                          srcFile="${src.dir}/website/calltoaction.download.htmlf"
+                          encoding="UTF-8" />
+            </sequential>
+
+            <!-- Load fragments for generating local files which should look simular to the website: -->
+            <sequential if:set="website.local.files">
+                <loadfile property="website.header"
+                          srcFile="${src.dir}/website/header.local.files.htmlf"
+                          encoding="UTF-8" />
+                <loadfile property="website.footer"
+                          srcFile="${src.dir}/website/footer.local.files.htmlf"
+                          encoding="UTF-8" />
+                <loadfile property="website.calltoaction.download"
+                          srcFile="${src.dir}/website/calltoaction.download.local.files.htmlf"
+                          encoding="UTF-8" />
+            </sequential>
+
+            <!-- Replace "<pre><code>" durch "<pre class="prettyprint"><code>": -->
+            <replaceregexp byline="false"
+                           flags="g"
+                           match='&lt;pre&gt;&lt;code&gt;'
+                           replace='&lt;pre class="prettyprint"&gt;&lt;code&gt;'>
+                <fileset dir="${work.dir}">
+                    <include name="${index.html}" />
+                </fileset>
+            </replaceregexp>
+
+            <!-- Replace relative image links by absolute ones for the website, unless we are generating local files: -->
+            <replaceregexp byline="false"
+                           flags="g"
+                           match='src="images/'
+                           replace='src="http://info.itemis.com/hubfs/Yakindu/Statechart_Tools/Documentation/images/'
+                           unless:set="website.local.files">
+                <fileset dir="${work.dir}">
+                    <include name="${index.html}" />
+                </fileset>
+            </replaceregexp>
+
+            <!-- Replace everything up to and including "<body>" by website-specific header: -->
+            <replaceregexp byline="false" flags="s" replace="${website.header}">
+                <regexp pattern="^(.*)&lt;body&gt;" />
+                <fileset dir="${work.dir}">
+                    <include name="${index.html}" />
+                </fileset>
+            </replaceregexp>
+
+            <!-- Replace everything from and including "</body>" by website-specific footer: -->
+            <replaceregexp byline="false" flags="s" replace="${website.footer}">
+                <regexp pattern="&lt;/body&gt;(.*)$" />
+                <fileset dir="${work.dir}">
+                    <include name="${index.html}" />
+                </fileset>
+            </replaceregexp>
+
+            <!-- If the generated code contains a table with the ID "updaterepositories", replace it by a
+                 "call-to-action" button on the website: -->
+            <replaceregexp byline="false" flags="s" replace="${website.calltoaction.download}">
+                <regexp pattern='&lt;table id="updaterepositories"&gt;.*&lt;/table&gt;' />
+                <fileset dir="${work.dir}">
+                    <include name="${index.html}" />
+                </fileset>
+            </replaceregexp>
+
+            <!-- Fix links: -->
+            <adjust-website-document-links document.dir.name="tutorials"
+                                           work.dir="${work.dir}"
+                                           html.file="${index.html}" />
+            <adjust-website-document-links document.dir.name="user-guide"
+                                           work.dir="${work.dir}"
+                                           html.file="${index.html}" />
+            <adjust-website-document-links document.dir.name="installation"
+                                           work.dir="${work.dir}"
+                                           html.file="${index.html}" />
+
+            <!-- Fix "pro-feature" elements -->
+            <replaceregexp byline="false"
+                           flags="g"
+                           match='&lt;p&gt;&lt;div class="pro-feature"&gt;&lt;/p&gt;'
+                           replace='&lt;div class="pro-feature"&gt;'>
+                <fileset dir="${work.dir}">
+                    <include name="${index.html}" />
+                </fileset>
+            </replaceregexp>
+            <replaceregexp byline="false" flags="g" match='&lt;p&gt;&lt;/div&gt;&lt;/p&gt;' replace='&lt;/div&gt;'>
+                <fileset dir="${work.dir}">
+                    <include name="${index.html}" />
+                </fileset>
+            </replaceregexp>
+
+            <!-- Copy the CSS files to the destination directory: -->
+            <copy todir="${work.dir}/${css.dir}">
+                <fileset dir="${css.dir}">
+                    <include name="*" />
+                </fileset>
+            </copy>
+
+            <!-- Copy the image files to the destination directory: -->
+            <copy todir="${work.dir}/${img.dir}" flatten="yes">
+                <image-files />
+            </copy>
+
+            <!-- The textile source file is no longer needed in the website directory. Remove it: -->
+            <delete includeemptydirs="true" failonerror="false">
+                <fileset dir="${website.dir}" defaultexcludes="false">
+                    <include name="${index.textile}" />
+                </fileset>
+            </delete>
+        </sequential>
+
+    </macrodef>
+
+    <!-- Adjusts links in the generated HTML document for either the website or a local equivalent. -->
+    <macrodef name="adjust-website-document-links"
+              description="Adjusts links in the generated HTML document for either the website or a local equivalent.">
+        <attribute name="work.dir" />
+        <attribute name="html.file" />
+        <attribute name="document.dir.name" />
+
+        <sequential>
+            <replaceregexp byline="false"
+                           flags="g"
+                           match='&lt;a href="(\.\./@{document.dir.name})/.+\.html(.*)"&gt;'
+                           replace='&lt;a href="\1/\2"&gt;'
+                           unless:set="website.local.files">
+                <fileset dir="@{work.dir}">
+                    <include name="@{html.file}" />
+                </fileset>
+            </replaceregexp>
+            <replaceregexp byline="false"
+                           flags="g"
+                           match='&lt;a href="\.\.(/@{document.dir.name})/.+\.html(.*)"&gt;'
+                           replace='&lt;a href="YSCT-@{document.dir.name}.html\2"&gt;'
+                           if:set="website.local.files">
+                <fileset dir="@{work.dir}">
+                    <include name="@{html.file}" />
+                </fileset>
+            </replaceregexp>
+
+        </sequential>
+    </macrodef>
+
+</project>

plugins/org.yakindu.sct.doc.user/contexts.xml

@@ -3,26 +3,26 @@
 <contexts>
    <context id="sc_properties_entry_entrykind" title="Entry">
       <description>An entry, possibly with a shallow or deep history, defines which state is to be activated first in a state machine or region.</description>
-      <topic href="help/Part2-User-Guide/30_statechart_language.html#entry" label="Entry"/>
-      <topic href="help/Part2-User-Guide/30_statechart_language.html#shallow-history" label="Shallow History state"/>
-        <topic href="help/Part2-User-Guide/30_statechart_language.html#deep-history" label="Deep History state"/>
+      <topic href="help/user-guide/statechart_language.html#entry" label="Entry"/>
+      <topic href="help/user-guide/statechart_language.html#shallow-history" label="Shallow History state"/>
+        <topic href="help/user-guide/statechart_language.html#deep-history" label="Deep History state"/>
    </context>
    <context id="sc_properties_state_expression" title="State">
       <description>States are central elements of a state machine.</description>
-      <topic href="help/Part2-User-Guide/30_statechart_language.html#state" label="State"/>
+      <topic href="help/user-guide/statechart_language.html#state" label="State"/>
    </context>
    <context id="sc_properties_statechart_expression" title="Expressions">
       <description>Expressions are used to declare events, variables etc. and to define behavior.</description>
-      <topic href="help/Part2-User-Guide/30_statechart_language.html#expressions" label="Expression reference"/>
+      <topic href="help/user-guide/statechart_language.html#expressions" label="Expression reference"/>
    </context>
    <context id="sc_properties_transition_expression" title="Transition">
       <description>A transition is the transfer of one state to another. Transitions are diagrammed as arrows. They can carry events and actions, but don't need to.</description>
-      <topic href="help/Part2-User-Guide/30_statechart_language.html#transition" label="Transition reference"/>
+      <topic href="help/user-guide/statechart_language.html#transition" label="Transition reference"/>
    </context>
    <context id="sgen_feature" title="Genmodel Features">
-      <topic href="help/Part2-User-Guide/60_generating_code.html" label="Generating state machine code"/>
+      <topic href="help/user-guide/generating_code.html" label="Generating state machine code"/>
    </context>
    <context id="stext_keyword">
-      <topic href="help/Part2-User-Guide/30_statechart_language.html" label="YAKINDU Statechart Tools User Guide"/>
+      <topic href="help/user-guide/statechart_language.html" label="YAKINDU Statechart Tools User Guide"/>
    </context>
 </contexts>

plugins/org.yakindu.sct.doc.user/css/custom.css

@@ -1,300 +0,0 @@
-@CHARSET "ISO-8859-1";
-
-#seperator {
-	height: 60px;
-	overflow: hidden;
-	margin-bottom: 25px;
-	background-image: -webkit-gradient(linear, 0 100%, 100% 0, color-stop(0.25, rgba(255, 255,
-		255, 0.15) ), color-stop(0.25, transparent),
-		color-stop(0.5, transparent),
-		color-stop(0.5, rgba(255, 255, 255, 0.15) ),
-		color-stop(0.75, rgba(255, 255, 255, 0.15) ),
-		color-stop(0.75, transparent), to(transparent) );
-	background-image: -webkit-linear-gradient(135deg, rgba(255, 255, 255, 0.15)
-		25%, transparent 25%, transparent 50%, rgba(255, 255, 255, 0.15) 50%,
-		rgba(255, 255, 255, 0.15) 75%, transparent 75%, transparent );
-	background-image: -moz-linear-gradient(135deg, rgba(255, 255, 255, 0.15)
-		25%, transparent 25%, transparent 50%, rgba(255, 255, 255, 0.15) 50%,
-		rgba(255, 255, 255, 0.15) 75%, transparent 75%, transparent );
-	background-image: -o-linear-gradient(135deg, rgba(255, 255, 255, 0.15)
-		25%, transparent 25%, transparent 50%, rgba(255, 255, 255, 0.15) 50%,
-		rgba(255, 255, 255, 0.15) 75%, transparent 75%, transparent );
-	background-image: linear-gradient(135deg, rgba(255, 255, 255, 0.15) 25%,
-		transparent 25%, transparent 50%, rgba(255, 255, 255, 0.15) 50%,
-		rgba(255, 255, 255, 0.15) 75%, transparent 75%, transparent );
-	-webkit-background-size: 60px 60px;
-	-moz-background-size: 60px 60px;
-	-o-background-size: 60px 60px;
-	background-size: 60px 60px;
-	z-index: 1000;
-}
-
-.modal {
-	position: fixed;
-	left: 50%; 
-	right : 50%; 
-	width : 1000px;
-	margin: -420px 0 0 -500px;
-}
-
-.modal-body {
-	max-height: 730px;
-}
-
-.twitter-follow-button {
-	padding: 5px;
-}
-
-.
-.green {
-	background-color: rgba(126, 181, 25, 0.45);
-}
-
-.blue {
-	background-color: rgba(7, 46, 99, 0.45);
-}
-
-.orange {
-	background-color: rgba(247, 169, 15, 0.45);
-}
-
-.white {
-	background-color: white;
-}
-
-.shadowed {
-	-webkit-box-shadow: 0 3px 7px rgba(0, 0, 0, 0.3);
-	-moz-box-shadow: 0 3px 7px rgba(0, 0, 0, 0.3);
-	box-shadow: 0 3px 7px rgba(0, 0, 0, 0.3);
-}
-
-.wrapping {
-	padding: 20px;
-	-webkit-border-radius: 6px;
-	-moz-border-radius: 6px;
-	border-radius: 6px;
-}
-
-.small {
-	width: 270px;
-	height: 180px;
-}
-
-#bgimg {
-	background: #bee2fc
-		url(http://www.yakindu.org/wp-content/themes/yakindu/layout/images/Hintergrund-oben.jpg)
-		top center no-repeat;
-}
-
-#screencast {
-	height: 320px;
-	width: 440px;
-	background-image: url("http://www.itemis.com/binary.ashx?id=43434");
-	background-position: center;
-	z-index: 8;
-}
-
-#glass-effect {
-	padding-top: 40px;
-	background-image: url(img/pattern1.jpg) top left;
-	background-color: rgba(238, 238, 238, 0.6);
-}
-
-.screencast_overlay:hover {
-	opacity: 1;
-	filter: alpha(opacity =   100);
-}
-
-.screencast_overlay {
-	height: 100%;
-	width: 100%;
-	opacity: 0.4;
-	filter: alpha(opacity =   40);
-	background: url("../img/player_play.png") center center no-repeat;
-	z-index: 10;
-}
-
-body {
-	margin: 2%;
-}
-
-
-img.standard-image {
-    max-width: 61.8%;
-    min-width: 38.2%;
-    height: auto;
-    text-align: center;
-    display: block;
-    margin-left: auto;
-    margin-right: auto;
-
-    box-shadow: 10px 10px 20px #888888;
-    border-radius: 4px;
-    margin-top: 1.5ex;
-    margin-bottom: 2.5ex;
-}
-
-img.tiny {
-    width:14.6%;
-    min-width:14.6%;
-}
-
-img.small {
-    width:38.2%;
-}
-
-img.large {
-    width:61.8%;
-}
-
-img.full {
-    width:100%;
-    max-width:100%;
-}
-
-img.shadowless {
-    box-shadow: none;
-    margin-bottom: 0px;
-}
-
-img.inlinemediaobject {
-    display: inline;
-    height: 1.1em;
-    width: auto; /* For keeping aspect ratio */
-    min-width: 0; /* Overrides min-width from img, as 'initial' does not work as intended */
-}
-
-
-
-/* Tables */
-
-.informaltable td {
-	border-color: #000;
-	border-radius: 0%;
-	border-style: solid;
-	border-width: 1px;
-	padding: 1ex;
-	vertical-align: top;
-}
-
-
-
-/* The class "scedit" is used in tables describing working with the statechart editor.
-   These tables typically consist of two columns with a textual description in the
-   left column and a screenshot on the right. */
-
-table.scedit {
-	width: auto;
-	border-collapse: collapse;
-}
-
-tr.scedit {
-	vertical-align: top;
-}
-
-table.scedit td {
-	border-color: #000;
-	border-radius: 0%;
-	border-style: solid;
-	border-width: 0px;
-	padding-bottom: 1ex;
-	vertical-align: top;
-}
-
-table.scedit img {
-	max-width: 100%;
-    margin-left: 0px;
-    margin-right: 0px;
-    box-shadow: 4px 4px 2px #bbb;
-}
-
-.application, .eclipse-view, .guibutton, .guimenuitem, .sct-state, .sct-variable, .sct-event, .sct-trigger {
-	font-style: italic;
-}
-
-.application-ysct {
-	font-weight: bold;
-	color: #555566;
-}
-
-
-.note {
-	padding-left: 1em;
-    border-style: solid;
-    border-width: 1px;
-    border-color: black;
-    background: #d0d0d0;
-    font-size: 50%;
-    line-height: 100%;
-    margin-top: 0ex;
-    margin-left: 0ex;
-    margin-right: 0ex;
-    margin-bottom: 2ex;
-}
-
-.warning {
-	padding-left: 1em;
-    border-style: solid;
-    border-width: 1px;
-    border-color: black;
-    background: #ffd0d0;
-    margin-top: 0ex;
-    margin-left: 0ex;
-    margin-right: 0ex;
-    margin-bottom: 2ex;
-}
-
-.note h3 {
-    font-size: 60%;
-	line-height: 100%;
-}
-
-
-
-/* Settings for "synopsys" sub-elements: */
-pre.synopsis code.literal {
-    font-weight: bold;
-    font-style: normal;
-}
-
-pre.synopsis code.varname {
-    font-weight: normal;
-    font-style: italic;
-}
-
-pre {
-    line-height: 100%;
-}
-
-
-
-div.example {
-	padding-left: 2%;
-	padding-right: 2%;
-	padding-top: 2%;
-	padding-bottom: 1%;
-	border-style: solid;
-	border-width: 1px;
-}
-
-
-.to-be-written {
-	background-color: yellow;
-}
-
-
-body {counter-reset: h1}
-h1 {counter-reset: h2}
-h2 {counter-reset: h3}
-h3 {counter-reset: h4}
-h4 {counter-reset: h5}
-h5 {counter-reset: h6}
-
-h1:before {counter-increment: h1; content: counter(h1) ". "}
-h2:before {counter-increment: h2; content: counter(h1) "." counter(h2) ". "}
-h3:before {counter-increment: h3; content: counter(h1) "." counter(h2) "." counter(h3) ". "}
-h4:before {counter-increment: h4; content: counter(h1) "." counter(h2) "." counter(h3) "." counter(h4) ". "}
-h5:before {counter-increment: h5; content: counter(h1) "." counter(h2) "." counter(h3) "." counter(h4) "." counter(h5) ". "}
-h6:before {counter-increment: h6; content: counter(h1) "." counter(h2) "." counter(h3) "." counter(h4) "." counter(h5) "." counter(h6) ". "}
-
-h1.nocount:before h2.nocount:before, h3.nocount:before, h4.nocount:before, h5.nocount:before, h6.nocount:before { content: ""; counter-increment: none } 

plugins/org.yakindu.sct.doc.user/css/local.css

@@ -0,0 +1,5 @@
+@CHARSET "ISO-8859-1";
+
+body {
+	margin: 2%;
+}

plugins/org.yakindu.sct.doc.user/css/style.css

@@ -1,2 +1,3 @@
 @import url("../css/bootstrap.css");
-@import url("../css/custom.css");
+@import url("../css/local.css");
+@import url("../css/ysct.css");

plugins/org.yakindu.sct.doc.user/css/ysct.css

@@ -0,0 +1,81 @@
+/* Images */
+img.standard-image {
+    max-width: 61.8%;
+    min-width: 38.2%;
+    height: auto;
+    text-align: center;
+    display: block;
+    margin-left: auto;
+    margin-right: auto;
+    box-shadow: 10px 10px 20px #888888;
+    -webkit-box-shadow: 10px 10px 20px #888888;
+    -moz-box-shadow: 10px 10px 20px #888888;
+    border-radius: 4px;
+    margin-top: 1.5ex;
+    margin-bottom: 2.5ex;
+}
+img.small {
+    width:38.2%;
+}
+img.full {
+    width:100%;
+    max-width:100%;
+}
+img.shadowless {
+    box-shadow: none;
+    margin-bottom: 0px;
+}
+img.inlinemediaobject {
+    line-height: 1;
+    vertical-align: middle;
+}
+
+/* Tables */
+/* The class "scedit" is used in tables describing working with the statechart editor.
+   These tables typically consist of two columns with a textual description in the
+   left column and a screenshot on the right. */
+table.scedit {
+	width: auto;
+	border-collapse: collapse;
+}
+tr.scedit {
+	vertical-align: top
+}
+table.scedit td {
+	border-color: #000;
+	border-radius: 0%;
+	border-style: solid;
+	border-width: 0px;
+	padding-bottom: 1ex;
+	vertical-align: top; 
+}
+table.scedit img {
+	max-width: 100%;
+    margin-left: 0px;
+    margin-right: 0px;
+    box-shadow: 4px 4px 2px #bbb;
+}
+
+/* Counter */
+body {counter-reset: h1}
+h1 {counter-reset: h2}
+h2 {counter-reset: h3}
+h3 {counter-reset: h4}
+h4 {counter-reset: h5}
+h5 {counter-reset: h6}
+
+.body-container h1:before {counter-increment: h1; content: counter(h1) ". "}
+.body-container h2:before {counter-increment: h2; content: counter(h1) "." counter(h2) ". "}
+.body-container h3:before {counter-increment: h3; content: counter(h1) "." counter(h2) "." counter(h3) ". "}
+.body-container h4:before {counter-increment: h4; content: counter(h1) "." counter(h2) "." counter(h3) "." counter(h4) ". "}
+.body-container h5:before {counter-increment: h5; content: counter(h1) "." counter(h2) "." counter(h3) "." counter(h4) "." counter(h5) ". "}
+.body-container h6:before {counter-increment: h6; content: counter(h1) "." counter(h2) "." counter(h3) "." counter(h4) "." counter(h5) "." counter(h6) ". "}
+
+h1.nocount:before h2.nocount:before, h3.nocount:before, h4.nocount:before, h5.nocount:before, h6.nocount:before { content: ""; counter-increment: none }
+
+
+@media (max-width: 767px) {
+    code {
+        word-wrap: break-word;
+    }
+}

plugins/org.yakindu.sct.doc.user/plugin.xml

@@ -4,13 +4,17 @@
 
     <extension point="org.eclipse.help.toc">
         <toc file="toc.xml" primary="true" />
-        <toc file="help/Part1-Installation-Guide/00_installation-toc.xml" primary="false"/>
-        <toc file="help/Part2-User-Guide/20_tutorial-toc.xml" primary="false" />
-        <toc file="help/Part2-User-Guide/50_simulating_statecharts-toc.xml" primary="false" />
-        <toc file="help/Part2-User-Guide/30_statechart_language-toc.xml" primary="false" />
-        <toc file="help/Part2-User-Guide/60_generating_code-toc.xml" primary="false" />
-        <toc file="help/Part2-User-Guide/10_overview-toc.xml" primary="false" />
-        <toc file="help/Part2-User-Guide/40_editing_statecharts-toc.xml" primary="false" />
+
+        <!-- List all files constituting the documentation here: -->
+        <toc file="help/tutorials/tutorials-toc.xml" primary="false"/>
+        <toc file="help/user-guide/overview-toc.xml" primary="false"/>
+        <toc file="help/user-guide/editing_statecharts-toc.xml" primary="false"/>
+        <toc file="help/user-guide/simulating_statecharts-toc.xml" primary="false"/>
+        <toc file="help/user-guide/advanced_simulation-toc.xml" primary="false"/>
+        <toc file="help/user-guide/c-domain-toc.xml" primary="false"/>
+        <toc file="help/user-guide/statechart_language-toc.xml" primary="false"/>
+        <toc file="help/user-guide/generating_code-toc.xml" primary="false"/>
+        <toc file="help/installation/installation-toc.xml" primary="false"/>
     </extension>
 
     <extension point="org.eclipse.help.contexts">

plugins/org.yakindu.sct.doc.user/src/Part1-Installation-Guide/00_installation.textile

@@ -48,7 +48,7 @@ h3(#unpacking-the-downloaded-file). Unpacking the downloaded file
 
 Unpack the software distribution file. Use the file explorer to open the directory you downloaded the software distribution file to, right-click on the latter, and select _Extract All..._ in the context menu.
 
-!(standard-image)images/windows7_install_010_eclipse_extract_1.png(Unpacking the downloaded file on Windows [1])!
+!(standard-image)images/inst_windows7_010_eclipse_extract_1.png(Unpacking the downloaded file on Windows [1])!
 
 p=. Unpacking the downloaded file on Windows [1]
 
@@ -56,7 +56,7 @@ Choose a directory for YAKINDU Statechart Tools (YAKINDU SCT). The example below
 
 Depending on your permissions, you might not be able to create a directory and install software under _C:\Program Files_. In this case, please choose another installation directory at a location you are allowed to write to.
 
-!(standard-image)images/windows7_install_020_eclipse_extract_2.png(Unpacking the downloaded file on Windows [2])!
+!(standard-image)images/inst_windows7_020_eclipse_extract_2.png(Unpacking the downloaded file on Windows [2])!
 
 p=. Unpacking the downloaded file on Windows [2]
 
@@ -64,13 +64,13 @@ Click on _Extract_ to start the extraction process. With Window's built-in unpac
 
 After unpacking, you will find a folder _yakindu-sct_ in your installation directory, i. e. _C:\Program Files\YAKINDU\yakindu-sct_ in our example, as shown in the image below:
 
-!(standard-image)images/windows7_install_030_eclipse_folder.png(The extracted "yakindu-sct" folder)!
+!(standard-image)images/inst_windows7_030_eclipse_folder.png(The extracted "yakindu-sct" folder)!
 
 p=. The extracted _yakindu-sct_ folder
 
 The contents of the _yakindu-sct_ folder looks like this:
 
-!(standard-image)images/windows7_install_040_eclipse_contents.png(Contents of the extracted "yakindu-sct" folder)!
+!(standard-image)images/inst_windows7_040_eclipse_contents.png(Contents of the extracted "yakindu-sct" folder)!
 
 p=. Contents of the extracted _yakindu-sct_ folder
 
@@ -84,7 +84,7 @@ To do so, please double-click (or single-click, depending on your Windows settin
 
 Depending on the Windows settings and your permissions, you might get the following security warning, indicating that you downloaded the application from a potentially unsecure source:
 
-!(standard-image)images/windows7_install_045_security_warning.png(Windows security warning)!
+!(standard-image)images/inst_windows7_045_security_warning.png(Windows security warning)!
 
 p=. Windows security warning
 
@@ -92,7 +92,7 @@ Uncheck the _Always ask before opening this file_ option. Click _Run_ to continu
 
 While YAKINDU Statechart Tools is starting up, it is showing a splash screen:
 
-!(standard-image)images/windows7_install_050_eclipse_splash.png(YAKINDU Statechart Tools starting up and showing a splash screen)!
+!(standard-image)images/inst_windows7_050_eclipse_splash.png(YAKINDU Statechart Tools starting up and showing a splash screen)!
 
 p=. YAKINDU Statechart Tools starting up and showing a splash screen
 
@@ -100,7 +100,7 @@ The software needs a _workspace_ directory where it stores its so-called project
 
 In the example below, we chose the _C:\Users\joedoe\workspace_ directory as our workspace. We also checked the _"Use this as the default and do not ask again"_ option. This is sensible, because on subsequent startups, YAKINDU Statechart Tools won't ask for a workspace directory again. Instead it will always use the one we chose once and forever. (You can still change the workspace later via _File → Switch Workspace_ in the main menu.)
 
-!(standard-image)images/windows7_install_060_eclipse_workspace_dialog.png(Selecting a workspace)!
+!(standard-image)images/inst_windows7_060_eclipse_workspace_dialog.png(Selecting a workspace)!
 
 p=. Selecting a workspace
 
@@ -108,19 +108,19 @@ Click on the _OK_ button to proceed.
 
 On the first start, YAKINDU Statechart Tools presents a _Welcome_ window:
 
-!(standard-image)images/windows7_install_070_eclipse_welcome.png(YAKINDU Statechart Tools presenting the "Welcome" window)!
+!(standard-image)images/inst_windows7_070_eclipse_welcome.png(YAKINDU Statechart Tools presenting the "Welcome" window)!
 
 p=. YAKINDU Statechart Tools presenting the "Welcome" window
 
 You can browse the material shown here, if you want. When you are done, please close the _Welcome_ tab or click on _Workbench_ at the upper right. Both actions are leading to the workbench:
 
-!(standard-image)images/windows7_install_080_eclipse_workbench.png(The YAKINDU Statechart Tools workbench)!
+!(standard-image)images/inst_windows7_080_eclipse_workbench.png(The YAKINDU Statechart Tools workbench)!
 
 p=. The YAKINDU Statechart Tools workbench
 
 This is your working environment now. Congratulations, you have just installed YAKINDU Statechart Tools with Eclipse!
 
-You can "proceed":../Part2-User-Guide/20_tutorial.html#oss_comprehensive-tutorial now to create your first YAKINDU Statecharts Tools project.
+You can "proceed":../tutorials/tutorials.html now to create your first YAKINDU Statecharts Tools project.
 
 h2(#installing-on-macosx). Installing on Mac OS X
 
@@ -134,7 +134,7 @@ Unpacking will provide you with the _YAKINDU SCT_ application bundle.
 
 Move the unpacked application bundle to your _Applications_ folder. Alternatively, you can also move it somewhere else as you see fit. The screenshot below shows the _YAKINDU SCT_ application bundle having been moved to _Applications_.
 
-!(standard-image shadowless)images/macosx_install_010_applications.png(The YAKINDU Statecharts Tools application in the "Applications" directory)!
+!(standard-image shadowless)images/inst_macosx_010_applications.png(The YAKINDU Statecharts Tools application in the "Applications" directory)!
 
 p=. The YAKINDU Statecharts Tools application in the "Applications" directory
 
@@ -148,7 +148,7 @@ To do so, please double-click on the _YAKINDU_ symbol shown in the sample screen
 
 Upon the first start, Mac OS X will verify the application and show you the following security warning, indicating that you did not download the application from Apple's App Store, but from a potentially unsecure source instead:
 
-!(standard-image shadowless)images/macosx_install_020_security_warning.png(Mac OS X warning)!
+!(standard-image shadowless)images/inst_macosx_020_security_warning.png(Mac OS X warning)!
 
 p=. Mac OS X warning
 
@@ -156,7 +156,7 @@ Click _Open_ to continue starting the application. Subsequently starting YAKINDU
 
 While YAKINDU Statechart Tools is starting up, it is showing a splash screen:
 
-!(standard-image shadowless)images/macosx_install_050_eclipse_splash.png(YAKINDU Statechart Tools starting up and showing a splash screen)!
+!(standard-image shadowless)images/inst_macosx_050_eclipse_splash.png(YAKINDU Statechart Tools starting up and showing a splash screen)!
 
 p=. YAKINDU Statechart Tools starting up and showing a splash screen
 
@@ -164,7 +164,7 @@ The software needs a _workspace_ directory where it stores its so-called project
 
 In the example below, we chose the _/Users/joedoe/workspace_ directory as our workspace. We also checked the _"Use this as the default and do not ask again"_ option. This is sensible, because on subsequent startups, YAKINDU Statechart Tools won't ask for a workspace directory again. Instead it will always use the one we chose once and forever. (You can still change the workspace later via _File → Switch Workspace_ in the main menu.)
 
-!(standard-image shadowless)images/macosx_install_060_eclipse_workspace_dialog.png(Selecting a workspace)!
+!(standard-image shadowless)images/inst_macosx_060_eclipse_workspace_dialog.png(Selecting a workspace)!
 
 p=. Selecting a workspace
 
@@ -172,19 +172,19 @@ Click on the _OK_ button to proceed.
 
 On the first start, YAKINDU Statechart Tools presents a _Welcome_ window:
 
-!(standard-image shadowless)images/macosx_install_070_eclipse_welcome.png(YAKINDU Statechart Tools presenting the "Welcome" window)!
+!(standard-image shadowless)images/inst_macosx_070_eclipse_welcome.png(YAKINDU Statechart Tools presenting the "Welcome" window)!
 
 p=. YAKINDU Statechart Tools presenting the "Welcome" window
 
 You can browse the material shown here, if you want. When you are done, please close the _Welcome_ tab or click on _Workbench_ at the upper right. Both actions are leading to the workbench:
 
-!(standard-image shadowless)images/macosx_install_080_eclipse_workbench.png(The YAKINDU Statechart Tools workbench)!
+!(standard-image shadowless)images/inst_macosx_080_eclipse_workbench.png(The YAKINDU Statechart Tools workbench)!
 
 p=. The YAKINDU Statechart Tools workbench
 
 This is your working environment now. Congratulations, you have just installed YAKINDU Statechart Tools with Eclipse!
 
-You can "proceed":../Part2-User-Guide/20_tutorial.html#oss_comprehensive-tutorial now to create your first YAKINDU Statecharts Tools project.
+You can "proceed":../tutorials/tutorials.html now to create your first YAKINDU Statecharts Tools project.
 
 h2(#installing-on-linux). Installing on Linux
 
@@ -206,13 +206,13 @@ bc. unzip /download/sct-linux.gtk.x86_64.zip
 
 This will create a folder _yakindu-sct_ in your installation directory, i. e. _/my/software/yakindu-sct_ in our example, as shown in the image below:
 
-!(standard-image)images/linux_install_010_eclipse_folder.png(The extracted "yakindu-sct" folder)!
+!(standard-image)images/inst_linux_010_eclipse_folder.png(The extracted "yakindu-sct" folder)!
 
 p=. The extracted "yakindu-sct" folder
 
 The contents of the _yakindu-sct_ folder looks like this:
 
-!(standard-image)images/linux_install_020_eclipse_contents.png(Contents of the extracted "yakindu-sct" folder)!
+!(standard-image)images/inst_linux_020_eclipse_contents.png(Contents of the extracted "yakindu-sct" folder)!
 
 p=. Contents of the extracted "yakindu-sct" folder
 
@@ -238,7 +238,7 @@ From a file browser, you can start YAKINDU Statechart Tools by clicking on the _
 
 While YAKINDU Statechart Tools is starting up, it is showing a splash screen:
 
-!(standard-image)images/linux_install_030_eclipse_splash.png(YAKINDU Statechart Tools starting up and showing a splash screen)!
+!(standard-image)images/inst_linux_030_eclipse_splash.png(YAKINDU Statechart Tools starting up and showing a splash screen)!
 
 p=. YAKINDU Statechart Tools starting up and showing a splash screen
 
@@ -246,7 +246,7 @@ The software needs a _workspace_ directory where it stores its so-called project
 
 In the example below, we chose the _/my/workspace_ directory as our workspace. We also checked the _"Use this as the default and do not ask again"_ option. This is sensible, because on subsequent startups, YAKINDU Statechart Tools won't ask for a workspace directory again. Instead it will always use the one we chose once and forever. (You can still change the workspace later via _File → Switch Workspace_ in the main menu.)
 
-!(standard-image)images/linux_install_040_eclipse_workspace_dialog.png(Selecting a workspace)!
+!(standard-image)images/inst_linux_040_eclipse_workspace_dialog.png(Selecting a workspace)!
 
 p=. Selecting a workspace
 
@@ -254,19 +254,19 @@ Click on the _OK_ button to proceed.
 
 On the first start, YAKINDU Statechart Tools presents a _Welcome_ window:
 
-!(standard-image)images/linux_install_050_eclipse_welcome.png(YAKINDU Statechart Tools presenting the "Welcome" window)!
+!(standard-image)images/inst_linux_050_eclipse_welcome.png(YAKINDU Statechart Tools presenting the "Welcome" window)!
 
 p=. YAKINDU Statechart Tools presenting the "Welcome" window
 
 You can browse the material shown here, if you want. When you are done, please close the _Welcome_ tab or click on _Workbench_ at the upper right. Both actions are leading to the workbench:
 
-!(standard-image)images/linux_install_060_eclipse_workbench.png(The YAKINDU Statechart Tools workbench)!
+!(standard-image)images/inst_linux_060_eclipse_workbench.png(The YAKINDU Statechart Tools workbench)!
 
 p=. The YAKINDU Statechart Tools workbench
 
 This is your working environment now. Congratulations, you have just started YAKINDU Statechart Tools!
 
-You can "proceed":../Part2-User-Guide/20_tutorial.html#oss_comprehensive-tutorial now to create your first YAKINDU Statecharts Tools project.
+You can "proceed":../tutorials/tutorials.html now to create your first YAKINDU Statecharts Tools project.
 
 h2(#installing-to-an-existing-eclipse-instance). Installing to an existing Eclipse instance
 
@@ -274,13 +274,13 @@ This chapter describes the steps that are needed to install YAKINDU Statechart T
 
 In the the _Help_ menu, select the _Install New Software_ menu item:
 
-!(standard-image)images/eclipse_install_010_eclipse_menu_install_new_software.png(Selecting "Help → Install New Software" in the main menu)!
+!(standard-image)images/inst_eclipse_010_eclipse_menu_install_new_software.png(Selecting "Help → Install New Software" in the main menu)!
 
 p=. Selecting "Help → Install New Software" in the main menu
 
 The _Install_ wizard opens:
 
-!(standard-image)images/eclipse_install_020_eclipse_install_wizard.png(The "Install" wizard)!
+!(standard-image)images/inst_eclipse_020_eclipse_install_wizard.png(The "Install" wizard)!
 
 p=. The "Install" wizard
 
@@ -299,7 +299,7 @@ p. Please note that YAKINDU Statechart Tools might take some time to catch up wi
 
 Enter some text into the _Name_ field. This text is abitrary in principle, but you should choose something that makes it easier for you to identify this particular update repository among other update repositories. In the example below, the repository's name is @YAKINDU Statechart Tools (Luna)@. It describes which piece of software the repository provides (YAKINDU Statechart Tools) and which Eclipse release that software is compatible with (Luna, i. e. Eclipse 4.4).
 
-!(standard-image)images/eclipse_install_030_eclipse_add_repository.png(Adding a software repository)!
+!(standard-image)images/inst_eclipse_030_eclipse_add_repository.png(Adding a software repository)!
 
 p=. Adding a software repository
 
@@ -307,7 +307,7 @@ After entering name and location of the update repository, click _OK_.
 
 Eclipse establishes a network connection to the update repository, asks it for available software items and shows them in the install wizard:
 
-!(standard-image)images/eclipse_install_040_eclipse_software_items.png(Selecting YAKINDU Statechart Tools software items)!
+!(standard-image)images/inst_eclipse_040_eclipse_software_items.png(Selecting YAKINDU Statechart Tools software items)!
 
 p=. Selecting YAKINDU Statechart Tools software items
 
@@ -317,7 +317,7 @@ Click _Next >_.
 
 Eclipse tries to integrate the new software with the software that is already installed. If it detects any mismatches between requirements and provisions, Eclipse will try to find a solution in order to mitigate this problem. The screenshot below shows such a case:
 
-!(standard-image)images/eclipse_install_050_eclipse_trouble.png(Install remediation page)!
+!(standard-image)images/inst_eclipse_050_eclipse_trouble.png(Install remediation page)!
 
 p=. Install remediation page
 
@@ -325,7 +325,7 @@ Select the most appropriate solution, then click _Next >_.
 
 The wizard shows the software to be installed and gives you the opportunity to review the changes:
 
-!(standard-image)images/eclipse_install_060_eclipse_review.png(Reviewing the items to be installed)!
+!(standard-image)images/inst_eclipse_060_eclipse_review.png(Reviewing the items to be installed)!
 
 p=. Reviewing the items to be installed
 
@@ -333,7 +333,7 @@ Click _Next >_.
 
 The wizard asks you to review and accept the terms of the new software's license agreements.
 
-!(standard-image)images/eclipse_install_070_eclipse_licenses.png(Accepting the new software's license agreements)!
+!(standard-image)images/inst_eclipse_070_eclipse_licenses.png(Accepting the new software's license agreements)!
 
 p=. Accepting the new software's license agreements
 
@@ -341,19 +341,19 @@ Select the radio button labelled _I accept the terms of the license agreements_
 
 Eclipse starts to download the software and installs it on your computer. This may take some time.
 
-!(standard-image)images/eclipse_install_080_eclipse_installation.png(Installing software in progress ...)!
+!(standard-image)images/inst_eclipse_080_eclipse_installation.png(Installing software in progress ...)!
 
 p=. Installing software in progress ...
 
 If the installation was completed successfully, Eclipse needs a restart in order to have the changes take effect. A dialog asks whether you want to restart Eclipse right now or later:
 
-!(standard-image)images/eclipse_install_090_eclipse_restart.png(Restarting Eclipse after software installation)!
+!(standard-image)images/inst_eclipse_090_eclipse_restart.png(Restarting Eclipse after software installation)!
 
 p=. Restarting Eclipse after software installation
 
 After the restart, Eclipse displays its _Welcome_ window, now also featuring YAKINDU Statechart Tools:
 
-!(standard-image)images/eclipse_install_100_eclipse_sct_help.png(Eclipse presenting the "Welcome" window)!
+!(standard-image)images/inst_eclipse_100_eclipse_sct_help.png(Eclipse presenting the "Welcome" window)!
 
 p=. Eclipse presenting the "Welcome" window
 
@@ -361,7 +361,7 @@ h2(#updating-yakindu-statechart-tools). Updating YAKINDU Statechart Tools
 
 To check whether a new YAKINDU Statechart Tools release is available and to install it, please select the _Help → Check for Updates_ menu item.
 
-!(standard-image)images/eclipse_update_010_eclipse_menu_check_for_updates.png(Selecting "Help → Check for Updates" in the main menu)!
+!(standard-image)images/inst_eclipse_update_010_eclipse_menu_check_for_updates.png(Selecting "Help → Check for Updates" in the main menu)!
 
 p=. Selecting "Help → Check for Updates" in the main menu
 
@@ -373,7 +373,7 @@ Select the _Window → Preferences_ menu item. The _Preferences_ dialog opens.
 
 Go to the _Install/Update → Automatic Updates_ section. Here you can configure whether and when Eclipse should check for updates and what to do when it finds any.
 
-!(standard-image)images/eclipse_update_020_eclipse_automatic_updates.png(Configuring automatic update)!
+!(standard-image)images/inst_eclipse_update_020_eclipse_automatic_updates.png(Configuring automatic update)!
 
 p=. Configuring automatic update
 
@@ -390,7 +390,7 @@ In order to check whether you are affected, proceed as follows:
 
 If the list of installed JREs is empty, you are affected by the problem and will have to manually add a JRE definition. Click on the _Add…_ button and follow the _Add JRE_ wizard. The Eclipse documentation explains in more detail how to "add a new JRE definition":http://help.eclipse.org/neon/index.jsp?topic=%252Forg.eclipse.jdt.doc.user%252Ftasks%252Ftask-add_new_jre.htm to your workspace.
 
-!(standard-image)images/installed_jres_010.png(Installed JREs)!
+!(standard-image)images/inst_installed_jres_010.png(Installed JREs)!
 
 p=. Installed JREs