<?xml version="1.0"?>
<api>
  <query-continue>
    <allpages gapcontinue="The_LSC_Compiler" />
  </query-continue>
  <query>
    <pages>
      <page pageid="75" ns="0" title="S2A Configuration">
        <revisions>
          <rev contentformat="text/x-wiki" contentmodel="wikitext" xml:space="preserve">Basically, the examples provided are configured with relative paths and should work well in your environment. However this is a good opportunity to introduce some parts of the configuration that you can control.
==S2A builder properties==

Right-click the project you work on and choose Properties-&amp;gt;PlayGo-&gt;S2A Builder:

[[Image:S2a.properties.png]]

&lt;br&gt;
As shown in the screenshot above, there are four tabs, in which you can configure properties related to S2A Builder:

#S2A Compilation
##Source interactions on build path: Add and remove model files that you want to compile with S2A. For the models you add, you may choose which LSCs should be compiled by S2A. In other words, which LSCs will participate in the system execution.
##Target Folder:  Here you specify the directory in which the generated aspects will be located.
##Clear Automatically: If on, cleans the aspects directory before generating new aspects.
##Polymorphism: Enable or disable polymorphism.

#Imports
##Add and remove Java packages that will be imported in the generated aspects.
##Specify the output package name: The package of the generated aspects.
#Tracing
##Generate trace: Check if you want to generate a trace/log at runtime.
##Append: Check if you want to append the log to the existing log (rather then deleting and adding new content).
##Output file: The path and name of the generated trace file. By default, the trace file is generated in the root directory of your project.
##LSCs to trace: Check those LSCs you would like to trace. Check or uncheck the model root to apply your selection on all LSCs.
#General: Currently used only for specifying the log4j configuration location.

&lt;big&gt;&lt;/big&gt;

==S2A play-out properties==

Right click your project and choose Properties-&gt;PlayGo-&gt;Play-Out

[[Image:S2a.playout.properties.jpeg]]

&lt;br&gt;Here you can choose a play-out strategy from a set of [[PlayGo_Feature_List#Na.C3.AFve_play-out | predefined strategies]].</rev>
        </revisions>
      </page>
      <page pageid="7" ns="0" title="Startup PlayGo">
        <revisions>
          <rev contentformat="text/x-wiki" contentmodel="wikitext" xml:space="preserve">To start PlayGo, go to your &amp;lt;PlayGo&amp;gt; directory and double click the PlayGo.exe file. As it is in Eclipse, PlayGo will ask you for the workspace to start with. Choose the workspace provided with the installation (i.e. &amp;lt;PlayGo&amp;gt;/workspace/).

The &amp;lt;PlayGo&amp;gt;/workspace/ contains 4 projects:

*ATM – example for ATM System. The ATM GUI side is based on GWT. ATM behavior was modeled by Playing in a set of scenarios. S2A is used for generating aspects, which are used to monitor and run the system (Play-Out).
*GWTMemoryGame – Another example system. The Memory Game GUI side is based on GWT. Its behavior was modeled by Playing in a set of scenarios. S2A is used for generating aspects, which are used to monitor and run the system (Play-Out).
*il.ac.wis.cs.common – a library which contains few examples for creating LSC models by coding in Java.
*il.ac.wis.cs.playgo.guitoolkit – a platform library used by the ATM and GWTMemoryGame. This is integral part of PlayGo and in the future will be provided as a jar file only.

We will refer to these projects in the following chapters.

Once PlayGo is open, note that the PlayGo perspective is selected. It is recommended to use this perspective, as it provides some shortcuts.

[[Image:playgo.perspective.JPG]]


[[Configure the Examples]]</rev>
        </revisions>
      </page>
    </pages>
  </query>
</api>