hi again:)
> Hi
>
> The general idea is that JBoss implements JSR-77 and the management
> GUI uses the JSR-77 interfaces. Therefore the client does not have
> to know much about JBoss.
>
oki.. I will start playing around with JSR-77.
> I will try to consolidate the positions and ideas on the JBossMGT project
> page (www.jboss.org -> projects -> JBossMGT).
>
> Right know there are two ways to create an GUI:
> - HTML client
> - Swing Client which can be split into
> - Using an existing Framework (NetBeans, IBM's eclipse etc.)
> - Creating our own Framework
> Therefore if you have some ideas please post it hear.
I'm mostly in favour of creating a new framework. I am too incompetent to
give you any reasons other than I would prefer a microframework that could
be LGPL'ed so that other (perhaps commercial) addons could be fitted ontop
of that. The primary design goal for that would be flexibility combined with
minimal framework size. Imagine how much it would rock if the JbossMGT
client could run on your mobile phone :oP
With danger of starting a flame war I would suggest that we ditch Swing.
That is just my personal opinion -- and I am ready to accept if we go ahead
with Swing anyway.
I will return with more ideas when I feel I have studied the JSR-77 ...AND
the mailing list archive:)
greetz,
J
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
