Re: FormComponent markup

2013-02-03 Thread Andrea Del Bene
To clarify a bit more, you should end up writing something like: form wicket:id=form input type=text wicket:id=formcomponentA / textarea wicket:id=formcomponentB.../textarea /form and Java code Form form = new Form(form); form.add(new FormComponentA(formcomponentA)); form.add(new

Re: FormComponent markup

2013-02-03 Thread Lucio Crusca
In data domenica 3 febbraio 2013 13:17:13, Andrea Del Bene ha scritto: To clarify a bit more, you should end up writing something like: form wicket:id=form input type=text wicket:id=formcomponentA / textarea wicket:id=formcomponentB.../textarea /form and Java code Form

Re: FormComponent markup

2013-02-03 Thread Lucio Crusca
In data domenica 3 febbraio 2013 14:57:46, Lucio Crusca ha scritto: In data domenica 3 febbraio 2013 13:17:13, Andrea Del Bene ha scritto: To clarify a bit more, you should end up writing something like: form wicket:id=form input type=text wicket:id=formcomponentA /

Re: FormComponent markup

2013-02-03 Thread Andrea Del Bene
ok, I think I've figured out what you need. If you want to group two or more form fields in your custom form component you should extend class FormComponentPanel instead of FormComponent. This class combines the features of both a Panel (it has it's own markup file) and a FormComponent (it is

FormComponent markup

2013-02-02 Thread Lucio Crusca
Hello *, I have two classes, along the lines of: class A { String id; } class B { A manyBToOneA; String description; } I want to provide a single form such as: Id: Default description: [Submit] I plan to use two subclasses of FormComponent, so that one uses IModelA,

Re: FormComponent markup

2013-02-02 Thread Andrea Del Bene
Hi, if you are planning to subclass a FormComponent (let's say a TextField for the id and a TextArea for the description) you don't need to use panels and you will bind your custom components to standard form's tags input type=text/ and texarea.../textarea IMHO the second component should

Re: FormComponent markup

2013-02-02 Thread Lucio Crusca
In data sabato 2 febbraio 2013 14:54:41, Andrea Del Bene ha scritto: Hi, if you are planning to subclass a FormComponent (let's say a TextField for the id and a TextArea for the description) you don't need to use panels and you will bind your custom components to standard form's tags input

Re: FormComponent markup

2013-02-02 Thread Lucio Crusca
In data sabato 2 febbraio 2013 22:28:11, Lucio Crusca ha scritto: Does that mean I'll have A.html like form input type=text ... / textarea.../textarea /form and then add my FormComponentA and FormComponentB instances directly to that Form? And that I won't have any