Hi
Did you work with EJX. I tried to use it and it has some
nice features but in the case of EJX (at least for me) it
is too complicated and NO docu.
I liked the idea of using Beans and the Bean Framework but
the actual version of EJX is clunky and not user friendly
(you cannot create the JAR files if they are not there but
only adjust existing ones).
When you want to reanimate EJX please do so but keep in
mind that this is a big job and we need someone dedicated
to it.
Andy
> -----Original Message-----
> From: Holger Engels [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 08, 2001 6:30 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] A new user interface for JBoss
>
>
>
> Sorry, I don't quite understand .. what was so bad about the
> ejx approach?
> I recognized ejx as a _generic_ powerful, simply to use framework for
> building xml-editors. I think, it would be a better idea, to
> build upon the
> existing editors and make them more user friendly, verbose
> and fool prove.
>
> Maybe, we'll have to enhance ejx itself somehow, but IMHO
> it's better to
> invest in generic code, than maintaining a rather specific
> code base for
> descriptors, that may change in future.
>
>
> Concerning the management GUI, I have another suggestion. If we agree,
> that the GUI should be html-based further on (I'm in favour of it), we
> could use the wingS framework therefore. Have a look at:
>
> http://www.wings.to.com
>
> Creating GUI with wingS is as easy and comfortable, as with Swing. You
> have an SComponent pendant for nearly every JComponent, the
> same Events,
> Listeners, Models, etc.
Go for it. I prefere a Swing GUI but we are not limited to create just
on. Do you have some time to make a review about it and create a simple
example.
How does it compare to Struts ?
Andy
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
