Hi!
Andreas Schaefer wrote:
> I want to make it a little bit more clear what I wanted to say.
>
> The discussion is about:
> Is EJX suitable as a GUI Framework for an jBoss Administration
> GUI Framework?
>
> OR mor general what GUI framework should we use?
>
> Here the objections I have:
> - EJX has a poor documentation (a good design is normally not simple
> and not obvious therefore at least JavaDoc is a must)
Fixable.
> - EJX is tidly integrated with Bean Context, XML and EJB
No. Actually it is not tightly integrated with either of the above. I
*chose* to use BeanContext since it made my life so much simpler, and I
also chose to make this BeanContext structure XML-aware, but you don't
*have to* do it this way. I just found it to be the easiest and most
straight-forward way to do things. The only thing EJX requires is that
the file handler can take a URL to a file, and then provide a GUI
component to edit it. That's all. Everything else is design choices.
> - EJX is not user friendly (IMO)
No it is lacking some features. But instead of making something
completely new from the ground up, why not fix EJX?
> IMO we have three choices:
> 1) improve EJX in a way that it becomes suitable as a GUI framework,
> add documentation and write HowTos.
Agreed.
> IMO then EJX must be separated
> into several part in a way that XML support becomes a service and that
> EJB is one of its usages.
The above is already the case.
> I have to admit that I am a really lazy programer and therefore I like
> to make my and also your life easier even when now more effort is
> necessary.
I am really lazy too, which is why I made EJX the way it is. For me it
represents the easiest way to get a functioning GUI going. Let me know
what you need to understand things, and let's get started.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
