Hi Geeks
Before I start coding the remote administration GUI for jBoss I want discuss
the future of EJX and if the administration GUI should use EJX or not.
>From the developer perspectiv EJX is easy to use when you understand its
structure and design (the only thing I miss is the lacking docu -> JavaDoc
etc.).
>From the user perspective EJX is difficult to use because it relay on the
underlaying XML structure and it is a "all in one" tool lacking user
friendly
features (like the separator tree/detail pane does not keep its set position
if you which the selected detail).
That's my goal for the administration GUI:
- easy to use
- use of look and feel already used in other GUIs
- help support
- tailored GUIs for know services (MBeans)
- all purpose GUIs for unknown services
- save and retrieve of user settings
- use of advanced GUI elements like sliders, radio buttons, checkboxes,
icons etc. to make it more appealing for the user
I don't think that EJX can deliver that and because of the lack of
documentation
I think I will waste more time than I will save through EJX because there is
no XML structure available (naturally).
I had to learn in the past (even when I hate it) that the acceptance of a
tool
or an application depends on big parts on their GUI and therefore I think
that the administration GUI is very important and that I has to be appealing
and sexy because this is what the user see and not the sexy design behind
it (I also do not like this but it seems to be true). Therefore I like to
make
the administration GUI like this to boost jBoss.
What do you think?
Have fun
Mad Andy
