I mean the markup of the individual components that get's inserted into the Border component, if that is the correct term. I'n not completly atop with my wicket understanding yet :-) MainPageBorder.html containing the wicket:border tag and wicket:body tags, then Page1.html containing markup to be inserted in place of wicket:body in MainPageBorder.html. So what you say is that the header markup in MainPageBorder.html is ignored and the header markup in Page1.html is used. If this is the case, I have to duplicate the header markup for every page to be inserted in the border component to get style sheets, javascript etc.
And the wicket:id="appTitle" does not work. Jan-Petter ::-Q -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Juergen Donnerstag Sent: 2. juni 2005 13:04 To: [email protected] Subject: Re: [Wicket-user] Need suggestions for structuring pages in a webapp Not sure I completely understand what you means. When you are talking about "individual pages" you mean the markup associated with your Border component? Border and Panel components currently simply ignores everything that is outside of <wicket:panel> or <wicket:border>. The first of your markups e.g. contains <wicket:border> but outside of that it is refers to <title><span wicket:id="appTitle"/>App - Prototype (v0.1)</title>. I would be surprised 1.0 handles it correctly. Juergen On 6/2/05, Kruger Jan-Petter <[EMAIL PROTECTED]> wrote: > Ok, so instead of the first html template I now got a "main page" like > this with a Border/body construct. > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> > <head> > <link rel="stylesheet" type="text/css" href="style/app.css" > title="style" /> > <title><span wicket:id="appTitle"/>App - Prototype > (v0.1)</title> > <script src="script/menuExpandable.js" type="text/javascript" > language="Javascript"></script> > <script src="script/option.js" type="text/javascript" > language="Javascript"></script> > <script type="text/javascript"> > <!-- > window.onload = function() { > initializeMenus(); > } > //--> > </script> > </head> > <body> > <wicket:border> > <!-- 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 --> > <span wicket:id = "mainBorder"> > <wicket:body/> > </span> > <!-- MAIN: container ends --> > </div> > <!-- Layout container ends --> > > </wicket:border> > </body> > </html> > > With my own subclass of wicket.markup.html.border.Border since I don't > want the box from BoxBorder. > > This gives me individual pages like > > <html xmlns:wicket="http://wicket.sourceforge.net/";> > <head> > <link rel="stylesheet" type="text/css" href="style/app.css" > title="style" /> > <title><span wicket:id="appTitle"/>App - Prototype > (v0.1)</title> > <script src="script/menuExpandable.js" type="text/javascript" > language="Javascript"></script> > <script src="script/option.js" type="text/javascript" > language="Javascript"></script> > <script type="text/javascript"> > <!-- > window.onload = function() { > initializeMenus(); > } > //--> > </script> > </head> > <body> > <span wicket:id = "mainBorder"> > <div id="main"> > ... Some content here ..... > </div> > </span> > </body> > </html> > > This leaves one more thing that I would like to remove from the > individual pages, the header part. I have to include the <head> things > in each page to get the stylesheet and java scripts right, even though > they are already included in the "Main" page. Is there any way to get > wicket to ignore <head> data in the individual pages , and use the > "main" page head data instead ? Or is this what you described as 1.1 > functionality Juergen ? > > Jan-Petter ::-Q > > -----Original Message----- > From: Kruger Jan-Petter > Sent: 2. juni 2005 10:38 > To: [email protected] > Subject: RE: [Wicket-user] Need suggestions for structuring pages in a > webapp > > > Ahh, missed that one in the samples. Seems to be what I'm looking for. > > Thanks ! > > Jan-Petter ::-Q > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Eelco > Hillenius > Sent: 2. juni 2005 10:26 > To: [email protected] > Subject: Re: [Wicket-user] Need suggestions for structuring pages in a > webapp > > > Use a wicket.markup.html.border.Border > (http://wicket.sourceforge.net/apidocs/wicket/markup/html/border/Borde > r. > 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 > > > ------------------------------------------------------- > 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/?froffad-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 ------------------------------------------------------- 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
