on 02-15-2006 6:30 AM
I want to develop mobile application on the front end side , and I know that using AWT is more flexible and consumes less resource on the client , but Is it more difficult to implement than using jsp's
Thanks ,
Oren
Hi Liron,
If you follow the development in JSP ,
1) then you can make use of the default browser capabilities.
2) can make use of the Cascade Style Sheets (for formatting(Attractive)the user interface).
3) can make use of java script , which can be used to do client side validations for input fields.
Regards
Kishor Gopinathan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think that if you don't need a canvas or something like that the difficulty of mantaining a AWT is not worth the effort.
With a JSP you can represent most of the information clearly enought
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hello liron,
if you are planning to use AWT for your UI, i would
recommend you to create base pages that could be just
extended. these base pages could also implement methods
that are commonly used like eventing and window refresh.
for example, a base page for your list pages, detail
pages, info pages and so on... in this way, it will be
easy to maintain. your base pages serve as your
"templates".
you can as well create your own presentation layer engine
that will run your scripts and present it in awt. but
this implies more work to do...
regards
jo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Oren,
Yes. AWT is more difficult to implement and maintain as compared to JSPs. There are certain more factors you should consider.
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
*Hence, most of the developers includinng me prefer JSP. This will prove very helpful when you are stuck with some problem and need an urgent solution.
Regards,
Rahul
If this helps, kindly assign me some points.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
61 | |
9 | |
7 | |
6 | |
6 | |
6 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.