AspectJ Installation Note

From 5ba7e88c10c7b254a2cdb59c09ebc102b4e68dfa Mon Sep 17 00:00:00 2001 From: mkersten Date: Tue, 11 Nov 2003 06:36:33 +0000 Subject: [PATCH] Adding old demo scripts. --- docs/teaching/demos/oopsla2001-script.html | 310 ++++++++++ docs/teaching/demos/oopsla2002-script.html | 671 +++++++++++++++++++++ 2 files changed, 981 insertions(+) create mode 100644 docs/teaching/demos/oopsla2001-script.html create mode 100644 docs/teaching/demos/oopsla2002-script.html diff --git a/docs/teaching/demos/oopsla2001-script.html b/docs/teaching/demos/oopsla2001-script.html new file mode 100644 index 000000000..1c506956c --- /dev/null +++ b/docs/teaching/demos/oopsla2001-script.html @@ -0,0 +1,310 @@ + + + + + + + +AspectJ Installation Note + + + + + +

AspectJ Demo

+ +

1. Installing the Demo

+ +

Extract the contents of "aspectj-demo.zip" to + "C:\aspectj-demo", resulting in the following directory structure: +
- C:\aspectj-demo +
  - apps
  - bin
  - examples
  - slides
  +
+
Verify that JBuilder 4 is using the correct project by opening it, closing + all of the current projects +
- Under the "File" menu select "Close Projects...", + select all of the open projects and close them
- Under the "File" menu select "Open Project...", + and open "C:\aspectj-demo\examples\jbuilder\Spacewar.jpr"
- You should now be able to compile "Spacewar". If + ajdeForJBuilder reports any problems refer to + "C:\aspectj-demo\apps\aspectj0.8\doc\primer\tools\ajdeForJBuilder.html"
+
Set up your "Windows Taskbar" to be permanently visible by + right-clicking the bar, selecting "Properties", and un-checking + "Auto hide"
From your "Windows Explorer" drag the + "C:\aspectj-demo\bin\Demo" folder to the "Windows + Taskbar". This will have the effect of placing the demo buttons + on the taskbar. To remove the buttons drag off the "Demo" + toolbar and close the resulting floating toolbar window.
It is useful to have the "Task Manager" running in the + "System Tray" during the demo in order to see when the debugger is + loading since it is slow. To launch it right-click the "Windows + Taskbar" and select "Task Manager", then minimize the window. +

+

2. Initial Setup

+

Emacs Setup +
- Click "Emacs", and move the cursor to the beginning of the + "spacewar.Ship.fire" method
+
JBuilder Setup +
- Click "JBuilder", open the "AspectJ Structure + View", and bring the editor to the "spacewar.Ship.fire" + method
- under the "Spacewar.jpr" node in the "Project + Explorer" (left pane of main window) expand the "spacewar" + package to see its classes
- ensure that the last compile was done without "Debug.java" + in the build configuration
+
Forte Setup +
- Click "Forte", click the "AspectJ Structure View" + button, and navigate the editor to the "spacewar.EnsureShipIsAlive" + class
+
AJDoc Setup +
- click "AJDoc", browse to the "spacewar/Ship.java" + class
+

+

3. Running the Demo

+

