Hi Tobias, I don't agree on a couple of points you made on Wicket.
Wicket is providing the GUI and you have to make sure your gluing to the backend is as transparent as it can be. So, if you have your interfaces untouched, you wont need to touch the Java code again for your 3-5 years. Also, wicket allows easy separation of your markup from your Java code, making redesign not that a big task as you suggest (given that the hierarchies need to be kept). But, I think a web /application/ is meant to evolve and not left untouched for years. Another thing about Wicket: It's all about reusability. If you design components, you can jar them up and just drop them into another project. That's one thing most frameworks don't allow. If you want to sell a product and don't want the customer to know Java: get your resources from a database and integrate some kind of templating. It just works with Wicket as well. I think I write my web applications at least as fast as you do with PHP. I have my established Wicket base and just put together the components I need: drop in authentication, localize things, complex wizards... I doubt you'll be that error-free in writing such code with PHP than you'd do with Wicket as a base. I never needed to debug much with Wicket at all. Most PHP I've seen mixes business logic and user interface so badly that - when you need to enhance things - you're really in trouble. My 2c, --- Jan. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
