Roadmap?

[softzer0]

First I must say that this thing saved me, so thank you for creating it! :+1: I mean, only AngularJS select directives that cooperate with Bootstrap (3) are yours and ui-select which is unfortunately in maintenance mode (i.e. with questionable future of development), too. I understand that there are not enough contributors here for some serious work, so I suggest you to put a precise roadmap and try to find people who are interested to continue with this project. Why? Because I think that this directive could be better than the mentioned one! Unlike ui-select, this worked perfectly fine with its ease of use and without any dependencies, and luckily it has fulfilled my needs for now, but I see that it needs to be improved to be concurrent with ui-router and eventually to replace it in the future, which I hope that it will. To be clear, I don't hate ui-router but I've seen that it's bloated and not functioning well when I've tried to use it for the first time, so I simply don't like it. But I like this, and it would be pity if it becomes abandoned.

Thanks for reading, and please take more care about the project! :)

[lordfriend]

No, there're no future plan for this project. In the early time, purpose of the project is implements similar features of bootstrap-select. But then it developed its own features and has some unique advantages. As the readme mentioned, This project is also into a maintenance state. Which means new feature will added.

But if you want to contribute, there are some work to do, in fact it's very hard to solve those issues without breaking compatibility.

• Live search is very slow when processing large data set. This caused by frequently change DOM. currently, live search using a special class to hide the options which not match the result and this cause a tremendous amount of rendering and reflow. But it is hard to add some virtual DOM operation and keep a non-isolated scope feature.(Well, I know non-isolated scope is not important)
• Dropdown toggle button is manipulated by some clunky code which make it hard to use template in option or default text. A typical scene is #137
• Data size feature is not properly implemented, sometimes it doesn't work as expected.
• Keyboard support is also a incomplete feature.

[GedMarc]

I've noticed on bootstrap 4 alpha 6 the drop down no longer appears, there's quite a few changes on drop down modifications, Is there any plan to migrate to bs4?

[lordfriend]

Sorry, no support for bs4. and no new feature will be added

If you're using a future bootstrap version. I suggest you to use angular2+bootstrap4. which has a lot more implementation.

[GedMarc]

Sadly not possible, Angular 2 fulfills a very different function to Angular 1. This widget you've made is perfect for portability across many environments, platforms, applications, mobile implementations as well as the very fast and rising server-side-only languages, which is what I'm using it for :) A think adding the extensability in a fork, and following the path JQX widgets took of simply porting A1.4 to @A2 in a single JSClass in the future is a stable mechanism for porting the widget in the future if needed :)

Thanks for this great and amazing widget!

[capesean]

Would you mind if I forked nya-bs-select and modified it to use Bootstrap4? I see it's MIT licensed, so as long as I keep the license / attribution, I presume that would be ok?

[capesean]

First attempt: https://github.com/capesean/nya-bootstrap4-select

Works well for me so far.