Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Message-ID: <01da01c2c943$a18a6a70$0700000a@pink>
From: =?iso-8859-1?Q?Dag_=D8yvind_Liodden?= <dag@liodden.no>
To: "James Strachan" <james_strachan@yahoo.co.uk>,
	"Jakarta Commons Users List" <commons-user@jakarta.apache.org>
References: <01ba01bf6313$628c17e0$0200000a@stua>
 <0c9101c2c930$9d28dfb0$9865fea9@spiritsoft.com>
Subject: Re: [Jelly] Running Jelly:SWT's withouth creating a new shell?
Date: Fri, 31 Jan 2003 17:13:01 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

> > I'm working on a JMX-console for JBoss and am looking into using
Jelly:Swt
> > for scripting custom configurators for each MBean.
>
> Cool!

I think so too. In my opinion, this represents a serious gap in JBoss that
need to be filled. JBoss's JMX kernel is cool, but as long as you only have
the default MBean view of it's MBeans, it's neither functional nor
good-looking. My effort is to make a highly configurable JMX console that
let's you bind jelly:swt-scripts to specific JMX domains or ObjectNames and
customize it's appearance. E.g, the JCA-components should be easier to view
and modify by presenting them i a standard-looking Datasource-configuration
panel instead of just listing it's attributes in a table. Although before a
real deployment, these settings will be set in the deployment-descriptors,
it will be easier to tweak settings etc without having to modify them. Also,
most other App servers have this kind of functionality which make them
attractive to beginners. Also, custom scripting of gui's for certains
aspects of a deployed application makes it easier for the end-user (often a
non-application-server-and-jmx-aware-person) to inspect the status various
components in a deployment.

Scripting this user-interface makes it less cumbersome to develop and deploy
(and the performance hit isn't really an issue).

> This was an oversight - I've just patched the SWT tags in CVS so that a
> parent (shell or Container) can now be specified in an attribute.
>
> e.g.
>
> <tree parent="${someShell}">
>     ...
> </tree>

Works great! I'd like to see another feature, though. :) It would be nice to
be able to set a default value for the style-property of a tag. Buttons, for
example, always appear without a border around them if you don't specify it
(I know, this is SWT's implementation). Is it possible to do something like:

<j:set-default tag="Button" style="border"/>

Thanks for the help!

Cheers,

Dag