Jan-Petter, I agree with you about HelloWorld, if there were HelloWorld only. We've developed some more examples (project wicket-examples) which are still small and no real world application, but the reason why we did it, was to focus and very specific feature on each example. The library example e.g. shows you by means of the Border component how you can achieve a common layout for all (but it doesn't have to be all pages) your pages.
The cdapp and library examples in project wicket-stuff focus more on real-world applications, rather than specific features. Whereas cdapp is better suited for wicket users, because it is well documented, the pattern are clear etc.., the wicket-library example (not to be mixed up with the small library example in wicket-examples) is more a play ground to proof certain functionality and pattern in a real-world application. With 1.1 there will be additional features available. Though the Border component works perfect, the concept is kind of difficult to understand and use. Anyway, wicket is about simplicity, and we were looking for a more intuitive approach. 1.1 will support markup inheritance. In order to solve your problem in 1.1 you simply subclass your base class which contains your template. You subclass contains the working area (the area which changes on your page) only. And because sometimes there is a need to slightly modifiy the template, the subclass will also support replacing/disabling components already defined in the base class. Actually the implementation is very similiar to Border, but it is much easier to use. 2nd, 1.1 will support the <wicket:head> tag. You'll be able to create a component (e.g. a user address form based on a Panel) and that specific component must trigger changes in the <head> of the Page. With 1.1 you defined the required CSS, Javascript or whatever in your component, and wicket takes care that it is "injected" at the right place of the response. Juergen On 6/2/05, Kruger Jan-Petter <[EMAIL PROTECTED]> 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
