And the last, but not the least - InputAssist is now ready to be used in projects compiled against Flex 4.5 SDK - I just did some code trick due to the public API change in MatrixUtil.getConcatenatedMatrix method in Flex 4.5.

   My hands are scratching today to show you a preview of MaskedTextInput control for Flex 4 SDK that I've been working on.

   Currently only date mask in format "DD/MM/YY" is supported, but more to come.

   The last, but not the least announcement for today - I plan to create MaskedTextInput control that will be independent of Flex SDK too for all Flash platform developers to benefit from!

Please welcome the last update for InputAssist component in 2010 year!

Bugs fixed
---------
[!] Fixed issue when adding/removing dynamically items to dataProvider did not reflect in visual updating of the component;

[!] selectedItem cannot be set to the value that is not present in dataProvider;

[!] Setting "prompt dynamically does not reset displayedText;

[!] Updating the position of popUp with data items every time when available data list shrinks/expands;

Demo that illustrates correct behaviour:

internal API changes
------------
[*] private property _collection is now typed as ListCollectionView;

[*] Replaced internal HighlightItemListEvent.ITEM_CLICK event with ItemClickEvent.ITEM_CLICK event;

As always, the most recent source code of the component and compiled SWC library file is available at github.com/JabbyPanda/InputAssist

I wish you all Happy New 2011 year for the Flash Platform!

   Thus, today I am releasing my open-sourced component DateField4 that fixes a number of bugs and issues related to international dates and inline date editing.

   I've named my component DateField4, to emphasize the fact that this component is only meant to be used with Flex 4 SDK and beyond.

   Below is the demo that showcases the difference between DateField4 and 'halo' DateField.

   For example, you may notice, that 'halo' DateField does not support neither French nor Italian international date formatting even to display the date, oouch.

   The complete list of new features and bug-list fixes:

[*] Always enabled much improved custom validator for editable DateField that fully supports i18n dates;

[*] Limiting the data entry to "allowedFormatChars" value + numeric chars for editable DateField;

[*] Added "autoShowDropDown" property that controls when dropDown DateChooser menu is displayed;

[*] Pressing ESCAPE key resets the date selection to the previous value before DateField control had obtained a focus;

[*] Improved keyboard navigation for dropDown DateChooser menu when DateField is editable: RIGHT, LEFT, UP, DOWN, PAGE_UP, PAGE_DOWN key strokes are supported;

[!] Fixed SDK-23069 [Localization]: DateFormatter.parseDateString does not support non-latin characters in month and days names;

[!] Fixed SDK-23075 "[Localization]: DateField should support "MMM" and "MMMM" for formatString";

[!] Fixed SDK-26715 "DateFormatter "parseDateString" method cannot parse dateString value formatted with non default en_US format";

[!] Default width of DateField is wider by 4px to correctly display selected Date when moving cursor caret to the end of the text.

Public Git URL for this project is: https://github.com/JabbyPanda/DateField4

The only "new" feature is that InputAssist now supports dataProvider typed as ArrayList.

    Here is the full changelist for this release:

[!] Fixed issue with resetting visible "prompt" value when changing dataProvider
[!] Fixed issue by keyboard navigation by the help of Keyboard.UP and Keyboard.DOWN buttons
within option list if option list was closed and reopened.
[!] Items that had "-" or "+" symbols in its labels were not properly filtered
[!] Creating complete copy of passed ArrayCollection into dataProvider to avoid filtering of the original data source
[!] Fixed RTE when using InputAssist control within Adobe AIR app in "onFlexWindowActivate" event listener
[!] Started to use weak references when adding event listeners to avoid possible memory leaks
[!] "dataProvider" property now accepts data list typed as ArrayList.

As always, the most recent source code of the component and compiled SWC library file is available at GitHub

Short description of new features:

"processing" property
   Quite often the long data list is being loaded into InputAssist control asynchronously from remote destinations. Now InputAssist is able to display "hourGlass" icon during the data loading process by controlling "processing" property.

"errorMessage" property
    If InputAssist's dataProvider is currently empty, then there is nothing to be chosen from. Displaying "errorMessage" text and disabling the control gives the user the right UI feedback about the component state.

"prompt" property
   If no value is not selected yet via InputAssist control, the control can display text specified by the "prompt" value to explain what action is expected to be taken from the user side.

   Alternative usage of "prompt" property that I can think of - is to display the suppossedly selected current data object label which is not present in the InputAssist's dataProvider list == e.g. this selected data object is not valid and should be altered by the further user action.

And yes, sorry about long time delay to retrieve city list in the demo below, it is not a component fault, but long service time response from api.business.gov

Changelog for 0.12 release:
[+] Added property "prompt"
[+] Added property "errorMessage"
[+] Added property "processing"

[!] Fixed issue with dispatching InputAssistEvent.CHANGE event for nullable selectedItem
[!] Fixed issue with auto-completion by hitting ENTER key

http://github.com/JabbyPanda/InputAssist/

Demo:

Changelog for 0.1 release:

[+] Added style "highlightBackgroundColor" to InputAssist
[+] Added Ant build script
[+] Packaged as SWC library

[*] Changed classes namespace to match industry standard
[*] Changed the algorithm for the highlighting of matched text segments, thankfully to
Maxim Kachurovsky "Slov v sapogah" for an idea

[!] Fixed the appearance of popup list when "forceAuto" option is on and
system focus is moved back and forth between 2 different instances of FocusManager class.

This process get me a chance to think a little bit about component branding.

What I've recently had learned that AutoComplete is a very common name for the component with such a functionality.

I know, at least, 4 different Flash platform contenders, all of them use "AutoComplete" word in its name:

1. com.adobe.flex.extras.controls.AutoComplete control written for Flex 2;
2. Flextras commercial component AutoCompleteComboBox;
3. Hillel Coren's AutoComplete control;
4. And the last, but not least, the Flex 4 AutoComplete component written by Tenger Ivan.

While "AutoComplete" is a very strong brand and it is well known to the end users, I'd like to bring into Flex components naming world more creativity.

What if I will rename AutoComplete control to InputAssist? You see, my component not only "auto-completes", it is also providing an helping hand to faster select the value in need from the list of options.

So, in general, what do you think of InputAssist name?

   Disclaimer: My implementation of AutoComplete component is based on the revised codebase of AutoComplete 4 component originally created by Tenger Ivan from FlashCommander.org

   Two different search modes are supported : PREFIX and INFIX, to see the difference please play with the interactive sample file below.

   The auto-completion operation can be achieved in two ways: