Configure the Examples - Revision history

Smadar at 13:47, 19 August 2010

2010-08-19T13:47:41Z

Smadar at 13:40, 19 August 2010

2010-08-19T13:40:03Z

Smadar at 13:39, 19 August 2010

2010-08-19T13:39:27Z

Smadar at 13:36, 19 August 2010

2010-08-19T13:36:52Z

Smadar at 13:34, 19 August 2010

2010-08-19T13:34:45Z

Smadar at 13:32, 19 August 2010

2010-08-19T13:32:32Z

Smadar at 13:31, 19 August 2010

2010-08-19T13:31:35Z

Smadar at 13:30, 19 August 2010

2010-08-19T13:30:06Z

Smadar at 13:26, 19 August 2010

2010-08-19T13:26:09Z

Smadar: New page: Before you can compile and run the examples, you need to configure them: 1. From Window menu, choose PreferencesGoogleWeb Toolkit. Configure it to point to your \plugins\com...

2010-08-19T13:19:50Z

New page: Before you can compile and run the examples, you need to configure them: 1. From Window menu, choose PreferencesGoogleWeb Toolkit. Configure it to point to your <PlayGo>\plugins\com...

New page

Before you can compile and run the examples, you need to configure them:

1. From Window menu, choose PreferencesGoogleWeb Toolkit. Configure it to point to your <PlayGo>\plugins\com.google.gwt.eclipse.sdkbundle.2.0.0_2.0.0.v200912062003\gwt-2.0.0 directory:

[[Image:gwt.preferences.jpg]]

@@ Line 1: / Line 1: @@
 Before you can compile and run the examples, you need to configure them:
 <span style="font-size: larger"><big>1. </big></span>From Window menu, choose Preferences-&gt;Google-&gt;Web Toolkit. Configure it to point to your &lt;PlayGo&gt;\plugins\com.google.gwt.eclipse.sdkbundle.2.0.0_2.0.0.v200912062003\gwt-2.0.0 directory:
 [[Image:Gwt.preferences.jpg]]
 <br>
 <big>2.</big> From Window menu, choose Preferences-&gt;Google-&gt;App Engine. Configure it to point to your &lt;PlayGo&gt;\plugins\com.google.appengine.eclipse.sdkbundle.1.3.0_1.3.0.v200912141120\appengine-java-sdk-1.3.0 directory:
 [[Image:Gwt.preferences2.jpg]]
 <br>
 <big>3.</big> From Window menu, choose Preferences-&gt;Java-&gt;Build PathClasspath Variables. Edit the PLAYGO_PLUGINS variable to point to your &lt;PlayGo&gt;/plugins/ directory:
 [[Image:Classpath.references.jpg]]
 <br>
 <big>4.</big> Basically the examples provided are configured with relative paths and should work well in your environment, but this is a good opportunity to introduce some parts of the configuration you can control. Right click the GWTMemoryGame project-&gt;Properties-&gt;S2A Builder:
 [[Image:Playgo.s2a.properties.jpg]]
 As shown in the screenshot above, there are 3 tabs in which you can configure properties related to S2A:
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A. S2A Compilation
        i.	Here you can add and remove models which you want to compile with S2A.
 For those models you add, you may choose which LSCs should be compiled by S2A. In other words, for which Interactions S2A will generate aspects.
       ii.	Target Folder: here you specify the directory in which the generated aspects will be located.
@@ Line 35: / Line 35: @@
       iv.	Polymorphism – enable or disable polymorphism.
 B. Imports
        i.	Here you may specify packages that will be imported in the generated aspects.
@@ Line 44: / Line 44: @@
 <big></big>
 <big>5.</big> S2A preferences – Advanced From the Windows menu, select Preferences-&gt;PlayGo-&gt;S2A Builder
 [[Image:Playgo.s2a.properties.advanced.jpg]]
 <br>Here you can choose the strategy you want to activate. Currently the only strategy implemented is the Naive strategy and this is the one being used.

@@ Line 40: / Line 40: @@
       ii.	Output package name – the package of the generated aspects.
-&nbsp;&nbsp;&nbsp;C. General – currently used only for specifying the log4j configuration location.<big>5.</big> S2A preferences – Advanced From the Windows menu, select Preferences-&gt;PlayGo-&gt;S2A Builder
+&nbsp;&nbsp;&nbsp;C. General – currently used only for specifying the log4j configuration location.
 [[Image:Playgo.s2a.properties.advanced.jpg]]
 <br>Here you can choose the strategy you want to activate. Currently the only strategy implemented is the Naive strategy and this is the one being used.

@@ Line 25: / Line 25: @@
 As shown in the screenshot above, there are 3 tabs in which you can configure properties related to S2A:
-A. S2A Compilation
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A. S2A Compilation
        i.	Here you can add and remove models which you want to compile with S2A.
@@ Line 40: / Line 40: @@
       ii.	Output package name – the package of the generated aspects.
-C. General – currently used only for specifying the log4j configuration location.
+&nbsp;&nbsp;&nbsp;C. General – currently used only for specifying the log4j configuration location.<big>5.</big> S2A preferences – Advanced From the Windows menu, select Preferences-&gt;PlayGo-&gt;S2A Builder
-−
 <big>5.</big> S2A preferences – Advanced From the Windows menu, select Preferences-&gt;PlayGo-&gt;S2A Builder
 [[Image:Playgo.s2a.properties.advanced.jpg]]
 <br>Here you can choose the strategy you want to activate. Currently the only strategy implemented is the Naive strategy and this is the one being used.

