Btw, Juergen is working on 'markup inheritance', which should provide an
alternative (even easier) way of achieving templating. It is planned for
1.1.
Eelco
Eelco Hillenius wrote:
Use a wicket.markup.html.border.Border
(http://wicket.sourceforge.net/apidocs/wicket/markup/html/border/Border.html)
to define common layout etc.
See the library and navomatic examples. That examples are simple, but
hopefully give you enough pointers to go on.
Please let us know when you still are not sure how to go on.
Eelco
Kruger Jan-Petter wrote:
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="style/app.css"
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
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit
http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
