Hey Rickard,
pretty & cool, below my 0.02:
> * The "Action" menu bar has been removed (people never really
> found it).
> Instead there is a toolbar with the possible actions. This takes more
> space, but hopefully it will be ok anyway.
I planned to move the Action menu into the main menu bar, a little bit of
work but seemed to me more usual. I have to say that your button solution
isn't bad at all, but what about a quite long "Add container configuration"
button ?
But of course you can replace text with icons and use the text as tooltip...
> If you guys have any other pet peeves that you want me to fix in EJX
> while I'm at it, let me know.
One thing I've already done is to split for example container configurations
between standard and custom. So I load standardjboss.xml, let those
configuration to be read-only and give possibility to the user to add custom
configurations which are the only one saved to jboss.xml.
This way the user can browse the standard configuration but cannot modify
them. But of course this requires the viewer to query the bean to know if
the node is read-only or not...
Another thing I haven't had time to do yet is, whenever you choose "new
configuration", to load the new one with a default one (eg for entity
containers load the standard CMP one) from standardjboss.xml so that the
user is not scared filling the advanced cache settings if he wants only
change the container invoker. Furthermore this will sweep the transaction
manager empty element bug (that EJX has now), since EJX will use a good
template instead of a empty one for the new configuration.
Another thing :-) use java.awt.Cursor to give feedback to user on long
operations such as save and load from jar, etc. Little change for a big
impression to users. With jdk1.3 almost all previous bugs with Cursor are
gone.
Bests,
Simon
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
