RE: Which UI "engine" to use?

I should have stated that one of the requirements is it MUST run as a "thick
client" on the desktop. It needs to run in "offline" mode if the server is
unavailable.

But in the end you are very right, we are basically implementing our own
browser that runs as a Java client. Like I mentioned before, I have
implemented this once in AWT and it is fun to learn what browser coders go
through as it relates to dynamic drawing of a screen (though mine is
obviously much easier to program against because I require a valid XML
document :-).

Aaron Bartell
http://mowyourlawn.com

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Thorbjørn Ravn Andersen
Sent: Wednesday, February 20, 2008 5:45 PM
To: Java Programming on and around the iSeries / AS400
Subject: Re: Which UI "engine" to use?

Aaron Bartell skrev den 20-02-2008 22:38:

Could you elaborate on what you mean by "drawing the screen dynamically"?

I get an XML feed from the server and it will have something like the
following:

<form id="form1">
<button id="btnSubmit" x="12" y="100" value="Submit" />
</form>

Based on that I know I need to display a form with a single button on the
screen which I do by parsing the XML and incrementally "drawing it" by
instantiating AWT objects and adding them to a panel/frame.

The snippet looks very close to something HTML'ish, so perhaps you could
use an XSLT-stylesheet to create HTML you could use in a web page? The
logic for that is very simple.

It all depends on how much functionality and speed you need.