The nice thing about wicket is that it will give you freedom to choose whatever you like. You can create individual pages but if you markup is mostly the same it is easy to to use markup inheritance from a single basepage. You can also have just one page and replace panels as required. It is all a matter of personal preference / application needs. >From what you are describing you might want to take a look at http://cwiki.apache.org/WICKET/markup-inheritance.html
Maurice On Fri, May 2, 2008 at 12:36 PM, Martijn Lindhout <[EMAIL PROTECTED]> wrote: > Hi, > > My web app background is from page oriented frameworks, and now while > using wicket, I find myself creating pages over and over. > I think I can miss many of them, because most of the time all I do is > adding an intelligent reusable component to it. > > How do you guys handle this? Are you creating some basepage that is > suitable to contain more than one functional part of your application? > Or just create page by page....? > > -- > Martijn Lindhout > JointEffort IT Services > http://www.jointeffort.nl > [EMAIL PROTECTED] > +31 (0)6 18 47 25 29 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
