Skip to content
This repository has been archived by the owner on Oct 2, 2019. It is now read-only.

Roadmap and design #3

Closed
ProLoser opened this issue Nov 7, 2013 · 32 comments
Closed

Roadmap and design #3

ProLoser opened this issue Nov 7, 2013 · 32 comments

Comments

@ProLoser
Copy link
Member

ProLoser commented Nov 7, 2013

I threw this together to pretty much scrape some features I am hoping this repo eventually is capable of doing: https://github.com/angular-ui/ui-select/wiki/Roadmap

One of the the things I'm focused on right now is easy-to-customize data, access to internal data, and templates.

One concern is the ability to specify a custom list-item template (currently possible) and a custom selected template (not possible, just uses a button). Perhaps we should break this up into multiple tags?

<ui-select>
  <selected></selected>
  <options>
    <li ng-repeat="..."></li>
  </options>
</ui-select>

These child-directives COULD in fact be optional, and if not specified, simply generate <li><a>{{value}}</a></li>

Secondly, if you don't specify <selected> or <options> but you DO specify a template we could use THAT one for both. Perhaps instead of making you create the <li> tag and it's related attributes we can do it for you and you simply specify the contents of each list-item and the selected-item?

@dimirc
Copy link
Contributor

dimirc commented Nov 7, 2013

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>

@ProLoser
Copy link
Member Author

ProLoser commented Nov 7, 2013

Not powerful enough to let you customize the list items.
On Nov 6, 2013 9:38 PM, "dimirc" [email protected] 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
.

@dimirc
Copy link
Contributor

dimirc commented Nov 15, 2013

@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

@ProLoser
Copy link
Member Author

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" [email protected] 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
Copy link
Member Author

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" [email protected] 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" [email protected] 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
.

@dimirc
Copy link
Contributor

dimirc commented Nov 17, 2013

@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.

@gabegorelick
Copy link

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

@j-walker23
Copy link

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

@pixelsailor
Copy link

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.

@leesei
Copy link

leesei commented Aug 8, 2014

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

@jverghese
Copy link
Contributor

+1 for multiselect. Is tagging on the roadmap?

@seiyria
Copy link

seiyria commented Oct 8, 2014

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

@ScrambledBits
Copy link

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.

@ghost
Copy link

ghost commented Oct 16, 2014

+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.

@jimmywarting
Copy link
Contributor

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.

@ProLoser
Copy link
Member Author

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

@jimmywarting
Copy link
Contributor

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

@brianfeister
Copy link

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

@xiangming
Copy link

We need Custom sorting / matching / filtering.
plz

@lasimon
Copy link

lasimon commented Dec 19, 2014

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.

@dubcanada
Copy link

+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."

@michaelhoes
Copy link

+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

@j-walker23
Copy link

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

brianfeister pushed a commit that referenced this issue Feb 16, 2015
@brianfeister
Copy link

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

@ghost
Copy link

ghost commented Mar 18, 2015

Hi, It is not working with angular verision: 1.2.10

@j-walker23
Copy link

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

@ashish612
Copy link

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

MartinNuc pushed a commit to MartinNuc/ui-select that referenced this issue Oct 7, 2015
@homerjam
Copy link
Contributor

Can I help with maintaining this repo?

@shyamal890
Copy link

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

@fru
Copy link

fru commented Jan 25, 2017

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

@Jefiozie
Copy link
Contributor

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

@Jefiozie
Copy link
Contributor

Jefiozie commented Mar 9, 2017

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 👍

@Jefiozie Jefiozie closed this as completed Mar 9, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests