Click
  1. Click
  2. CLK-186

Implement client side javascript functionality for tree control

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: examples, extras
    • Labels:
      None

      Description

      Add javascript functionality to the tree control.

      Features should include:

      1) ability to expand/collapse nodes
      2) after a server round trip, the currently selected nodes should still be displayed in browser. The tree should not collapse unto itself after a submit

        Activity

        Henri Yandell made changes -
        Project Import Fri Mar 20 14:11:32 PDT 2009 [ 1237583492744 ]
        Malcolm Edgar made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Bob Schellink made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Hide
        Bob Schellink added a comment -

        Tree client side behavior added. Both server and cookie policies supported now.

        Show
        Bob Schellink added a comment - Tree client side behavior added. Both server and cookie policies supported now.
        Hide
        Bob Schellink added a comment -

        This feature has been checked in. The javascript support is session based. To ensure the selected nodes are visible in the browser, the selected node id's are stored in the session. This enables one to recalculate which nodes should be rendered as expanded on the client side.

        Another approach is to use cookies to track the expanded and collapsed nodes. Advantages of this approach is that the session stays clean, and it enables one to inform the server exactly which nodes should be expanded instead of calculating it from the selected nodes. I am adding cookie support after the 1.2 release.

        Show
        Bob Schellink added a comment - This feature has been checked in. The javascript support is session based. To ensure the selected nodes are visible in the browser, the selected node id's are stored in the session. This enables one to recalculate which nodes should be rendered as expanded on the client side. Another approach is to use cookies to track the expanded and collapsed nodes. Advantages of this approach is that the session stays clean, and it enables one to inform the server exactly which nodes should be expanded instead of calculating it from the selected nodes. I am adding cookie support after the 1.2 release.
        Bob Schellink created issue -

          People

          • Assignee:
            Bob Schellink
            Reporter:
            Bob Schellink
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development