You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Eelco Hillenius (JIRA)" <ji...@apache.org> on 2006/12/03 23:37:22 UTC

[jira] Updated: (WICKET-136) Add FormComponentPanel to the core project.

     [ http://issues.apache.org/jira/browse/WICKET-136?page=all ]

Eelco Hillenius updated WICKET-136:
-----------------------------------

    Attachment: 12-3-2006-FormComponentPanel-1.3.patch

> Add FormComponentPanel to the core project.
> -------------------------------------------
>
>                 Key: WICKET-136
>                 URL: http://issues.apache.org/jira/browse/WICKET-136
>             Project: Wicket
>          Issue Type: New Feature
>            Reporter: Eelco Hillenius
>             Fix For: 1.3, 2.0
>
>         Attachments: 12-3-2006-FormComponentPanel-1.3.patch
>
>
> I found it to be quite a common case that you want to have a panel that itself is not a form component in the sense that it actually receives user input, but in the sense that it cooperates with the form processing. A typical use case is a panel that embeds multiple form components but that to the outside world acts like one component with one model. For example: a Date/Time component could have a component for the date and components for hours /minutes /am or pm.
> See the attached file for a component that supports such use. It is the simplest version. The end-version should have <wicket:head> parsing in it, but that's only possible with some refactoring.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira