You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Marcus Brito (JIRA)" <ta...@jakarta.apache.org> on 2005/08/10 16:40:36 UTC
[jira] Created: (TAPESTRY-540) All For and If components in the non-form table family should be declared as volatile
All For and If components in the non-form table family should be declared as volatile
-------------------------------------------------------------------------------------
Key: TAPESTRY-540
URL: http://issues.apache.org/jira/browse/TAPESTRY-540
Project: Tapestry
Type: Improvement
Components: Contrib
Versions: 4.0
Reporter: Marcus Brito
... to avoid the creation of lots and lots of hidden form values, when the user doesn't need them. If the user actually needs the table state to be kept on the form, he should use TableForm and friends.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Commented: (TAPESTRY-540) All For and If components in the non-form table family should be declared as volatile
Posted by "Mind Bridge (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-540?page=comments#action_12318394 ]
Mind Bridge commented on TAPESTRY-540:
--------------------------------------
I was actually thinking of deprecating FormTable, and making Table form-aware, similar to the For component. In other words, that will combine Table and FormTable. The component will also have a 'volatile' parameter to turn off the hidden fields if that behaviour is not desired. Is that solution okay?
> All For and If components in the non-form table family should be declared as volatile
> -------------------------------------------------------------------------------------
>
> Key: TAPESTRY-540
> URL: http://issues.apache.org/jira/browse/TAPESTRY-540
> Project: Tapestry
> Type: Improvement
> Components: Contrib
> Versions: 4.0
> Reporter: Marcus Brito
>
> ... to avoid the creation of lots and lots of hidden form values, when the user doesn't need them. If the user actually needs the table state to be kept on the form, he should use TableForm and friends.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Resolved: (TAPESTRY-540) All For and If components in the non-form table family should be declared as volatile
Posted by "Mind Bridge (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-540?page=all ]
Mind Bridge resolved TAPESTRY-540:
----------------------------------
Fix Version: 4.0
Resolution: Fixed
Assign To: Mind Bridge
As described in the other comment, the FormTable functions are now in Table, which has a 'volatile' parameter if needed.
> All For and If components in the non-form table family should be declared as volatile
> -------------------------------------------------------------------------------------
>
> Key: TAPESTRY-540
> URL: http://issues.apache.org/jira/browse/TAPESTRY-540
> Project: Tapestry
> Type: Improvement
> Components: Contrib
> Versions: 4.0
> Reporter: Marcus Brito
> Assignee: Mind Bridge
> Fix For: 4.0
>
> ... to avoid the creation of lots and lots of hidden form values, when the user doesn't need them. If the user actually needs the table state to be kept on the form, he should use TableForm and friends.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Commented: (TAPESTRY-540) All For and If components in the non-form table family should be declared as volatile
Posted by "Marcus Brito (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-540?page=comments#action_12318396 ]
Marcus Brito commented on TAPESTRY-540:
---------------------------------------
Yes, I was about to write a comment about it. The Table component already use For and If components, which can be form-aware. It could sport a new "volatile" parameter, which would be propagated all the way down to the individual For and If components. That sounds great.
> All For and If components in the non-form table family should be declared as volatile
> -------------------------------------------------------------------------------------
>
> Key: TAPESTRY-540
> URL: http://issues.apache.org/jira/browse/TAPESTRY-540
> Project: Tapestry
> Type: Improvement
> Components: Contrib
> Versions: 4.0
> Reporter: Marcus Brito
>
> ... to avoid the creation of lots and lots of hidden form values, when the user doesn't need them. If the user actually needs the table state to be kept on the form, he should use TableForm and friends.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org