@@ Line 1: / Line 1: @@
 Before you can compile and run the examples, you need to configure them:
-.	From Window menu, choose Preferences->Google->Web Toolkit. Configure it to point to your <PlayGo>\plugins\com.google.gwt.eclipse.sdkbundle.2.0.0_2.0.0.v200912062003\gwt-2.0.0 directory:
+<span style="font-size: larger"><big>1. </big></span>From Window menu, choose Preferences-&gt;Google-&gt;Web Toolkit. Configure it to point to your &lt;PlayGo&gt;\plugins\com.google.gwt.eclipse.sdkbundle.2.0.0_2.0.0.v200912062003\gwt-2.0.0 directory:
-[[Image:gwt.preferences.jpg]]
+[[Image:Gwt.preferences.jpg]]
-.	From Window menu, choose Preferences->Google->App Engine. Configure it to point to your <PlayGo>\plugins\com.google.appengine.eclipse.sdkbundle.1.3.0_1.3.0.v200912141120\appengine-java-sdk-1.3.0 directory:
+[[Image:Gwt.preferences2.jpg]]
-[[Image:gwt.preferences2.jpg]]
+<br>
-.	From Window menu, choose Preferences->Java->Build PathClasspath Variables. Edit the PLAYGO_PLUGINS variable to point to your <PlayGo>/plugins/ directory:
+<br>
-[[Image:classpath.references.jpg]]
+<big>4.</big> Basically the examples provided are configured with relative paths and should work well in your environment, but this is a good opportunity to introduce some parts of the configuration you can control. Right click the GWTMemoryGame project-&gt;Properties-&gt;S2A Builder:
-.	Basically the examples provided are configured with relative paths and should work well in your environment, but this is a good opportunity to introduce some parts of the configuration you can control.
+A. S2A Compilation
-Right click the GWTMemoryGame project->Properties->S2A Builder:
-[[Image:playgo.s2a.properties.jpg]]
+      i.	Here you can add and remove models which you want to compile with S2A.
-As shown in the screenshot above, there are 3 tabs in which you can configure properties related to S2A:
+For those models you add, you may choose which LSCs should be compiled by S2A. In other words, for which Interactions S2A will generate aspects.
       ii.	Target Folder: here you specify the directory in which the generated aspects will be located.
      iii.	Clear Automatically – if on, cleans the aspects directory before generating new aspects.
       iv.	Polymorphism – enable or disable polymorphism.
 B.	Imports
        i.	Here you may specify packages that will be imported in the generated aspects.
       ii.	Output package name – the package of the generated aspects.
-.	S2A preferences – Advanced
+C. General – currently used only for specifying the log4j configuration location.
-From the Windows menu, select Preferences->PlayGo->S2A Builder
-[[Image:playgo.s2a.properties.advanced.jpg]]
+<big>5.</big> S2A preferences – Advanced From the Windows menu, select Preferences-&gt;PlayGo-&gt;S2A Builder
-Here you can choose the strategy you want to activate. Currently the only strategy implemented is the Naive strategy and this is the one being used.
+<br>Here you can choose the strategy you want to activate. Currently the only strategy implemented is the Naive strategy and this is the one being used.

@@ Line 27: / Line 27: @@
 A.	S2A Compilation
        i.	Here you can add and remove models which you want to compile with S2A.
 For those models you add, you may choose which LSCs should be compiled by S2A.
 In other words, for which Interactions S2A will generate aspects.
       ii.	Target Folder: here you specify the directory in which the generated aspects will be located.
@@ Line 37: / Line 37: @@
       ii.	Output package name – the package of the generated aspects.
 C.	General – currently used only for specifying the log4j configuration location.

← Older revision		Revision as of 13:26, 19 August 2010
Line 4:		Line 4:

	[[Image:gwt.preferences.jpg]]		[[Image:gwt.preferences.jpg]]
		+
		+
		+	2. From Window menu, choose PreferencesGoogleApp Engine. Configure it to point to your <PlayGo>\plugins\com.google.appengine.eclipse.sdkbundle.1.3.0_1.3.0.v200912141120\appengine-java-sdk-1.3.0 directory:
		+
		+	[[Image:gwt.preferences2.jpg]]
		+
		+	3. From Window menu, choose PreferencesJavaBuild PathClasspath Variables. Edit the PLAYGO_PLUGINS variable to point to your <PlayGo>/plugins/ directory:
		+
		+	[[Image:classpath.references.jpg]]
		+
		+	4. Basically the examples provided are configured with relative paths and should work well in your environment, but this is a good opportunity to introduce some parts of the configuration you can control.
		+	Right click the GWTMemoryGame project->Properties->S2A Builder:
		+
		+	[[Image:playgo.s2a.properties.jpg]]
		+
		+	As shown in the screenshot above, there are 3 tabs in which you can configure properties related to S2A:
		+	a. S2A Compilation
		+	i. Here you can add and remove models which you want to compile with S2A. For those models you add, you may choose which LSCs should be compiled by S2A. In other words, for which Interactions S2A will generate aspects.
		+	ii. Target Folder: here you specify the directory in which the generated aspects will be located.
		+	iii. Clear Automatically – if on, cleans the aspects directory before generating new aspects.
		+	iv. Polymorphism – enable or disable polymorphism.
		+	b. Imports
		+	i. Here you may specify packages that will be imported in the generated aspects.
		+	ii. Output package name – the package of the generated aspects.
		+	c. General – currently used only for specifying the log4j configuration location.