What about using an attribute that accepts a comprehension_expression like ngOptions

Simple version

<ui-select options="email for user in users"></ui-select>

Or with child-directives for more flexibility

<ui-select options="user in users">
  <selected>{{user.email}}</selected>
  <options>
    {{user.name}} <b>{{user.email}}</b>
  </options>
</ui-select>

Not powerful enough to let you customize the list items.
On Nov 6, 2013 9:38 PM, "dimirc" notifications@github.com wrote:

What about using an attribute that accepts a comprehension_expression like
ngOptions

Simple version

Or with child-directives for more flexibility

{{user.email}} {{user.name}} {{user.email}}

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-27939050
.

@ProLoser I'm experimenting some approaches and will like to keep going pushing changes but not sure how to proceed since I didn't start this repo and wouldn't want push to master branch and maybe complicating your original roadmap. Let me know your opinion, maybe I could create my own repo and later we check back if we merge or something? Cheers

Add branches or multiple files. I am not married to my code and you are
free to trash all of it if you see fit.
On Nov 15, 2013 1:23 PM, "Wladimir Coka" notifications@github.com wrote:

@ProLoser https://github.com/ProLoser I'm experimenting some approacheshttps://github.com/angular-ui/ui-select/pull/8and will like to keep going pushing changes but not sure how to proceed
since I didn't start this repo and wouldn't want push to master branch and
maybe complicating your original roadmap. Let me know your opinion, maybe I
could create my own repo and later we check back if we merge or something?
Cheers

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-28604489
.

Also, I personally would prefer to see as little styling as possible. The
css and html used in select2 could be cleaned up but primarily I would like
to see approximate structure in the base stylesheet and then we can provide
optional "themes" such as select2 or bootstrap dropdown in additional
stylesheets.

Secondly, the ability for the stylesheet to work depends primarily on the
html structure, so one of the earliest goals should be to make the
directive as structureless as possible. Build a version where you are
forced to specify a custom template, then create secondary directives or
templates that people can choose to use instead. These secondary templates
can give people the option of a bootstrap structure or select2 structure,
etc.

Hopefully that makes sense. I'm pushing this same approach on the ng-grid
rewrite.
On Nov 15, 2013 2:03 PM, "Dean Sofer" deansofer@gmail.com wrote:

Add branches or multiple files. I am not married to my code and you are
free to trash all of it if you see fit.
On Nov 15, 2013 1:23 PM, "Wladimir Coka" notifications@github.com wrote:

@ProLoser https://github.com/ProLoser I'm experimenting some approacheshttps://github.com/angular-ui/ui-select/pull/8and will like to keep going pushing changes but not sure how to proceed
since I didn't start this repo and wouldn't want push to master branch and
maybe complicating your original roadmap. Let me know your opinion, maybe I
could create my own repo and later we check back if we merge or something?
Cheers

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-28604489
.

@ProLoser I agree that "themes" will be a nice feature, but maybe we can focus on one style for now and later add this ability. Take a look at some changes I committed just a moment ago. To be honest I'd like to have a fully functional directive asap since its really needed it in a working project that I'm right now, so let me know your comments of the changes I did and what do you think of merging to master and keep going with that.

I see multiselect is on the roadmap. Any idea when that will be implemented?

^ @gabegorelick. I would like to throw away select2 for this, one day hopefully!

Getting this to work with Angular 1.2.* has been a pain in the arse. Any thoughts about updating the plunker demo and fixing the $sce errors? I haven't been able to figure out how to get the highlight custom filter to work as a result.

👍 for implementing multiselect.
I can say goodbye to select2 then.

+1 for multiselect. Is tagging on the roadmap?

+1 for multiselect, +10 for tags, +100 if it also supports editing tags a la https://github.com/ivaynberg/select2/issues/116

Is there an option to add a call to action in the event that the specified option is not among the ones the select is constructed on?

e.g. Add the option to add an element to the list in the event it does not exist already.
I've been reading the examples and documentation on the internet and can't find anything yet.

+1 for JohnQ's question. I was looking for the same ability to be able to add new options even if they are not present in the list, but user just types them in.

Editing tags, ajax result... what is next? fells more like it is turning out to be a Typeahead thing. kind of beats the purpose of being a select with static options.

@jimmywarting technically this was a continuation of select2, which I think may have been around before typeahead.

Don't have anything against it... maybe the only thing you will need to include then is this tool

@seiyria @jverghese Tagging functionality is in PR #327, FYI. Hoping for it to be merged soon.

We need Custom sorting / matching / filtering.
plz

Is there a way to do the equivalent of ui-select2's createSearchChoice? I need to allow a person to enter a name if it isn't in the list of existing options.

+1 for "Is there a way to do the equivalent of ui-select2's createSearchChoice? I need to allow a person to enter a name if it isn't in the list of existing options."

+1 for "Is there a way to do the equivalent of ui-select2's createSearchChoice? I need to allow a person to enter a name if it isn't in the list of existing options." or the selectize 'item Creation' function

+1. Just hacked the tagging feature to give this kind of behavior, lol wasn't pretty. +1 for this and thanks for tagging!

@j-walker23 @michaelhoes @dubcanada @lasimon This is available in v0.9.8.

Hi, It is not working with angular verision: 1.2.10

Thank you @brianfeister, you guys are the difference between a shitty day programming and a smooth day.

Does select2 support using matchers (finding all the texts starting with) like the jquery select supports?

Can I help with maintaining this repo?

@homerjam Talk with @aaronroberson he is the one maintaining the library now I think.

First of all thanks everyone for this awesome component! Are there any plans to port this to angular 2? Is help wanted in that area?
p.s. There already is a stackoverflow question on the subject: http://stackoverflow.com/questions/37921979/ui-select-replacement-in-angular2

@fru I don't think there are any plans on angular 2 yet. At the moment we are trying to handle all the bugs.

Closing it down as it is a very old issue for now this repo is focusing on handling the bugs.
Trying to get a grip on the bugs that are relevant to bugs in the newer versions of ui-select.
Help is welcome 👍