Originally posted by Tomasz Prus:
The power of Wicket is his big awesome community. I heard that Wicket have a lot of contributors. This have some pluses and some minuses. How Wicket leaders secure code quality, design quality and Wicket quality at all.
I'd like ask question for Agile and TDD fanatics "Do You like Wicket?"
Originally posted by Josh Brown:
Does the Eclipse plugin work well? I've used some Eclipse plugins that are severely lacking, so I'm a bit wary. What about the plugin for IntelliJ? Have you worked with it at all? How does it compare to Eclipse?
Originally posted by Martijn Dashorst:
I think the Sun motto is: Innovation happens elsewhere. JSF may have a benefit of being a standard, but it is also its achilles heel. Improvements in the platform arrive at glacial speed because they have to be approved by the committee.
Originally posted by John Todd:
But one drawback -I think- is you hard-code component's name in your Java code :
add(new Label("message", "Hello World!"));
What if you want to change component's name ?
?
Originally posted by Karthik Guru:
Does tapestry support stateful components and pages like wicket? If it doesn't then the only similarities are that they have swing-like components and work out plain html templates? How about echo? Is there any other framework that manages state/session like wicket?
Originally posted by John Todd:
Aaaa, I don't mean wicket:id , I mean message.
You hard-code the component name in your code then you refer to it in you HTML page.
Originally posted by Frank Silbermann:
Though Wicket's implementation uses some ideas taken from Tapestry, the only framework I know of which might have a similar style of programming is Echo.