ICEfaces
  1. ICEfaces
  2. ICE-9269

ace:autoCompleteEntry tutorial use textChangeListener

          Details

          • Type: Improvement Improvement
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 3.3
          • Fix Version/s: 4.1
          • Component/s: Sample Apps
          • Labels:
            None
          • Environment:
            selectInputText-tutorial
          • Assignee Priority:
            P2
          • Affects:
            Sample App./Tutorial

            Description

            The present tutorial uses the valueChangeListener, and doesn't use a value property, since those don't work with complex data types, like City in the tutorial. We should instead use a Converter, along with the value property, and only use the valueChangeListener as the notification of an actually completed selection. The textChangeListener is intended for being the mechanism for selecting items based on partially entered input.

            We could also illustrate startsWith substring matching in the basic mode, and contains substring match with a facet where the contains substring is bolded.

            ACE AutoCompleteEntry could also demonstrate these techniques.

              Activity

              Ascending order - Click to sort in descending order
              Mark Collette created issue -
              Mark Collette made changes -
              Field Original Value New Value
              Fix Version/s 3.4 [ 10770 ]
              Ken Fyten made changes -
              Summary ice:selectInputText tutorial use textChangeListener ace:autoCompleteEntry tutorial use textChangeListener
              Ken Fyten made changes -
              Fix Version/s 4.1 [ 11375 ]
              Fix Version/s 4.0.BETA [ 10770 ]
              Ken Fyten made changes -
              Assignee Carlo Guglielmin [ carlo.guglielmin ]
              Affects Sample App./Tutorial [ 10001 ]
              Assignee Priority P2 [ 10011 ]
              Hide
              Permalink
              Carlo Guglielmin added a comment -

              I checked the 9 ace:autoCompleteEntry demos in the showcase trunk, and the best practices talked about in this bug are already done there.
              We use textChangeListener where necessary (complex data types), and in other cases we don't even need it since the component has been improved enough since the initial 3.3 filing. Similarly we have a "Match Criteria" demo already which demonstrates the "substring matching" talked about in this bug.
              As a result I'm just going to resolve this one as Fixed already.

              Show
              Carlo Guglielmin added a comment - I checked the 9 ace:autoCompleteEntry demos in the showcase trunk, and the best practices talked about in this bug are already done there. We use textChangeListener where necessary (complex data types), and in other cases we don't even need it since the component has been improved enough since the initial 3.3 filing. Similarly we have a "Match Criteria" demo already which demonstrates the "substring matching" talked about in this bug. As a result I'm just going to resolve this one as Fixed already.
              Carlo Guglielmin made changes -
              Status Open [ 1 ] Resolved [ 5 ]
              Resolution Fixed [ 1 ]
              Ken Fyten made changes -
              Status Resolved [ 5 ] Closed [ 6 ]

                People

                • Assignee:
                  Carlo Guglielmin
                  Reporter:
                  Mark Collette
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: