You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Vitaly Tsaplin (JIRA)" <ji...@apache.org> on 2008/02/29 14:34:52 UTC
[jira] Created: (WICKET-1386) Implement the FormComponentFragment
Implement the FormComponentFragment
-----------------------------------
Key: WICKET-1386
URL: https://issues.apache.org/jira/browse/WICKET-1386
Project: Wicket
Issue Type: New Feature
Components: wicket
Reporter: Vitaly Tsaplin
It often appears that a form component is small and it requires no complex markup. It would be overkill to create such kind of component as a subclass of the FormComponentPanel. So I propose to provide the FormComponentFragment to address to this situation. This way anyone can create a different versions of standard components just from the ground up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1386) Implement the FormComponentFragment
Posted by "Jeremy Thomerson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Thomerson updated WICKET-1386:
-------------------------------------
Fix Version/s: (was: 1.5-M3)
1.5-M4
> Implement the FormComponentFragment
> -----------------------------------
>
> Key: WICKET-1386
> URL: https://issues.apache.org/jira/browse/WICKET-1386
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Reporter: Vitaly Tsaplin
> Fix For: 1.5-M4
>
>
> It often appears that a form component is small and it requires no complex markup. It would be overkill to create such kind of component as a subclass of the FormComponentPanel. So I propose to provide the FormComponentFragment to address to this situation. This way anyone can create a different versions of standard components just from the ground up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1386) Implement the FormComponentFragment
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg updated WICKET-1386:
----------------------------------
Fix Version/s: 1.5-M2
(was: 1.5-M1)
> Implement the FormComponentFragment
> -----------------------------------
>
> Key: WICKET-1386
> URL: https://issues.apache.org/jira/browse/WICKET-1386
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Reporter: Vitaly Tsaplin
> Fix For: 1.5-M2
>
>
> It often appears that a form component is small and it requires no complex markup. It would be overkill to create such kind of component as a subclass of the FormComponentPanel. So I propose to provide the FormComponentFragment to address to this situation. This way anyone can create a different versions of standard components just from the ground up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1386) Implement the FormComponentFragment
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg updated WICKET-1386:
----------------------------------
Fix Version/s: 1.5-M1
> Implement the FormComponentFragment
> -----------------------------------
>
> Key: WICKET-1386
> URL: https://issues.apache.org/jira/browse/WICKET-1386
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Reporter: Vitaly Tsaplin
> Fix For: 1.5-M1
>
>
> It often appears that a form component is small and it requires no complex markup. It would be overkill to create such kind of component as a subclass of the FormComponentPanel. So I propose to provide the FormComponentFragment to address to this situation. This way anyone can create a different versions of standard components just from the ground up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1386) Implement the FormComponentFragment
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg updated WICKET-1386:
----------------------------------
Fix Version/s: 1.5-M3
(was: 1.5-M2)
> Implement the FormComponentFragment
> -----------------------------------
>
> Key: WICKET-1386
> URL: https://issues.apache.org/jira/browse/WICKET-1386
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Reporter: Vitaly Tsaplin
> Fix For: 1.5-M3
>
>
> It often appears that a form component is small and it requires no complex markup. It would be overkill to create such kind of component as a subclass of the FormComponentPanel. So I propose to provide the FormComponentFragment to address to this situation. This way anyone can create a different versions of standard components just from the ground up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.