Difference: DuckySebastianSukesh539Project (8 vs. 9)

Line: 1 to 1

META TOPICPARENT	name="DuckyHomework"

GUI XML to AspectJ translator project

A Project for 539D in Term 2 of 2006: DuckySherwood, Sebastian, and Sukesh

Line: 10 to 10

Changed:

<
<

- Find XML dialects and tools SS
- 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 SS (farming out work to KDS and SC as possible)
- Present the different dialects/tools and recommend a dialect SS

>
>

- ~~Find XML dialects and tools SS~~
- ~~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 SS (farming out work to KDS and SC as possible)~~
- ~~Present the different dialects/tools and recommend a dialect SS~~
- Choose a tool/language

Line: 52 to 53

Changed:

<
<

Luxor -- XUL toolkit -- looks like it interprets XUL, but XUL might be a good starting point. (Is there a graphical XUL builder?) -- kds

>
>

Luxor -- XUL toolkit
- looks like it interprets XUL, but XUL might be a good starting point. (Is there a graphical XUL builder?) -- kds
- Good XUL engine. But you have to define actions in your java code. There seems to exist to write some kind of scripts to extend the XML language, but I do not know how it works exactly. -- ss

jxmlguibuilder XML to Java: difficult documentation (in German), project looks abandoned

Changed:

<
<

Java Gui Builder (JGB) XML to Java -- minimal documentation, minimal activity, stuff looks abandoned

>
>

Java Gui Builder (JGB) XML to Java --
- minimal documentation, minimal activity, stuff looks abandoned -- kds
- registration of ActionListeners in the XML-file possible but for object like buttons etc. there is a limited number of predefined attributes available. I prefer not to use it.

Added:

>
>

- Like XUL but I found no possibility of writing scripts.(Do we need that at all?) Has in my opinion a good documentation but you have to fire your events completely in your javacode.(is that bad?)

Added:

>
>

jxul very poor documentated but it seems alright. However there is no reason why to prefer it to luxor. -- ss
thinlet -- similar to swixml, however swing is not requiered (according to their documentation). Since they use an event-model, I’m wondering how it works.
gui4j - event handling is integrated more into XML than in Luxor, but you still have to fire events in java code, so this feature is a little bit weird and useless to my opinion. The number of attributes for objects is limited so that I do not want to work with it!
Koala -- seems not to be build on Swing, because they describe javaBeans all the time. So that it won’t work for our project

These might or might not be useful -- some might have some dialect of XML as a output language