geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Kurjanowicz" <mkurj...@cc.gatech.edu>
Subject Re: new console-swing team
Date Fri, 21 Nov 2003 20:50:41 GMT
I happen to agree with Alex here, when we really look at it, all of the
functions we need are really easy to do in JMX and we don't need to make up
some common code that exists between the consoles.  Basically, the consoles
are just the pretty front-end to the direct JMX code.

I think I like the idea of Swing better for the stand-alone client, and I'll
start throwing something together this afternoon/night.  I've got a good
deal of time tonight, and should have something at service-cache by early
morning (1, 2am EDT GMT -5, I think).

Anybody who wants to help, make sure that you get a sourceforge username and
then let us know.
Thanks,
Matt K.
----- Original Message ----- 
From: "n. alex rupp" <rupp0035@umn.edu>
To: <geronimo-dev@incubator.apache.org>
Sent: Friday, November 21, 2003 3:12 PM
Subject: Re: new console-swing team


> Al, we actually do share the same model--JMX : )
>
> It's the custom addons to JMX to prettify the output that
> might not transfer too well between apps ; )
> --
> N.
>
>
> ----- Original Message ----- 
> From: "Allen Fogleson" <afogleson@blackboard.com>
> To: <geronimo-dev@incubator.apache.org>; <mariano.kamp@acm.org>
> Sent: Friday, November 21, 2003 2:12 PM
> Subject: RE: new console-swing team
>
>
> I have done a fair amount of swing development - although I suspect as
> most here I have done much more work on thin clients, and the
> model/controller side of things.
>
> I really wouldn't be a big fan of an swt stand-alone app (although I
> admit to its better look and feel) As someone else pointed out the
> supported OS' are limited for swt.
>
> I would disagree that the model cannot be shared with the apps. A
> properly designed model should easily be shareable. Isn't that the idea
> behind separation of concerns :)
>
> Al
>
> >>Just one more thing regarding the discussion on sharing model code
> between
> >>clients. I am bit sceptic about sharing code between the web-console
> and a
> >>standalone-client, but I can imagine that it would be much easier to
> do so
> >>with a swing and an eclipse app.
>
>
>


Mime
View raw message