DataTables VS select2

I've done quite a bit of scouting for a solution, and it looks like many people gravitate around django-tables2, https://www.datatables.net/, https://bootstrap-table.com/, and a few others. The latter two are JS/HTML frameworks that can accept either Django templated HTML (of a table) or JSON, and they seem to prefer JSON to give you the most access to features.

If you’re only trying to not show 2000 results to the user at once, you could send them all and then use front-end techniques to paginate (a JS table library, for instance).

Don't know the plugin, but it looks like just a WordPress wrapper around the https://www.datatables.net/ datatable plugin. That plugin is very powerful and popular, there are many plugins for it too, pretty sure you can easily find a front-end developer to make the search more powerful.

I'm using datatables for displaying server-side data in tables.

I am using DataTables to create a table that is able to dynamically filter context. I am following the basic example, here.

I am trying to work with jQuery's Datatable JS for my project from this link.

I am using the jQuery DataTables plugin to sort the table fields. My question is: how do I disable sorting for a particular column? I have tried with the following code, but it did not work:

Great, currently I am using the Datatables from https://www.datatables.net, have a hard time with column fiiltering plugin (yadcf). Keep on!

The design called for a grid of 12 cards that could be paginated, searched, and selected. For instance if we have 32 cards, on multiple pages, we needed to be able to select all the cards, and on submit, persist 32 cards to the need controller action. After reviewing the specification, we decided to use DataTables, which we have already used throughout this Rails 5 application.

Most people using react aren't building SPAs. Vue/React can be used the same way as jquery, which is to add enhanced UI functionality that server-side HTML views simply can't offer.

The best example is a multi-select box, or a searchable select box with autocomplete (what W3 calls the combobox pattern https://www.w3.org/WAI/ARIA/apg/patterns/combobox/) which in jquery was usually via https://select2.org/

For example, on my company website there's a timezone select box with are 151 options. Asking a user to simply scroll through 100+ to find theirs is annoying vs typing a few characters and hitting enter.

There's many examples of select boxes like that and there really is no static server-side way to solve this problem (I tried hard to think of one)... without creating a multi-page Wizard for what should be a single field on a larger form.

If you're building a SaaS product there are many highly-interactive components that demand JS and there's really no better mainstream solution atm than static-first sites with small "islands" of Vue/React style components (ideally with hydration) where interactivity is required.

People still abuse React/Vue of course, but the trend is 100% moving back to "mostly static" rather than slow SPAs and IMO JS-powered components are not never going away unless browsers start offering these complex components built-in.

I’m a fan of select2 (https://select2.org), it supports loading in data from a foreign source (API)

You could use a Select2() for the records which prevent the massive amount of data being transferred.

Sometimes I still import it for only one thing : select2 that depends on it. Does anyone have an alternative ? I'd love it

The traditional solution was to use ModelAdmin.raw_id_fields, a comma-delimited string of IDs in a text input. Many users found the interaction inelegant, and so ModelAdmin.autocomplete_fields with live search integration with Select2 was added in Django 2.0.

The module django-extensions has a searchable select box widget. There are others using Select2 as well.