CONVOLUTED? Sorry Tomm, but IMHO an applet would be 3x more convoluted.  And the user would have to wait for that thing to load.  Also, the age old debate: you compound the user browser settings issues.  And refresh. And the pain of debugging of the applet. And you're mixing logic in your view. And you still can not make those menus dynamic, unless you hit the DB anyway, so back to square 1. etc. Ad Nauseum.
 
I have built enough applets to know never to touch one again, if I can help it. 
 
JSP is the way to go.  Code and unit test the logic in <1 hr and then let your web designers deal with colors etc. MVC all the way!  Again, as I said before -- IF AND ONLY IF you can afford the user waiting between steps of A, B, C (or if you want those menus dynamic).
 
Greg
 
-----Original Message-----
From: Tomm Carr [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 18, 2002 1:23 AM
To: JDJList
Subject: [jdjlist] RE: JSP TAGS Interaction

Greg Nudelman wrote:
Young Jedi, path to the Dark Side of Programming that way lies! 
Afraid, you will be!
Better way, there is:
Wouldn't a simple applet do the job without all the page reloading and convoluted JSP code?

Tomm

____________________________________________________
To change your JDJList options, please visit:
http://www.sys-con.com/java/list.cfm

Be respectful! Clean up your posts before replying
____________________________________________________
____________________________________________________
To change your JDJList options, please visit:
http://www.sys-con.com/java/list.cfm

Be respectful! Clean up your posts before replying
____________________________________________________

Reply via email to