 |
|
 |
|
|
|
Object Oriented Web Programming
by Davide Montesin d@vide.bz
|
|
|
|
|
|
|
Complexity of Web page:
Simple JSP Structured programming |
|
|
|
|
|
|
Complexity of Web page:
JSP tag lib and includes |
|
|
|
|
|
|
Complexity of Web page:
What about object oriented programming?
|
|
|
|
|
|
|
What about web OOP?:
Powerful tools for complexity: Inheritance and composition |
|
|
|
|
|
|
What about web OOP?:
Why web is a step back? |
|
|
|
|
|
|
What about web OOP?:
object oriented is easy!? |
|
|
|
|
|
|
Ajax:
More rich but complex web pages |
|
|
|
|
|
|
Ajax:
Ajax/Js client side vs Java server side |
|
|
|
|
|
|
I think:
Server side Java is the manager! |
|
|
|
|
|
|
Server side Java programming: GWT
|
|
|
|
|
|
|
And what about client Ajax/Js?:
I generated it from server side objects |
|
|
|
|
|
|
Server side java frameworks: GWT
From java to javascript translation |
|
|
|
|
|
|
Server side java frameworks: ECHO2
|
|
|
|
|
|
|
Server side java frameworks: Wicket
|
|
|
|
|
|
|
I want more from OO:
The "What and How" promise! |
|
|
|
|
|
|
I want more from OO:
A conceptual object oriented model layer (interface) of my application and then a pluggable implementation! |
|
|
|
|
|
|
MVC:
Same model, more views |
|
|
|
|
|
|
|
|
|
|
|
My challenge: WebOE
A little more than a proof of concept of abstract web OO programming with pluggable implementations: custom, swing, gwt, ... |
| Why WebOE | 1 / 21 |
|