Greg Nudelman wrote:
<MAIN POINT 1>
My main point was this:
 
---- With JSP GUI (written with MVC in mind) you will NEVER need to change your JAVA CODE to change the color/size/placement/formatting of this page after you're done.  This is strictly HTML work.
 
------ On the other hand, with the GUI Applet, you WILL have to change your JAVA SWING CODE every time your project manager wants to change the colors, or labels, or some other sh*t they make their business to change 17 times a week. This is a pain.
 
Agreed?
Agreed that project managers are, in general, asses.  That is why the boss I now work for is, well, me.

However, have you not heard of resource bundles?  There is not much I can think of about the appearance of the app/applet that cannot be read from a property file.  You can change not just the button text, but the font, size and color.  You can line them up across the screen or down one side.  If you really wanted to get anal about MVC, you could create an entire "V" infrastructure where you can change the appearance of every GUI app(let) company wide without touching a line of code.

Granted, this will impact startup time, something you have already expressed dissatisfaction with.  But rule #1 in every rule book in existence: there is always a cost.
<MAIN POINT 2>
>An applet would not need to refresh the entire page just to display new information.
Sure. However, if anyone ever tried to build this kind of an applet and make it run in their web page, they would have to involve a specialized interface not a simple HTML form-based HTTP GET/POST (mainly java.net.URL) , and/or use frames and lots of JavaScript communication (BTW: I am currently working on just such a project!!)  This can be done, but this is by no means trivial.
Here I have no idea what you are talking about.  What javascript?  Other than the <applet> tag, the applet (as originally described) is completely self contained -- on the client side, anyway.  You may be working with applets that need to send/receive data to/from other applets on other pages, but such is not the case here.
IMHO, I think this comes down to utility and "appropriate technology".  I think I can make this run with JSP/Servlets in <1 hr.  >From scratch. Can you code and make this kind on an applet you're talking about and make it run in that time frame? 
Three combo boxes, the lists of two of which are dependent on the selection of the previous one?  Probably.

But even if not, this would be the last reason I would select one method over another.  Initial development is the least expensive time to work on a project.  This is precisely where you don't want to rush.  Any shortcuts taken here will come back later at ten or more times the cost.  You will spend an dollar and and hour tomorrow to save a penny and a minute today.

This is something else PM's can't seem to get through their thick skulls.  But that is a different rant altogether.
You will need to code the DB calls (as does the JSP solution), but in addition you'll need the Swing GUI, applet logic, java.net.URL get/post or 100 lines of JavaScript and HTML frame mess...  
Ah, so you use Swing with your applets.  That might explain your animosity. 8^)

Applet logic?  You are much more advanced than I.  I haven't gotten there yet.  But, as it seems to be so much more difficult than ordinary programming logic, I can't wait to learn about it.  I just hope I'm up to the task.

And you still have me completely at a loss with the get/post and Javascript -- I know what they are, I just don't see where they are needed in this particular instance!  And who brought frames into this?

Tomm

____________________________________________________
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