Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
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.
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
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
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.