You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Geoff Callender (JIRA)" <ji...@apache.org> on 2012/04/24 14:21:35 UTC
[jira] [Created] (TAP5-1916) Tree client should handle Zone or page
returned from events
Geoff Callender created TAP5-1916:
-------------------------------------
Summary: Tree client should handle Zone or page returned from events
Key: TAP5-1916
URL: https://issues.apache.org/jira/browse/TAP5-1916
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Reporter: Geoff Callender
Tree would be much more usable if it responded to a Zone or page returned from the NODE_SELECTED and NODE_UN_SELECTED event handlers.
This would address the most common use case for a tree: displaying a page with a tree on the left, user selects a node, the node highlights, and a zone on the right is updated with info from the server about the node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1916) Tree client should handle Zone or
page returned from events
Posted by "Geoff Callender (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263545#comment-13263545 ]
Geoff Callender commented on TAP5-1916:
---------------------------------------
Thanks Lance, understood. I'd like to change this to a documentation request.
Please add Lance's notes (above) to the the documentation. It's important info when it comes to understanding how to use the component.
* The doco also needs to describe how to achieve the most common use case (mentioned above).
* And the doco news to make clear that selectionModel is only needed for (in my opinion) an obscure use case - to select multiple leaves (and presumably submit them).
> Tree client should handle Zone or page returned from events
> -----------------------------------------------------------
>
> Key: TAP5-1916
> URL: https://issues.apache.org/jira/browse/TAP5-1916
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Geoff Callender
>
> Tree would be much more usable if it responded to a Zone or page returned from the NODE_SELECTED and NODE_UN_SELECTED event handlers.
> This would address the most common use case for a tree: displaying a page with a tree on the left, user selects a node, the node highlights, and a zone on the right is updated with info from the server about the node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (TAP5-1916) Tree client should handle
Zone or page returned from events
Posted by "Lance (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260646#comment-13260646 ]
Lance edited comment on TAP5-1916 at 4/24/12 3:22 PM:
------------------------------------------------------
I think that you might have misunderstood what is managed by the tree component and what is managed by the developer:
1. The tree component keeps track of which "folders" are open and closed so that when you navigate away and come back, the tree state is maintained.
2. The tree component does not concern itself with leaf actions. A developer can customise leaf actions by specifying a "label" block which may contain a checkbox for example.
was (Author: uklance):
I think that you might have misunderstood what is managed by the tree componentand what is managed by the developer:
1. The tree component keeps track of which "folders" are open and closed so that when you navigate away and come back, the tree state is maintained.
2. The tree component does not concern itself with leaf actions. A developer can customise leaf actions by specifying a "label" block which may contain a checkbox for example.
> Tree client should handle Zone or page returned from events
> -----------------------------------------------------------
>
> Key: TAP5-1916
> URL: https://issues.apache.org/jira/browse/TAP5-1916
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Geoff Callender
>
> Tree would be much more usable if it responded to a Zone or page returned from the NODE_SELECTED and NODE_UN_SELECTED event handlers.
> This would address the most common use case for a tree: displaying a page with a tree on the left, user selects a node, the node highlights, and a zone on the right is updated with info from the server about the node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (TAP5-1916) Tree client should handle
Zone or page returned from events
Posted by "Geoff Callender (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263545#comment-13263545 ]
Geoff Callender edited comment on TAP5-1916 at 4/27/12 10:00 AM:
-----------------------------------------------------------------
Thanks Lance, understood. I've opened TAP5-1921 as a documentation request.
was (Author: geoffcallender):
Thanks Lance, understood. I'd like to change this to a documentation request.
Please add Lance's notes (above) to the the documentation. It's important info when it comes to understanding how to use the component.
* The doco also needs to describe how to achieve the most common use case (mentioned above).
* And the doco news to make clear that selectionModel is only needed for (in my opinion) an obscure use case - to select multiple leaves (and presumably submit them).
> Tree client should handle Zone or page returned from events
> -----------------------------------------------------------
>
> Key: TAP5-1916
> URL: https://issues.apache.org/jira/browse/TAP5-1916
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Geoff Callender
>
> Tree would be much more usable if it responded to a Zone or page returned from the NODE_SELECTED and NODE_UN_SELECTED event handlers.
> This would address the most common use case for a tree: displaying a page with a tree on the left, user selects a node, the node highlights, and a zone on the right is updated with info from the server about the node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1916) Tree client should handle Zone or page
returned from events
Posted by "Geoff Callender (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Geoff Callender closed TAP5-1916.
---------------------------------
Resolution: Invalid
> Tree client should handle Zone or page returned from events
> -----------------------------------------------------------
>
> Key: TAP5-1916
> URL: https://issues.apache.org/jira/browse/TAP5-1916
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Geoff Callender
>
> Tree would be much more usable if it responded to a Zone or page returned from the NODE_SELECTED and NODE_UN_SELECTED event handlers.
> This would address the most common use case for a tree: displaying a page with a tree on the left, user selects a node, the node highlights, and a zone on the right is updated with info from the server about the node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (TAP5-1916) Tree client should handle
Zone or page returned from events
Posted by "Geoff Callender (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263545#comment-13263545 ]
Geoff Callender edited comment on TAP5-1916 at 4/27/12 10:00 AM:
-----------------------------------------------------------------
Thanks Lance, understood. I've opened TAP5-1921 as a documentation request.
was (Author: geoffcallender):
Thanks Lance, understood. I'd like to change this to a documentation request.
Please add Lance's notes (above) to the the documentation. It's important info when it comes to understanding how to use the component.
* The doco also needs to describe how to achieve the most common use case (mentioned above).
* And the doco news to make clear that selectionModel is only needed for (in my opinion) an obscure use case - to select multiple leaves (and presumably submit them).
> Tree client should handle Zone or page returned from events
> -----------------------------------------------------------
>
> Key: TAP5-1916
> URL: https://issues.apache.org/jira/browse/TAP5-1916
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Geoff Callender
>
> Tree would be much more usable if it responded to a Zone or page returned from the NODE_SELECTED and NODE_UN_SELECTED event handlers.
> This would address the most common use case for a tree: displaying a page with a tree on the left, user selects a node, the node highlights, and a zone on the right is updated with info from the server about the node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1916) Tree client should handle Zone or
page returned from events
Posted by "Geoff Callender (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263545#comment-13263545 ]
Geoff Callender commented on TAP5-1916:
---------------------------------------
Thanks Lance, understood. I'd like to change this to a documentation request.
Please add Lance's notes (above) to the the documentation. It's important info when it comes to understanding how to use the component.
* The doco also needs to describe how to achieve the most common use case (mentioned above).
* And the doco news to make clear that selectionModel is only needed for (in my opinion) an obscure use case - to select multiple leaves (and presumably submit them).
> Tree client should handle Zone or page returned from events
> -----------------------------------------------------------
>
> Key: TAP5-1916
> URL: https://issues.apache.org/jira/browse/TAP5-1916
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Geoff Callender
>
> Tree would be much more usable if it responded to a Zone or page returned from the NODE_SELECTED and NODE_UN_SELECTED event handlers.
> This would address the most common use case for a tree: displaying a page with a tree on the left, user selects a node, the node highlights, and a zone on the right is updated with info from the server about the node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1916) Tree client should handle Zone or
page returned from events
Posted by "Lance (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260646#comment-13260646 ]
Lance commented on TAP5-1916:
-----------------------------
I think that you might have misunderstood what is considered "in scope" for the tree component to manage and what is left up to the developer:
1. The tree component keeps track of which "folders" are open and closed so that when you navigate away and come back, the tree state is maintained.
2. The tree component does not concern itself with leaf actions. A developer can customise leaf actions by specifying a "label" block which may contain a checkbox for example.
> Tree client should handle Zone or page returned from events
> -----------------------------------------------------------
>
> Key: TAP5-1916
> URL: https://issues.apache.org/jira/browse/TAP5-1916
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Geoff Callender
>
> Tree would be much more usable if it responded to a Zone or page returned from the NODE_SELECTED and NODE_UN_SELECTED event handlers.
> This would address the most common use case for a tree: displaying a page with a tree on the left, user selects a node, the node highlights, and a zone on the right is updated with info from the server about the node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (TAP5-1916) Tree client should handle
Zone or page returned from events
Posted by "Lance (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260646#comment-13260646 ]
Lance edited comment on TAP5-1916 at 4/24/12 3:21 PM:
------------------------------------------------------
I think that you might have misunderstood what is managed by the tree componentand what is managed by the developer:
1. The tree component keeps track of which "folders" are open and closed so that when you navigate away and come back, the tree state is maintained.
2. The tree component does not concern itself with leaf actions. A developer can customise leaf actions by specifying a "label" block which may contain a checkbox for example.
was (Author: uklance):
I think that you might have misunderstood what is considered "in scope" for the tree component to manage and what is left up to the developer:
1. The tree component keeps track of which "folders" are open and closed so that when you navigate away and come back, the tree state is maintained.
2. The tree component does not concern itself with leaf actions. A developer can customise leaf actions by specifying a "label" block which may contain a checkbox for example.
> Tree client should handle Zone or page returned from events
> -----------------------------------------------------------
>
> Key: TAP5-1916
> URL: https://issues.apache.org/jira/browse/TAP5-1916
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Geoff Callender
>
> Tree would be much more usable if it responded to a Zone or page returned from the NODE_SELECTED and NODE_UN_SELECTED event handlers.
> This would address the most common use case for a tree: displaying a page with a tree on the left, user selects a node, the node highlights, and a zone on the right is updated with info from the server about the node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (TAP5-1916) Tree client should handle
Zone or page returned from events
Posted by "Lance (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260646#comment-13260646 ]
Lance edited comment on TAP5-1916 at 4/24/12 3:22 PM:
------------------------------------------------------
I think that you might have misunderstood what is managed by the tree component and what is managed by the developer:
1. The tree component keeps track of which "folders" are open and closed so that when you navigate away and come back, the tree state is maintained.
2. The tree component does not concern itself with leaf actions. A developer can customise leaf actions by specifying a "label" block which may contain a checkbox for example.
was (Author: uklance):
I think that you might have misunderstood what is managed by the tree componentand what is managed by the developer:
1. The tree component keeps track of which "folders" are open and closed so that when you navigate away and come back, the tree state is maintained.
2. The tree component does not concern itself with leaf actions. A developer can customise leaf actions by specifying a "label" block which may contain a checkbox for example.
> Tree client should handle Zone or page returned from events
> -----------------------------------------------------------
>
> Key: TAP5-1916
> URL: https://issues.apache.org/jira/browse/TAP5-1916
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Geoff Callender
>
> Tree would be much more usable if it responded to a Zone or page returned from the NODE_SELECTED and NODE_UN_SELECTED event handlers.
> This would address the most common use case for a tree: displaying a page with a tree on the left, user selects a node, the node highlights, and a zone on the right is updated with info from the server about the node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (TAP5-1916) Tree client should handle
Zone or page returned from events
Posted by "Lance (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260646#comment-13260646 ]
Lance edited comment on TAP5-1916 at 4/24/12 3:21 PM:
------------------------------------------------------
I think that you might have misunderstood what is managed by the tree componentand what is managed by the developer:
1. The tree component keeps track of which "folders" are open and closed so that when you navigate away and come back, the tree state is maintained.
2. The tree component does not concern itself with leaf actions. A developer can customise leaf actions by specifying a "label" block which may contain a checkbox for example.
was (Author: uklance):
I think that you might have misunderstood what is considered "in scope" for the tree component to manage and what is left up to the developer:
1. The tree component keeps track of which "folders" are open and closed so that when you navigate away and come back, the tree state is maintained.
2. The tree component does not concern itself with leaf actions. A developer can customise leaf actions by specifying a "label" block which may contain a checkbox for example.
> Tree client should handle Zone or page returned from events
> -----------------------------------------------------------
>
> Key: TAP5-1916
> URL: https://issues.apache.org/jira/browse/TAP5-1916
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Geoff Callender
>
> Tree would be much more usable if it responded to a Zone or page returned from the NODE_SELECTED and NODE_UN_SELECTED event handlers.
> This would address the most common use case for a tree: displaying a page with a tree on the left, user selects a node, the node highlights, and a zone on the right is updated with info from the server about the node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1916) Tree client should handle Zone or
page returned from events
Posted by "Lance (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260646#comment-13260646 ]
Lance commented on TAP5-1916:
-----------------------------
I think that you might have misunderstood what is considered "in scope" for the tree component to manage and what is left up to the developer:
1. The tree component keeps track of which "folders" are open and closed so that when you navigate away and come back, the tree state is maintained.
2. The tree component does not concern itself with leaf actions. A developer can customise leaf actions by specifying a "label" block which may contain a checkbox for example.
> Tree client should handle Zone or page returned from events
> -----------------------------------------------------------
>
> Key: TAP5-1916
> URL: https://issues.apache.org/jira/browse/TAP5-1916
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Geoff Callender
>
> Tree would be much more usable if it responded to a Zone or page returned from the NODE_SELECTED and NODE_UN_SELECTED event handlers.
> This would address the most common use case for a tree: displaying a page with a tree on the left, user selects a node, the node highlights, and a zone on the right is updated with info from the server about the node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1916) Tree client should handle Zone or page
returned from events
Posted by "Geoff Callender (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Geoff Callender closed TAP5-1916.
---------------------------------
Resolution: Invalid
> Tree client should handle Zone or page returned from events
> -----------------------------------------------------------
>
> Key: TAP5-1916
> URL: https://issues.apache.org/jira/browse/TAP5-1916
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Geoff Callender
>
> Tree would be much more usable if it responded to a Zone or page returned from the NODE_SELECTED and NODE_UN_SELECTED event handlers.
> This would address the most common use case for a tree: displaying a page with a tree on the left, user selects a node, the node highlights, and a zone on the right is updated with info from the server about the node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira