The only markup difference between pages and panels for me is that panels use wicket:panel and pages use wicket:extend. Making that the same, I'd prefer wicket:extend, would make it even easier to switch from a page to a panel and back.
Jörn On Mon, Oct 20, 2008 at 10:22 AM, Ned Collyer <[EMAIL PROTECTED]> wrote: > > I use those annotations - they are awesome :) > > If you could annotate a panel to be bookmarkable.. that'd be interesting. > So the panel COULD be embeded into other components, or used standalone as a > "page". > > Currently I achieve this by creating a new page class which instantiates and > passes the panel to the super. > > Anyway, i thought it was an interesting thing to discuss. > > > Jörn Zaefferer-2 wrote: >> >> A URL is quite a strong argument for using pages. With the >> wicket-annotations project its dead-easy to make pages bookmarkable, >> just add @MountPath(path="/path/to/page"). >> >> Jörn >> > > -- > View this message in context: > http://www.nabble.com/Pages-or-components...-how-do-u-decide--tp20016807p20065174.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
