Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

md-autocomplete #117

Closed
jelbourn opened this issue Feb 27, 2016 · 39 comments
Closed

md-autocomplete #117

jelbourn opened this issue Feb 27, 2016 · 39 comments
Assignees
Labels
feature This issue represents a new feature or feature request rather than a bug or bug fix new component This issue is tracking a new component to be added to the library
Milestone

Comments

@jelbourn
Copy link
Member

Blocked on both #113 and #84

@jelbourn jelbourn added the feature This issue represents a new feature or feature request rather than a bug or bug fix label Feb 27, 2016
@jelbourn jelbourn added this to the before beta milestone Feb 27, 2016
@jelbourn jelbourn mentioned this issue Feb 27, 2016
@jelbourn jelbourn changed the title mdAutocomplete md-autocomplete Feb 27, 2016
@jelbourn jelbourn added the new component This issue is tracking a new component to be added to the library label Feb 27, 2016
@pramttl
Copy link

pramttl commented Jun 29, 2016

Any updates on this?

@michaeljota
Copy link

Hi! If both issues are close, how this is not being updated? Is it being developed?

@EladBezalel
Copy link
Member

It's in early stages of development

@michaeljota
Copy link

Thanks you! 😄

@drew-codes
Copy link

Is regarding autocomplete support on popular text editors?

@topherfangio
Copy link
Contributor

This issue is in regards to the Material Autocomplete which you can view at https://material.google.com/components/text-fields.html#text-fields-auto-complete-text-field.

@ioandr
Copy link

ioandr commented Oct 21, 2016

is there an estimation regarding the release ? thanks a lot!

@nkwood
Copy link
Contributor

nkwood commented Oct 21, 2016

@EladBezalel @topherfangio Is there anything on md-autocomplete that might be good for community contribution at this time? I didn't see anything on md-autocomplete in the design documents, except for the references in the design doc for md-input and the hooks in md-input.

I think there may be a few people that are willing to contribute here, but if there has already been significant design progress that hasn't made it into the publicly available design docs it doesn't make any sense to duplicate that effort.

@topherfangio
Copy link
Contributor

@nkwood We are currently still in the design phase for this component and are trying to come to a consensus on the structure and API we plan/want to support.

@creativedeveloper-net
Copy link

if someone needs autocomplete made in Angular 2 you can have a look here:
https://github.com/creativedeveloper-net/angular2-autocomplete
here is a plunker demo:
https://plnkr.co:443/2aL2Ju
I've made it based on examples from here:
http://stackoverflow.com/questions/35881815/implementing-autocomplete-for-angular2/

Feel free to update/improve it

@michaeljota
Copy link

@creativedeveloper-net I can see the list of the possible values, however I'm unable to select any.

@creativedeveloper-net
Copy link

@michaeljota thanks for the input, could you please add it as an issue here:
https://github.com/creativedeveloper-net/angular2-autocomplete/issues
and please describe which browser do you use etc thanks in advance

@alan345
Copy link

alan345 commented Dec 15, 2016

is there an estimation regarding the release ? thanks a lot!

@kkjf02
Copy link

kkjf02 commented Dec 15, 2016

is there an estimation regarding the release ? thanks a lot! (2)

@daBishMan
Copy link

is there going to have the ability to add new items that are not part of the suggestions ? or you can only select what is in the "Suggestions". I would prefer if we have the ability to do both?

@MarcusCalidus
Copy link

it would be cool if one could bind to the current input value. Currently I am using md2-autocomplete by @dharmeshpipariya
But since it is not possible to get the input value from there I use jquery events
userChange(event: JQueryEventObject) { if (event) { this.userInputText = $(event.currentTarget).val().toLowerCase(); this.onChange(event); } }

To have a "new item" item would be awesome like here: https://material.angularjs.org/latest/demo/autocomplete

@kara
Copy link
Contributor

kara commented Dec 27, 2016

Design doc: https://docs.google.com/document/d/1c9e9-5HlOFKqmdq147yugAQroMLfOeGdRGyB1JGxKVE/preview

@bendg25
Copy link

bendg25 commented Jan 9, 2017

Is there an early release of this available?

@elvisbegovic
Copy link

any ETA?

@elvisbegovic
Copy link

I'm trying to implement autocomplete (for personal use):
https://gist.github.com/istiti/225c29afee646da66224b3388c9b52d9#file-autocomplete-directive-ts-L53

Why I can't change my input model from my directive ? How can I achieve this ?

Thanks

@ehegnes
Copy link

ehegnes commented Jan 18, 2017

@bendg25 Please consider tracking changes to the code to determine release progress. This GitHub search query may help you.

@istiti, @alan345, @kkjf02 ETA inquiries are generally not conducive to improving development efforts.

@istiti With respect to your autocomplete implementation, please consider posting such questions to another platform (Stack Overflow, for example). Your implementation is not germane to this issue.

@kara
Copy link
Contributor

kara commented Jan 19, 2017

Also worth noting anyone who's interested can follow the autocomplete board here.

@alan345
Copy link

alan345 commented Jan 20, 2017

@kara Thanks Kara

@sobvan
Copy link

sobvan commented Jan 30, 2017

Hello, the material2 repo seams quite silent. Is there an ETA for this?

@elvisbegovic
Copy link

It's always silent even with new employees going team !!!

@jelbourn
Copy link
Member Author

I wouldn't exactly call the activity on master or on the autocomplete branch "silent".

@alirezamirian
Copy link

I really love how in Material 2 Autocomplete is not a black box component hiding the underlying input.
I was about to add a link to this issue, and then I saw this commit.
Thank you guys 👍

@sobvan
Copy link

sobvan commented Feb 9, 2017

Guys, you can add thumbs down to the questions about ETA.

