Re: Constructors take vararg of Component? (Enhancement RFC)

2013-01-07 Thread Martin Grigorov
Hi, The component constructor doesn't call #add() at the moment (and I think this wont change soon without a better reason). So even if adding the varargs this wont help. But you can create your own components which do this: public class MyForm extends FormEntity { public MyForm(String id,

Re: Constructors take vararg of Component? (Enhancement RFC)

2013-01-07 Thread Jochen Mader
Why aren't you using fluent interfaces? The API ist built around that and allows for a much cleaner structure inside your constructors. Just watch out for those Auto-Formaters ;) new FormRsvpPage(frmRsvp, cpm) .add(new StatusPanel(pnlRsvp)) .add(new ConfirmPanel(pnlConfirm))

Constructors take vararg of Component? (Enhancement RFC)

2013-01-06 Thread Zac Bedell
Greetings all, I was wondering what Wicket users devs might thing of a possible API change for a future version (maybe Wicket 7?) of including a varargs array of Component as the final parameter of all of the various MarkupContainer subclasses? I find myself doing things like these a lot:

Re: Constructors take vararg of Component? (Enhancement RFC)

2013-01-06 Thread Robert Szmurlo
Hi, you can use something like this: RsvpPage.this.add( new Label(event.title), new CssFeedbackPanel(feedback), new FormRsvpPage(frmRsvp, cpm).add(pnlNoRsvp, pnlRsvp, pnlConfirm), pnlRsvpRules ); I am not dev, but I wouldn't break the API. BR, Robert