| |
| META TOPICPARENT |
name="DuckyHomework" |
GUI XML to AspectJ translator project
A Project for 539D in Term 2 of 2006: DuckySherwood, Sebastian, and Sukesh |
|
<
< | For this project, we will take an XML representation of a GUI plus some glue code and convert it to AspectJ SWING code.
Immediate tasks
Write a new proposal and resubmit it to Eric, preferably by Sunday
- Develop expertise in XML SC
- Choose XML GUI language
-
Find XML dialects and tools SE
-
Evaluate XML dialects and tools, including evaluating how Java/AspectJ gets plugged in and whether or not there is a GUI that will dump that output SE (farming out work to KDS and SC as possible)
-
Present the different dialects/tools and recommend a dialect SS
- Choose a tool/language
- Set up/install tools
-
AspectJ SC SS KDS
-
Eclipse KDS SE SC
- XML tools -- e.g. parser -- to be determined KDS SE SC
-
Set up CVS repository KDS
- Connect up to electricbagpipes CVS repository.
- Read directions
- Use the servername, username, and password that I sent you earlier; path /home/duckys/cvsroot
- Set up collaboration tools
- Set up Skype SC
- Publish contact information
KDS SE SC
-
Make wiki page KDS
- Get on wiki SE
SC (KDS help)
- Hand-code one small example in AspectJ KDS SE SC -- to be done collectively on Sat 25 Feb
- Do academic literature review
- XML GUIs KDS
- Observer pattern KDS
- Develop schedule (all?)
- come up with tasks
- write up schedule
- Write proposal led by KDS
|
>
> | For this project, we will take an XML representation and some aspects and make a UI |
| | |
|
>
> | Paper outline
Goal: eliminate crosscutting of widgets; one aspect per widget instance
- Lit review
- Tools review
- Possible approaches to problem
- straight LTW -- wasted a lot of time, not an option => must have wrapper -> must create wrappers, must change all swix code to call the wrappers
- different class for each instance
- different dummy method for each instance
- have pointcuts driven by the arguments
|
| |
Resources |
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.