I prefer to work with pages. With this approach, you can still reuse panels ofcourse. But my experience is that allthough it is nice to have your pages componentized to the max by breaking it up in smaller, possibly reusable parts, it is also easy to loose track. I like to work with pages as I can see in one glance what that page is doing. I try to wait breaking out panels until I need similar components in other pages. If reuse not needed, I keep my stuff in pages. The disadvantage of this though, is that you need to pass around state (models), and worry about navigation more.
Eelco On 9/5/05, Kenneth Foo <[EMAIL PROTECTED]> wrote: > > Hi > > Just curious here as to which is more "correct" > > Was trying out wicket and noticed that i have a tendency to design apps > where there are > few pages (2 or 3 WebPage objects), and many more panels (navigation panels, > main content panel, header panel). > The main content panel would then be interchanged with the necessary > "module" panels. > > (eg. if I click on a "user management" link in the navigation panel, I'll > swap what's in the main content panel with the > user management panel. In this user management panel, I'll have a "user > listing" panel, an "edit user" panel, etc which I'll > swap depending on which one i'm interested to use. The responsibility of > swapping belongs to the parent container which > decides on what to swap with based on the events fired by the subpanels) > > > > In this model,each page has 1 form, and within this form, I have panels of > modules (such as user management module, > etc...). Panels nest with other panels, sometimes up to 3-5 levels deep. > > I'm curious whether others are using this method (which I feel is more > "componentized), or the more traditional > web-style approach where we have many pages (eg. one page for user listing, > one page for editing user details, etc) > and transferring navigation to these pages via redirects/etc or > requestCycle.setResponsePage(). > > Off the top of my head, using panels instead of web pages allows me to reuse > the "user management" module in other web apps > or for quick prototyping. > > What are your thoughts, guys? > > > Regards > Kenneth ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
