On 4/11/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > After 40+ hours of more research, I did indeed find my style of coding
- and
> > it clicks. Page-based, ...
Another thing I don't agree with is that page-orientation is something
to aim for[1]. I believe a mixed model is more powerful[2].
There's a lot more that can be said about the different frameworks,
but I think it can be summed up by saying that Click is primarily
pragmatic and focussed on simplicity, whereas Wicket is focussed on
providing a true OO programming model with clean separation of markup
and logic. Imo, there's something to say for both.
[1] http://www.nabble.com/Click-Rules%21%21%21-tf3555269.html
[2] http://chillenious.wordpress.com/2006/07/16/on-page-navigation/
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
I wonder if someone here can answer me this question: Why do more and more
Java frameworks try to push users farther away from the tried-and-true web
experience of having web pages that submit to servers and create other web
pages? Everything I see is trying to redefine how websites are developed and
frankly I've yet to see a single framework that does this completely and
doesn't get in the developer's way. In the end, it's still a web page, and
the expectations are there. For example, I want to submit a form, process
the data, and redisplay the same page, though with some changes according to
what was inputted. I don't know how to do this and I can't find anything in
the docs. Why is something so simple, so trivial anywhere else not also
trivial here in Wicket?
I've never messed with the likes of Echo or GWT, but I can't think that
these are any better as they try to abstract even farther by generating
Javascript for super-dynamic (read: one-page browser-breaking) applications.
Why is this, and where are the "modern" Java web frameworks that don't try
to reinvent the concept of a website?
Jason
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
