New design of EJB module properties

Hi!

We're redesigning various EJB views in IDEA now, and we need the user
opinion about it. I mean mostly EJB module view, where there's seemingly too
much screen space wasted. Thus, we think it would be good to move EJB
relation settings from a separate tab into the one with EJB list. The result
will look approximately as the image in the attachment. What do you think?

--

Peter Gromov

Software Developer

JetBrains, Inc

http://www.jetbrains.com

"Develop with pleasure!"





Attachment(s):
ejb.png
4 comments

The main point here is getting rid of the dialog, and use master/detail
form instead.

0

It's slightly better than before, but I don't like it since you're
wasting an awful lot of screen space for the "Configured EJBs" list,
and then having to cram all the info we have to work with in the lower
right corner.

What about using a drop down box or tabs instead of this huge list? The
main point seems to be to select the ejb to work with...

O


On 2006-02-06 13:25:05 +0100, "Peter Gromov" <peter@jetbrains.com> said:

Hi!

We're redesigning various EJB views in IDEA now, and we need the user
opinion about it. I mean mostly EJB module view, where there's
seemingly too much screen space wasted. Thus, we think it would be good
to move EJB relation settings from a separate tab into the one with EJB
list. The result will look approximately as the image in the
attachment. What do you think?



0

Oliver Fink wrote:

It's slightly better than before, but I don't like it since you're
wasting an awful lot of screen space for the "Configured EJBs" list, and
then having to cram all the info we have to work with in the lower right
corner.

What about using a drop down box or tabs instead of this huge list? The
main point seems to be to select the ejb to work with...


The top list doesn't actually select the item from the bottom part. It
looks like it's better to have "Relations" in a separate tab. But the
"generic" tab would be so empty... :)

0

My objection is more philosophical than practical, but is there much demand for an enhanced EJB2 entity view? I'm an EJB2 entity user (one of the few few remaining ones), and I don't see anyone caring much about IDE support for improving relationship stuff. If you can't do it by hand/xdoclet by now, you probably never will!

0

Please sign in to leave a comment.