Emacs +
- At the declaration of the "spacewar.Ship.fire" method hit + "<cntrl>x, <cntrl>j"
- Follow the resulting popup menu to the "EnsureShipIsAlive" + advice
- Navigate back to "spacewar.Ship.fire" using the same method
+
JBuilder +
- Navigation +
  - In the "Structure View" select the "fire" + method and expand it's children to reveal "EnsureShipIsAlive: + around..."
  - Double-click "EnsureShipIsAlive: around..." to navigate + to that advice declaration
  - Navigate back using the same method, or using the + "Back", then "Forward" method in conjuntion with + the structure tree (this navigation can also be done by + right-clicking the inline advice icons in the editor's gutter)
  +
- Compilation +
  - In "EnsureShipIsAlive" remove "ship" from the + "proceed(ship)" call and recompile.
  - When the error message pops up fix it by replacing + "ship"
  +
- Build Configuration +
  - Double-click "Default.lst" and select the "lst + Designer" tab at the bottom of the editor pane
  - Expand the "spacewar" node
  - Click "Debug.java" in order to add it to the + configuration
  - Navigate to the "Ship.java" class so that the effects of + the new compilation are visible in the "Structure View" + when the compilation completes
  - Compile "Default.lst"
  - Run the project (top the execution of the project by clicking the + red stop button in the run messages pane)
  +
- Debugging +
  - Start the debugger
  - When the "Please select launch parameters..." dialog + pops up click "OK"
  - Select the "Classes" tab (4th tab from the top)
  - When the game starts, expand "spacewar", expand "Ship.java"
  - Browse to the "fire" method and expand it
  - Right-click on the "fire" method and select "stop + in spaceawar.Ship.fire"
  - Wait for the breakpoint to be hit
  - Use the "Step Into" button (5th button on the bottom + from the left) to single step the file until you step through the + advice and into the body of the fire method
  - Click the red stop button (1st button) in order to stop the + debugging
  +
+
Forte +
- Currently no Forte demo (fyi: navigate the structure the same way as + in JBuilder, and right-click the LST files to compile them, right click + "Game.java" to execute it)
+
AJDoc +
- Scroll down to the "fire" method, and follow it's + "Advised by: " link to get to the "EnsureShipIsAlive" + aspect
+

+

+ + + + + diff --git a/docs/teaching/demos/oopsla2002-script.html b/docs/teaching/demos/oopsla2002-script.html new file mode 100644 index 000000000..310505196 --- /dev/null +++ b/docs/teaching/demos/oopsla2002-script.html @@ -0,0 +1,671 @@ + + + + + + + + +demo: OO IDE + + + + + + + +

+ +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+ demo: object-oriented IDE +
+ + good at showing hierarchical + OO structure + +
+ demo: modularize concern +
+ · + Show FigureEd running + · + Inspect Point.java + · + Use joinpoint probe to find +	+ call(void figures.Canvas.updateHistory()) + && within(*) +
+ · + Describe places that its called + · + create aspect (defines a special class that can crosscut other + classes) + · + aspect HistoryUpdating + · + write pointcut (has name and parameters) +	+ pointcut moves(): + call(void + Line.setP1(Point)) \|\| + call(void + Line.setP2(Point)); +
+ · + write after advice (runs on the way back out) +	+ after() returning: move() { + <runs after each move> } +
+ · + extend advice to Point setters (multi-class) +	+ call(void FigureElement+.set*(..)) +
+ · + capture context & use interface +	+ move(FigureElement fe): target(fe) &&.. +
+ · + Show structure, note that SlothfulPoint is now included + · + Run & show effect +	+ +
+ · + Show Point.moveBy history violoation + · + Want to make sure that sets of private fields of classes implementing + FigureElement only happen from within the set methods +	+ declare warning: + + set(private * FigureElement+.) + + && !(withincode( FigureElement+.set*(..)) \|\| withincode(FigureElement+.new(..))): + + "should only assign to fields from set methods"; +
+ · + Write before advice that does precondition checking on Points. +	+ before(int + newValue): + set(int Point.*) && + args(newValue) { + if (newValue < 0) { + throw new IAE("too + small"); + } + } +
+ demo: pluggable aspects +
+ · + Worlds first fully interactive video game, now 41 years old.. + · + Explain spacewar + · + Launch with Ship.java and "Release.lst" selected and compiled. +		+ + Run + Show debug configuration in + config designer + Select + "Debug.lst", compile, and run again + Show debug window, menu, and + method tracing + +
+ demo: crosscutting structure +
+ Explain + annotations over program structure + Explain + links and associations, inheritance links + Explain + model genericity, different views + Show + inline annotations + Show + history navigation +		+ Show + global views (multiple views of your code) + Show + refactoring by changing helmCommandsCut + Show view + synchronization, task-oriented views + Discuss + how it is harder in AJ (implicit invocation) + Show + fluid documents (ISTL project) +

+ +

+ +

+ +

+ + + + -- 2.39.5