The list season is on! In a response to Xavier’s top 10 reasons to choose Wicket, James goes beyond that and provides us with a list of reasons to love Wicket. He has worked with Wicket for just about 12 hours, and already has 13 reasons to love Wicket. Here’s reason number 4:
“real re-use. Using every other framework, reuse at the UI layer has been nearly impossible, or at least broken. In struts you could re-use forms, but ended up copying jsp crap around. In wicket, you can make subclasses of existing components (like a panel) that contain your bus specific version of it.â€
Hi,
for me wicket sounds good. In our company we have developed an App-Framework with PHP and I had a look on tapestry an JSF, but I don’t like the XML-configration nightmare.
Now the things I’m waiting for are an Appl-Framework, using Wicket, with the standard things done, like user authentication, configurable access to functions and views and one special component would be great, an editable table/spreadsheet like Goggle Spreadsheet. Nothing is more convenient than having the possibility to edit data in a spreadsheet than to edit each dataset ot its own. regads mikel