This will not be added to Toolset Views as a core feature if this is what you mean.
Let me explain why:
- assume we add this library
- it is a beautiful, and powerful library, but:
-- another user will discover or use already a "nicer and more powerful" (maybe just in their opinion) library
-- users will want to customise this and will ask for it through Toolset (even thou, it would be an external library just like Bootstrap)
These are the main reasons we do not add "nice" libraries like Select2, or this one.
We would satisfy only a few people, but add a large code piece, which needs maintenance and also may fail (what if the 3rd party stops developing, or updates, etc)
That is what leads Plugin and Theme developers to rely as much they can on WordPress only, and not on any other independent script or library (often impossible, but that is somehow the first thought when you talk "3rd party libraries": updates and compatibility).
Now, I assume you can add most of that library manually and apply it to Views using its classes, but, this would fall under the custom code, and there may be a few conflicts with our own AJAX updating mechanism.
What is the problem most often is, that after enqueueing the JS and CSS codes, applying them to your HTML, and updating a View with ur AJAX filters, the JS of the 3rd Party suddenly stops working?
This is because our AJAX call needs to re-fire the 3rd party JS after our search is done.
For that, we added JS Hooks to the JS Editor of the "Custom Filter" section in every View.
There, you might re-hook your JS functions, which will fire the 3rd party JS again.
We cannot provide much code examples for this, but I wanted you to know the feature is there, in case you will try to add this manually and run into issues with ajax updated views.
I filed the request, added your voice, and will upvote it as comes, but i cannot guarantee for above reasons that this will be considered.
