RE: MVC and applet

As others have mentioned applets can be a real pain.
 
With Microsoft not supplying a JVM anymore for WinXP you need to install a jvm 
(probably sun).  
 
We have some browser applications that will not operate correctly if the JVM is 
enabled for the browser... you may want to ensure this will not be a problem in 
your organization.
 
While today your application is internal, what about if you want to open it up 
for external use ?  Then you lose control over the choice of browsers by the 
external users, also possible issues with openning ports in firewalls unless 
you are going to use HTTP tunneling for the connection. 
 
The best business advantage I have put applets to use is around real time 
streaming data.  

If these are internal users why not write a thick client java application ?  
You could put the code on a networked drive.  This also frees you from the 
restrictions of the Sandbox. 
 

Lim Hock-Chai <Lim.Hock-Chai@xxxxxxxx> wrote:

The problem I've with browser base application is that the UI is not as good, 
compare to PC type application. The objective is to modernize our legacy green 
screen application. This application is primary use by internal user and most 
of them probably using the same application all the time. A non user friendly 
UI will not provide any benefit for the user. 

As a generalization I would disagree with your strategy here !  The browser 
based UI is the standard. Introducing a flasher but different style of user 
interface can increase costs of training and increasse operational support 
costs.  I would argue that consistency is the key attribute here. Your AS/400 
server based application should look feel and behave like the other browser 
based applications in your company and applications hosted outside your company 
but commonly used by your targetted users. 

                
---------------------------------
Do you Yahoo!?
Shop for Back-to-School deals on Yahoo! Shopping.