Originally posted by Bhupesh Arya: have not worked on Swing much, so would appreciate if somebody can help with some links where i can find some design tutorial/notes/tips etc for Swing.
i dont think we have to enter so much in details, with swing client app : dont you think ? I mean, once you said the travel agent will connect thru a swing app, i think the next step is to say how : protocols, differents subystems ...
Plus the architect needs to justify why a swing client was prefered over a thin client.
I don't think we have to do that since it is a clear customer requirement. Why should you justify the customers decision? It would make sense if you would break that requirement - but that's a no go!
Joined: Jun 01, 2005
Originally posted by David Follow:
I don't think we have to do that since it is a clear customer requirement. Why should you justify the customers decision? It would make sense if you would break that requirement - but that's a no go! D.
I think the customer requirement is best performance, the client has not specified that a thick swing client is needed. The choice of thick-vs-thin client is made by architect.
This is being discussed in multiple threads in this forum :-
and each thread is looking at one side of this thick-vs-thin client ( Swing-vs-browser client ).
Joined: Jul 12, 2005
The only customer requirement for the user interface is that it should be graphical. We have to justify why we preferred a standalone swing application. There are other web based choices: applet, java webstart. java server faces (you can build reach visual components).
Joined: Jul 25, 2005
i decided to show that there are some swing widgets that coordinate with other classes to connect to the required EJB services.