Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.5
    • Component/s: wtk
    • Labels:
      None

      Description

      Data binding should be more robust. It should support a configurable two-way mapping using a bind type of LOAD, STORE, or BOTH, and should support binding to model data as well as selection state in data-driven components. The following components should be updated:

      Button
      Calendar
      CalendarButton
      ColorChooser
      ColorChooserButton
      Label
      ListButton
      ListView
      Spinner
      TableView
      TextArea
      TextInput
      TreeView

      Additionally, data binding events should be moved to their own interfaces, as the addition of these new bound properties will create a number of new data-binding related events.

        Activity

        Hide
        Greg Brown added a comment -

        All components have been updated with the exception of:

        ColorChooser - needs bind mapping, bind type, and bind listener interface
        ColorChooserButton - needs bind mapping, bind type, and bind listener interface
        TreeView - needs tree data and selected node/nodes keys, bind mappings, bind types, and bind listener interface

        Show
        Greg Brown added a comment - All components have been updated with the exception of: ColorChooser - needs bind mapping, bind type, and bind listener interface ColorChooserButton - needs bind mapping, bind type, and bind listener interface TreeView - needs tree data and selected node/nodes keys, bind mappings, bind types, and bind listener interface
        Hide
        Todd Volkert added a comment -

        ColorChooser and ColorChooserButton have been done

        Show
        Todd Volkert added a comment - ColorChooser and ColorChooserButton have been done
        Hide
        Todd Volkert added a comment -

        Skipped TreeView because it's not clear that binding to a tree view is a common use case that warrants supporting. Further, there is no TreeView.setSelectedNode() right now because of the inherent inefficiency of the pathOf() method.

        Thus, this ticket is done.

        Show
        Todd Volkert added a comment - Skipped TreeView because it's not clear that binding to a tree view is a common use case that warrants supporting. Further, there is no TreeView.setSelectedNode() right now because of the inherent inefficiency of the pathOf() method. Thus, this ticket is done.

          People

          • Assignee:
            Todd Volkert
            Reporter:
            Greg Brown
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development