• About
• AIR Applications
  • ImageSizer
  • Screentweetr
• Blog
• Contact

Psyked *

it’s easy once you know how.

Link: Flex AutoComplete component

Posted by James - 11/01/10 at 03:01:20 pm

If you’re ever looking for an autocompletion component in the Flex framework, I’d strongly suggest you check this one out: http://hillelcoren.com/flex-autocomplete/ Quite simply it’s awesome, it’s fully featured and packs a helluva lot of options into such a small package.

I swapped an old ComoBox component for it just now, and it worked fantastically with no additional configuration.

Check out the demo for it here: http://web.me.com/hillelcoren/Site/Demo.html

11 Comments »

1. 

   If you’re looking for a Flex AutoComplete that comes with support, you can check out ours at:

   http://www.flextras.com/?event=ProductHome&productID=10

   It is based on the Combobox so, is a slightly different take than Hillel’s.

   Comment by Jeffry Houser — 11 January 2010 #

2. 

   We also have one of these as the hillelcoren one was too complex for our needs.

   http://www.tink.ws/blog/filtercombobox/

   Comment by Tink — 11 January 2010 #

3. 

   Thanks guys, I’ll check both of those out also – there’s another couple of situations where a ComboBox-based solution would be more suitable.

   Comment by James — 11 January 2010 #

4. 

   Let me know if we can answer any questions that you have. Ours can easily revert to an AutoCompete TextInput by just removing the down arrow via a property (I believe downArrowVisible ).

   If you’re dealing with large data sets, but don’t want to load the data all at once, we support the pinging of a database, and replacing the dataProvider after each call.

   As always, we’d welcome any feedback that you’d have.

   Comment by Jeffry Houser — 11 January 2010 #

5. 

   In the same wat, setting ‘arrowButtonWidth’ to 0 would make ours look like a TextInput.

   Personally I recommend access to a DB through a command and storing the data in a model, then bind the FilterComboBox to the data.

   Comment by Tink — 11 January 2010 #

6. 

   Tink,

   Not sure if that last comment was directed at me or not; but just to be clear; there is nothing about our AutoCompleteComboBox that prevents that approach, even if you are using our “RemoteData” option or not.

   I believe that encapsulation is important to the long-term maintainability of a code base; and encapsulating the data access functionality seems like a no brainer.

   Comment by Jeffry Houser — 11 January 2010 #

7. 

   It was aimed at you as a diss mate, was just commenting on how I would recommend managing data and serverside calls (i.e. I wouldn’t do this from inside view components).

   Comment by Tink — 12 January 2010 #

8. 

   LOL “wasn’t”

   Comment by Tink — 12 January 2010 #

9. 

   Tink; In that case I agree completely.

   Comment by Jeffry Houser — 12 January 2010 #

10. 

    Thanks for the comments guys, got a bit tense there!

    In the end I actually ended up using Tink’s FilterComboBox component – the original one was great but the multiple selection stuff was throwing a spanner in the works.

    Comment by James — 12 January 2010 #

11. 

    James,

    I you took a look at the Flextras AutoCompleteComboBox; I’d welcome any feedback.

    Feel free to contact me privately if that is your preference.

    Comment by Jeffry Houser — 12 January 2010 #

Leave a comment

Name (required)

Mail (will not be published) (required)

Website

XHTML: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Note: This post is over 7 months old. You may want to check later in this blog to see if there is new information relevant to your comment.

Notify me of followup comments via e-mail.