DataTables VS catalyst

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.

Reminds me of GitHub catalyst web component framework, which has targets & actions. https://github.com/github/catalyst

Working on the next Web UI (TypeScript + Catalyst).

Catalyst (opt-in via CLI flag)

They actually use a web component system, with a library called Catalyst used to make things a bit easier. They aren't simply doing raw DOM manipulation in Vanilla JavaScript, they're using components and what is essentially a fairly lightweight framework.

Personally, I'd really like to see the unmolested, with-dependencies versions[1].

This version is VERY easy to ship and adopt. But in my mind, these components hide how the sausage is made! Many were built with a library (Catalyst[2]), but the tools were obfuscated out in these end products.

There's a huge amount to be said for these web components. We need more models like this. But I also think there's an opportunity lost here, to teach, to inform, to help others learn how to build components, using the tech Github actually used to develop them.

[1] https://news.ycombinator.com/item?id=26439167

[2] https://github.com/github/catalyst

GitHub Catalyst is a library that makes it easier to develop Web Components.

The only real escape is using something like /r/webcomponents. I did some playing around with Github's new Catalyst framework over the holidays, quite enjoyed it. But you'd be one of the only people on the planet using it. Stick with whatever works for you.