Hi Rickard,
Just some quick thoughts.
Underneath AccountEJB you have an "EJB references" node,
which has an "EJB reference" node and an "ejb/Customer" node as
siblings. Can I verify that "EJB reference" actually represents an
example of some reference and not meta-data? If not, I'm not
exactly sure what's going on...
---
Presumably, other sub-nodes would represent configuration
possibilities of other plugins. Beneath "Account EJB" you might
have "Jaws O/R mapping." One question I have is whether or not
we should distinguish between plugins at this level of the tree.
For instance, in your prototype you've put EJB references directly
under the bean, and I think you'd also put resource references,
environment entries, security role references, etc. at this level. I
wonder if they shouldn't all be grouped under an "EJB 1.1
deployment descriptor" node.
The reason I might consider this is that other plugins may also
have multiple configuration screens that the user might want to
navigate via tree nodes. For example, an O/R mapping plugin
might need a screen for column-to-table mappings, a screen for
relationship join definitions, or whatever. It seems to me they
should all go under the "Jaws O/R mapping" node beneath
AccountEJB, rather than as "Jaws Column-to-Table Mappings,"
"Jaws Relationship Join Definitions," etc.
The disadvantage is that there is an extra click of the mouse to get
to all these settings, so it's a question of organization vs.
navigational convenience. One way to solve this without an extra
layer in the tree might be simply to make each plugin define its
own icon.
Dan
On 25 May 00, at 18:05, Rickard �berg wrote:
> Hi!
>
> Rickard �berg wrote:
> > Justin Forder wrote:
> > > Moving the tabs to subnodes of the bean (your suggestion) would be good.
> > > There would be a possibility of using subnodes for categories, each
> > > having up to three tabs, but I don't think it applies to this example.
> >
> > +1. Very good idea.
>
> I have made a rough prototype of what this could look like. A screenshot
> can be found at:
> http://dreambean.com/download/rickard/newejx.gif
>
> As you can see, the entity has the categories of subnodes as subnodes,
> and each of these categories have the entries as leaves.
>
> This approach can take many more categories than the tabbed variant
> (currently in use).
>
> Comments?
>
> /Rickard
>
> --
> Rickard �berg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
