Re: Overriding panel markup

2008-08-26 Thread shetc
Excellent! Thanks for your help. -- View this message in context: http://www.nabble.com/Overriding-panel-markup-tp14642196p19161133.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail

Re: Overriding panel markup

2008-08-26 Thread pixologe
w this message in context: http://www.nabble.com/Overriding-panel-markup-tp14642196p19157016.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional command

Re: Overriding panel markup

2008-08-25 Thread shetc
ds, etc. > > Just create another class. You VM can handle it :-) > > Eelco > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Ov

Re: Overriding panel markup: close tag not found for tag

2008-05-12 Thread Maurice Marrink
So in your page you are doing exactly the same as Palette, i.e. you are adding all the components, headers, etc ? Just because you want to have different markup. Then why don't you create your own Palette and use fragments to change the markup, that certainly is a lot code friendlier then repeating

Re: Overriding panel markup: close tag not found for tag

2008-05-12 Thread Martin Makundi
But why does it seem to work with FeedbackPanel? I want just that. A fragment I understand just means providing optional markups. That is not exactly what I want because every realization is different. ** Martin 2008/5/12 Eelco Hillenius <[EMAIL PROTECTED]>: > > Instead, I want the MyPage.html to

Re: Overriding panel markup: close tag not found for tag

2008-05-11 Thread Eelco Hillenius
> Instead, I want the MyPage.html to contain the panel markup: In a > similar manner to how the feedbackpanel markup is given in that > example in the book "created the component component structure inside > the page". You should use a Fragment instead of a Panel in that case. Eelco

Re: Overriding panel markup: close tag not found for tag

2008-05-11 Thread Martin Makundi
I do not want to have a separate MyPalette.html, because many times I use the palette its layout must be different. Instead, I want the MyPage.html to contain the panel markup: In a similar manner to how the feedbackpanel markup is given in that example in the book "created the component component

Re: Overriding panel markup: close tag not found for tag

2008-05-10 Thread Maurice Marrink
Correct me if i am wrong but is this not the com.apress.wicketbook.validation.UserProfilePage from the book? Note that i do not have the book nor have i read it, i just have the example sourcecode, but judging from the code they are not replacing FeedBackPanel markup but are actually creating a com

Overriding panel markup: close tag not found for tag

2008-05-10 Thread Martin Makundi
Hi! I understand that it is possible to override Panel markup in your within your main page. The Pro Wicket gives a simple example with the FeedbackPanel: User Profile Message goes here Message log level However, when I try to override the Palette component layout in a similar manner:

Re: Overriding panel markup

2008-01-06 Thread Chris Webb
I imagine it can :) cheers Eelco Hillenius wrote: I wondering what's the best approach to overriding the markup for a panel. Is there a method I can override or should I just extend the Panel? You should extend it. You *could* use a custom resolution (see the custom markup example in wic

Re: Overriding panel markup

2008-01-05 Thread Eelco Hillenius
> I wondering what's the best approach to overriding the markup for a > panel. Is there a method I can override or should I just extend the > Panel? You should extend it. You *could* use a custom resolution (see the custom markup example in wicket-examples), but extending the class is easier to im

Overriding panel markup

2008-01-05 Thread Chris Webb
Hi, I wondering what's the best approach to overriding the markup for a panel. Is there a method I can override or should I just extend the Panel? I thought extending might be overkill if all I want to do is specify different markup but not change the functionality. Specically I'm trying to o