I need some hints or pointers on some aspects of developing web applications with wicket. I really hate those HelloWorld applications that does nothing in the direction of giving any clues regarding "real" applications. I usually end up with more questions than answers after going through those apps.
Lets say I have a potential web application, 40-50 pages or so in total. Readyly prototyped, layed out with CSS and ready to be put into an application. I have been looking into how to structure this using wicket. I have ended up with a page template like
<html>
<head>
<link rel="stylesheet" type="text/css" href="" title="style" />
<title><span wicket:id="appTitle"/>App - Prototype (v0.1)</title> </head> <body>
<!-- Layout container starts -->
<div id="layoutBox">
<span wicket:id="headerBoxPanel"/>
<span wicket:id="welcomeBoxPanel"/>
<span wicket:id="menuBoxPanel"/>
<span wicket:id="loginBoxPanel"/>
<!-- MAIN: Put page contents inside the main div -->
<div id="main">
</div>
<!-- MAIN: container ends -->
</div>
<!-- Layout container ends -->
</body>
</html>
So, this template have to be copied 40-50 times, entering different information in the main container for the different pages. Is there any way with wicket to have one html template thats reused through out pages in the application ? That way I could change the layout of the application in just one place. Maybe I could go for using panels instead of pages? That way I would put a wicket id in the main page for the content, always loading the main page , but inserting different panels for the different pages. Anyone have any experiences yet, using wicket for more than HelloWorld applications that have any thoughts on this ? What I'm looking for is maintainability in webapps with more than a few pages.
Regards,
Jan-Petter ::-Q
