Re: Markup for a component interior
You'll need to do something like this inside your border: form.add(getBodyContainer()); See the Border javadoc for a more detailed explanation. jk On Tue, Nov 18, 2008 at 04:56:09PM -0200, Adriano dos Santos Fernandes wrote: > John Krasnay escreveu: > >You probably want to implement a Border instead of extending Form. > Border is exactly what I was looking for. But I'm having problems > [Cannot modify component hierarchy after render phase has started (page > version cant change then anymore)] with component hierarchies. > > My border markup has a and is inside > it. Is it Border suitable for this usage? > > > Adriano > > > - > 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]
Re: Markup for a component interior
John Krasnay escreveu: You probably want to implement a Border instead of extending Form. Border is exactly what I was looking for. But I'm having problems [Cannot modify component hierarchy after render phase has started (page version cant change then anymore)] with component hierarchies. My border markup has a and is inside it. Is it Border suitable for this usage? Adriano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Markup for a component interior
Extract the form to a Panel and publish the onSubmit() listener there:
MyFormPanel extends Panel {
MyFormPanel(...) {
add(new MyGenericForm(...) {
public void onSubmit() {
MyFormPanel.onSubmit();
}
}
}
abstract void onSubmit();
}
Martijn
On Tue, Nov 18, 2008 at 4:36 PM, Adriano dos Santos Fernandes
<[EMAIL PROTECTED]> wrote:
> I have a generic Form component (extends Form) and it adds child components
> to this. But where I place this form, I need to specify more content for the
> form interior. Kind of:
>
>
> tags put by the Form class
>
> tags put by who inserted the class on the page
>
>
> In my prototype code, I have all the markup inside the page, and I add the
> form to it. But as I'm going to create more pages, I don't want to duplicate
> the markup. I feel my case is not for page inheritance. In fact, I'm already
> using page inheritance for generic layout.
>
> Any advice why I could do it?
>
>
> Adriano
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Markup for a component interior
You probably want to implement a Border instead of extending Form. jk On Tue, Nov 18, 2008 at 01:36:06PM -0200, Adriano dos Santos Fernandes wrote: > I have a generic Form component (extends Form) and it adds child > components to this. But where I place this form, I need to specify more > content for the form interior. Kind of: > > >tags put by the Form class > >tags put by who inserted the class on the page > > > In my prototype code, I have all the markup inside the page, and I add > the form to it. But as I'm going to create more pages, I don't want to > duplicate the markup. I feel my case is not for page inheritance. In > fact, I'm already using page inheritance for generic layout. > > Any advice why I could do it? > > > Adriano > > > - > 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]
Markup for a component interior
I have a generic Form component (extends Form) and it adds child components to this. But where I place this form, I need to specify more content for the form interior. Kind of: tags put by the Form class tags put by who inserted the class on the page In my prototype code, I have all the markup inside the page, and I add the form to it. But as I'm going to create more pages, I don't want to duplicate the markup. I feel my case is not for page inheritance. In fact, I'm already using page inheritance for generic layout. Any advice why I could do it? Adriano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
