[Echo-list] Re: [EchoPoint] Go and vote !

[Domagoj J. <do...@la...>]

Well for my view of the problem and current solutions I think that Echo =
is the best (for rich interactivity apps).
And for more portal / presentation like where designers must do much =
work and only some dynamic content is "included" , then some =
lightweigth, more template oriented (JSP, Velocity) technology is better =
, but then we can use templates from EchoPoint.

It seems that Tapestry is very popular , and ideas in Tapestry are very =
similiar to Echo.
Very toeoreticaly speaking :
Velocity, WebMacro, Maverick could be integrated into one and,
Echo, Tapestry, JSF, MillStone, wingS could be integrated into one.

I divide web frameworks by ther goal and there are rogly only two, =
template based, or like Echo, component/GUI toolkit/Swing like    =
oriented (like normal software should be).

But if you look at the templates and see HTML tags,  they are nothing =
more than textual representation of components that are realy going to =
be instatied in browsers memory, so we are using components all over the =
time, ve could say that some Echo component is a derivative component of =
a dozen of browsers tags/components, only difference here is that we use =
browsers components through HTML text.

And finaly even Microsoft made ASP.NET which is also component based.