If you want default html for those things use panels. Make for all those components a panel part that has its own markup (so do that once) Then reuse those components everywhere. Not that you gain much in my eyes because you still need to have a span that places the panel at the right place
On 1/7/08, Sam Hough <[EMAIL PROTECTED]> wrote: > > > > Nino.Martinez wrote: > > > > > > Using markup inheritance: > > one super class with a corresponding html and a sub class with > > corrosponding html, extending the super class to the special need. And > > maybe a mounted page that redirects to the wanted sub based on parameters. > > > > > > Dear Nino, > > Can you do this for components that don't extend > http://wicketstuff.org/wicket13doc/org/apache/wicket/markup/html/WebMarkupContainerWithAssociatedMarkup.html > ? > > So say have an AjaxFallbackButton that you can just add to a Repeater? So > can have all the goodness of large swathe of HTML managed by the HTML monkey > but still let me, Java monkey, add components (without specific HTML)? I can > only see how I would do that by wrapping the Button in a Panel but that > seems like a lot of overhead and the object I would be returning would look > like a Panel not a Button.... > > Re: "Why not just use Echo" - could be that 80% of app is perfect fit for > Wicket but 20% would be nicer if just had default HTML for Button, Link, > TextField etc...? > > Cheers > > Sam > -- > View this message in context: > http://www.nabble.com/Is-it-possible-to-use-wicket-without-having-any-html-page--tp14607438p14668784.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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