I really appreciate the hard work you guys put in Material 2, and I did not intend to hurt your feelings, I just really would like to know your plans on releasing autocomplete.

I guess Google is not doing Angular only out of generosity. Google wants developers to use their stack instead of React, and maybe even contribute code to Angular.
Angular 2 without Material 2 is simply not production ready. Material is THE ui recommendation of Google. This is why I (and many another developer) think that Material 2 library would need more resources.

@EladBezalel, honestly how could I understand your project management and generally just how the Material 2 team works, and what you work on? I based my view about autocomplete being silent on the kanban board you maintain for this feature.

We have projects that clients are waiting for. One happens to be blocked on autocomplete. I have to tell them something. So guys, do you have an estimated ETA for autocomplete? :)

@michaeljota
Copy link

michaeljota commented Feb 9, 2017

@istvanszoboszlai Why? Why even ask for an ETA? Every of us have their own schedule (Even Angular team, and it is public, you can track their doing in the "Milestone" section of the issues), but you can't count with something that does not exist.

Beside the one mention to the "Milestone" section, the readme explicitly show this as a BETA, and it should NOT be used in production. I use it. You use it. Most of us are using it. But, we have to be grown up here, this is not yet ready. We have to wait. There are plenty of choice if you need an UI framework.

I'm sorry if I'm being rude, but when I get a notification about this I'm expecting that update to say "It's available guys, test it", but instead a found another post about "They should say when it will be ready", spoiler: They don't know. They are people, like us.

You can help. The code it's available, glob, there is even a branch just for the autocomplete. 😄

@sobvan
Copy link

sobvan commented Feb 9, 2017

@michaeljota, I think you were definitely not rude.
Every software team has plans. I am simply curious about that. Maybe I miss something, but I cannot find up-to-date plans on this project. The milestones section is not up-to-date. So I cannot rely on that.
I am using Material2 with https://github.com/Teradata/covalent right now. They maintain nice documentation on their progress, and if I ask ETA than they simply answer.

@michaeljota, what I am really interested in: Which Angular2 UI framework do you think is there to choose? I know of none that is built with native Angular 2.

@michaeljota
Copy link

michaeljota commented Feb 9, 2017

Like I say, they have a branch about autocomplete:

@jelbourn: I wouldn't exactly call the activity on master or on the autocomplete branch "silent".

For the others UI for Angular, one of the most complete support would be NgPrime, but for a most complete list, in Angular's website, in the resources section you can find many libraries for UI composition.

@sobvan
Copy link

sobvan commented Feb 9, 2017

Sorry for offtopic posts, this is my last.
I did do my homework about half a year ago and there is not much change in the UI framework landscape.
PrimeNG is an Angular 2 wrapper over their jquery based UI elements. Not exactly native Angular 2.
On the other hand, look, even react has a mature, and awesome material UI library: http://www.material-ui.com/

I think Material 2 is the most important entry point for new users of Angular 2, and still - as awesome as it is - it is not treated as an extremely important project inside Google. This is pretty much a pity, IMHO.

@elvisbegovic
Copy link

elvisbegovic commented Feb 9, 2017

@istvanszoboszlai reactmeaterial is 1.5year older than material2. but i agree with you !mateirla2 team need more resources-employes or so!! no news and very slow from google devs

@michaeljota
Copy link

You should notice that material-ui it's just an open source project, without any big company behind. So, why do you request more resources in an open source project with a big company behind? Instead you should just support the project, if you like. I think it's kind of unfair to request "more devs" from "google" cause this is a "google project". We all are just devs here. This still just another OSS. So, act alike.

@elvisbegovic
Copy link

Lol open source=open ok but when I start a project using this techno or when I join a team using this techo we aren't so free as you thnk! We depends! Before mask all behind opensource explain why these project are open why android is open if no profits?! stop telling opensource here! Its troll. I continue to think here need more resources to fight and be the most used fw

@ehegnes
Copy link

ehegnes commented Feb 9, 2017

@jelbourn I hope I am not out of line when requesting this, but may this issue kindly be locked to collaborators only? This way the issue may constructively track progress without the overhead of accumulating inflammatory remarks.

@kara
Copy link
Contributor

kara commented Feb 9, 2017

Update: The initial version of autocomplete is getting pretty close. At this point, it's bare bones but usable. We are just ironing out any last bugs that come up. I can't give you an exact date when it will be available, but it will definitely go out with our next beta release (soon!).

@ehegnes I try to avoid closing threads because we do like hearing from the community, but I think you're right that this one is getting derailed a bit. I'm going to lock it for now. But if anyone wants to comment on potential bugs or feature requests for the autocomplete, please feel free to file a separate issue.

@angular angular locked and limited conversation to collaborators Feb 9, 2017
@EladBezalel
Copy link
Member

@kara i know it's locked but i have to reply to this one -

@istvanszoboszlai @istiti you should listen to @michaeljota,
I joined the material team a year and a half ago after contributing for more than a year to AngularJS material, I did it on my own free time and if I had an issue or a feature suggestion i opened issues and did PRs so not only i'd benefit from it, the entire community will.

It's super rude and egoistic to say - Google should put more devs on that cause they're probably using it - this project, as the Angular project is open-source, if you use it, contribute! don't demand that some company would throw more money over your problems!

If the company you work for doesn't understand the open-source community and how it's about to share and contribute, you should teach them or leave.

I get why people ask for ETA, but i don't get why some take this project or the people working for it as granted.

@kara
Copy link
Contributor

kara commented Feb 17, 2017

Closing this, as the initial version of autocomplete is out in beta.2. We'll track future features in separate issues.

@kara kara closed this as completed Feb 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature This issue represents a new feature or feature request rather than a bug or bug fix new component This issue is tracking a new component to be added to the library
Projects
None yet
Development

No branches or pull requests