on 2004 Jan 06 1:44 PM
Dear all;
any guidelines on when to go for the UI modelling with AWT or when to use the JSP approach ?
Hi Darry,
the choice for JSP vs. AWT depends on a couple of issues and is discussed in the standard developer training. We'll need to move this info also into the MDK:
********************************
When to use JSP:
Pros:
Standard UI model best known by end-users
Modern look and customizability
Easily enhancable
Recommended programming model of SAP for white collar apps
Best choice for all modern business PDA
Easy switch between online and offline
Integrates best with other web applications
Cons:
Requires more system ressources (local web server)
HTTP paradigm not suitable in all situations (e.g. scanners)
*************************************
When to use AWT:
Pros:
Full UI control
- Best use of screen size
- Very good for blue-collar workers
- HTTP paradigm not suitable in all situations (e.g. scanners)
Smaller, faster installation requiring less system resources
Cons:
UI changes require coding changes (and additional testing!)
UI development difficult*
Old-fashioned look
Cu, Jan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
66 | |
10 | |
10 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.