I've done both and tend toward straight Swing using, of course,
gridbag layout with either Eclipse or Netbeans. The new "Matisse"
layout manager from Netbeans is pretty nice -- almost drag and drop.
Swing is OK, once you get used to the layout manager stuff. UI user
events tie off nicely to backend handlers well if you're using a
visual gui like Eclipse or Netbeans.
Bill
On 11/20/06, Šoltís Ján <[EMAIL PROTECTED]> wrote:
Hello,
I've developed a couple of Tapestry apps and now we have to develop an
application with a rich gui in Java (SWING or SWT).
I particularly like 'The Tapestry way' of developing the UI as opposed to the
Struts, JSP or JSF way. What I like the most is the notion of high-level
application components that are easy to create, easy to use by other
programmers and that encapsulate both visual appearance and some high-level
functionality unique to that particular application.
Our application will consist of hundreds of screens all of them very similar
(kind of CRUD but not exactly). Had it been in web, Tapestry would be a great
choice. We could create some high level components and our screens' sources
would by very simple, clear and concise.
And the question is: what do you, Tapestry addicts, use for development of rich
gui Java apps? Plain SWING? SWT? Some framework?
XUL (XSWT) is quite close to my expectations, but it's missing "application-level
custom components". What's your opinion?
thanks
jan soltis
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
"Budgets are moral documents."
-- Ann Richards
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
