[
https://issues.apache.org/jira/browse/TAP5-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-1921:
---------------------------------
Labels: bulk-close-candidate (was: )
This issue affects an old version of Tapestry that is not actively developed
anymore, and is therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent version of Tapestry (currently
5.4.0, available from Maven Central), please update it as soon as possible and
add '5.4.0') to the issue's affected versions.
> Tree's standard use case needs to be documented
> -----------------------------------------------
>
> Key: TAP5-1921
> URL: https://issues.apache.org/jira/browse/TAP5-1921
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Geoff Callender
> Labels: bulk-close-candidate
>
> While developing Tree examples for JumpStart it became apparent that the
> existing documentation gave no clue as to how to use Tree in the most common
> way:
> * Display 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.
> Answers on the mailing lists showed that I was not alone.
> I think the documentation would be improved a lot by drawing on Lance's
> comments in TAP5-1915 and my text in
> http://jumpstart.doublenegative.com.au/jumpstart/examples/ajax/treefromdatabasewithzones
> (as of JumpStart v5.7.4).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
