I think it would be great if there were an AutoComplete component built into Flex, but I do have some reservations with this approach. The biggest issue from my point of view is that one company/person would decide what the basic implementation will be, possibly making it harder for us to add the things we need later on. I've put quite some hours in the development of my own Spark AutoComplete component (https://github.com/RIAstar/AutoCompleteFx) because I couldn't find any components that did what I needed them to do, so I know a little about this topic too. It can be a complex component with tons of possibilities.
For instance: for an AutoComplete component to be truly compatible with the existing Flex framework, I believe that its API should be as similar as possible to a List component (i.e. it must expose 'selectedItem', 'selectedItems', 'selectedIndices', etc. properties). If this kickstarter project decides to implement the component otherwise, it might be very hard to add this later on. To me it feels a bit like going back to the days that Adobe decided on the basic implementation and we were allowed to give some feedback. I must admit that feeling comes from the fact that I've put in a lot of hours myself, and I may not have anything to say in this project, unless I donated some money to the kickstarter project. Somehow that doesn't feel right. Max On Wed, Nov 14, 2012 at 5:38 PM, Jeffry Houser <jef...@dot-com-it.com>wrote: > > Thanks Mark for the plug. I was just about to post my own announcement. > > > On 11/14/2012 10:41 AM, Jonathan Campos wrote: > >> It just seemed like some of the wording was off. >> There seemed to be an assumption in the text that whatever was developed >> would be definitely accepted into the Apache Flex project. >> > I was very careful with the wording; but perhaps I failed. > There is no guarantee that it would be added to the base framework; but I > don't see how the donation could be rejected. > > > Furthermore it >> said that only the "finished" component would be added. What constitutes >> finished? >> > The text of the Kickstarter provides a list of explicit features that > will be implemented; and those features are the base line that constitute > finished. > > > There didn't seem to be that interest in feedback and open development. >> > > It was not my intent to give that impression. For backers; I'll be > hosting routine sessions for the purpose of showing progress and soliciting > feedback. > > > -- > Jeffry Houser > Technical Entrepreneur > 203-379-0773 > -- > http://www.flextras.com?c=104 > UI Flex Components: Tested! Supported! Ready! > -- > http://www.theflexshow.com > http://www.jeffryhouser.com > http://www.asktheflexpert.com > -- > Part of the DotComIt Brain Trust > >
