Hi Martin,

No, no further features required at this point. With your help, key-press handling override as well as other functionality were set up with a customised MultiSelect.

Thank you.

Hi Martin,

Yes, this is looking like functionality that can be achieved easily enough through widget configuration and event logic in something like the existing MutliSelect.

I have just re-implemented something similar to me example with the MultiSelect widget to use as a custom parameter editor for cases of multi-value string/numeric parameters that have no "available" values, allowing users to filter by an arbitrary list of values or key-phrases. Using direct jQuery initialisation avoided working around MVVM observable members. Adding handling for "Ctrl-<enter>" etc. type key-presses is something I'll still need to work out.

"option Popup list" is just the value list of the MutiSelect - I understand a "popup" is a component wdiget for this.

Thank you,

Steven

Hi Neli,

I mentioned a ListView as I imagined that it might be a better candidate on which to base my suggested widget functionality, but now I am more familiar with the MultiSelect widget, it could work well as a starting point. I defer to your/Teleriks expertise on Kendo widgets as to whether the suggested functionality would be a worthwhile extension of MultiSelect or ListView functionality or even something to develop as a new widget.

As to the suggested features, I refer again to my rough example on dojo (email input, separators: [",", ";", " "] , RegEx check).

The main widget features:

• the widget functions primarily as a "free text" input, supporting the collection/capture of multiple string values into a list/datasource
• has a configurable functionality to separate input text sequences as separate values, e.g. a separator character such as a space or comma
  • options such as key sequence like "Shift-Enter" might be useful in addition to a configurable character
• as text is typed, the separator key-press triggers the input of the existing text - adding it as a new entry to the widget's input list
• input values are displayed as tags, like with the MultiSelect

Further desirable features:

• for editing some existing records in a form, support binding to existing data
  • new text values are added
  • by default, duplicates are not added
  • text input filters existing values
• support binding a collection of "available values" - but not as a limiting set of values
  • the widget will be bound on initialisation to a union of an optional base set of "known values" and any values previously selected for the data field being edited
  • "known values" - useful or previously used values
    • e.g. email addresses: a user can select from known addresses while still adding new ones
  • when initialised for editing an existing data field, these previously selected fields are selected in the widget
  • new free text values are added to the select list and remain if deselected - easy to reselect
• support rich, object values, where the text value is a primary field
  • e.g. email addresses: known addresses can have a "display name" and picture URL that can be shown in item templates, but the address field is the primary data field. RegEx pattern match can be bound to field that is used in the item template styling
    
• support an optional "Popup" list like that in the MultiSelect
• support tag and popup list item templates
• optional RegEx pattern that can reject invalid values
  • or optionally, non-matched items can be added, setting a boolean "matched"/"valid" attribute/property against the input value

Perhaps this is a little too easily implemented with a standard MultiSelect, but for my email input example, at least, this did not seem clean or simple to achieve with MVVM initialisation.

Thanks,

Steven

Hi Martin,

Apologies if I wasnt clear. Also, as Im not too practised on Kendo UI, there was a level of guess work without much further investigation on my part, to the feasibility of a better implementation using an existing widget.

The main point was that if this "list input" idea could be implemented easily enough using an existing widget (possibly ListView), I can understand that you would not want to implement a new widget - and additionally, in that case, maybe such an implementation might make a useful example on your demos or documetation for that widget.

Hi Martin,

This originated as I wanted to have an email list input that was better than a text field with comma separated email addresses.

Seeing how some email clients support a dynamic input box that supports text input and renders values in a formatted tag/box - and that similar inputs are used for things like category tag lists for online posts etc, it seemded a good idea for a new input control. This could be potentially data bound to existing data for an "available" values list as well as the current "selected" list and potentially support input of "new" items not in the available list. Though the idea was to work with a simple list of strings and so just work with a simple array output.

I implemented something similar to the linked dojo example. After some further thought, I was guessing that maybe something similar could be better implemented in a ListView. So unless this would be suited to a new control, maybe something like this could be added as an example ListView implementation in documentation or the Demo area.