Thanks, Igor, for taking the effort to answer my question. I so understand
that one of the core vision statements is separation of concerns. I am
evaluating Click but haven't ruled out Wicket - just that some aspects of
Click seem less cumbersome because separation of concerns is not a priority
there - Click seems to suit what I need better than what Eelco had suggested
much earier: Echo.
Thanks for your time,
Phil
On 4/11/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
i thought you were using Click?
anyways, what you want is possible, like ive mentioned, but is not the
primary focus of wicket. wicket is about separation of concerns. that means
letting the designers design the markup with all its pretty css and images,
rather then making developers try to reproduce that markup via layout
managers ala swing.
what you want is not our priority so it will probably never make it into
core project unless one of core developers writes it up and maintains it.
like i said take a look at bean panels, what you want is pretty simple to
achieve with a bit of work. let me give you a short example.
class textfieldpanel extends panel {
public textfieldpanel(string id, imodel model) {
super(id);
add(new textfield("tf", model));
}
}
<wicket:panel><input wicket:id="tf" type="text"/></wicket:panel>
class checkboxpanel extends panel {
public checkboxpanel(string id, imodel model) {
super(id);
add(new checkbox("cb", model));
}
}
<wicket:panel><input wicket:id="cb" type="checkbox"/></wicket:panel>
now in your page
Form form=new Form("form");
add(form);
RepeatingView items=new RepeatingView("items");
form.add(items);
items.add(new textfieldpanel(items.newchildid(), ..));
items.add(new checkboxpanel(items.newchildid(), ..));
and in markup
<form wicket:id="form"><span wicket:id="items"></span></form>
that is pretty close to what you want. you can then start adding labels to
your checkbox/textfield panels to add labels, etc
-igor
On 4/11/07, Philip Weaver <[EMAIL PROTECTED]> wrote:
> I started this thread because I wish Wicket would support the following
> feature.
>
> I wish that each form or form element element had a default renderer and
> would render itself without needing to be embedded in some other html file.
> If layout is a problem - find a solution. I wish that Wicket had a higher
> level of componentry which could be directed purely and simply by/in Java
> code alone. This was a how-to question - but perhaps now it is a feature
> request.
>
> Phil
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
>
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Wicket-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/wicket-user
