- I also vote for an administration Web UI (maybe using GWT like we do
in Hupa or integrating with it).
While I understand the general direction toward Web UIs, I proposed the
list of projects with Swing UI's + JNLP for several pragmatic reasons:
- Swing is already available everywhere Java is, so no need for extra
JARs. (IMHO JAMES already has too many dependencies).
- It is very very easy and fast to use a good GUI builder to achieve the
above UIs, so it would be more suitable for student projects like this
to be able to have something really usable until the deadline.
This is important considering how few of the past GSOC projects made it
back into the projects base (and remained only forgotten "experiments").
- The effect is the same as with a Web UI (but the result is available
faster): platform independent, and accessible over HTTP (with JNLP).
Also note there's no heavy loading and huge concurrence in such a UI
(only a few users).
The most important part is for the admins/owners (that are not expert
programmers) to be able to achieve their tasks, and thus to adopt JAMES.
Adrian.
P.S. If it were about Web UIs I would have proposed the use of Apache
Click Framework in first place:
http://click.apache.org/
Since it's much easier to learn and use, so a student would have been
productive in a matter of days.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
