|
|
|
|
|
by olifolkerd
2762 days ago
|
|
Hey Don, on the whole the key is to stick to vanilla JS and avoid trying to use to forcible a design paradigm that could conflict with other frameworks. Removing dependencies on other libraries was key to making it interoperable. Everything in Tabulator is built to be extensible so where an incompatibility exists it is easy to build a solution for a particular framework. Tabulator still has one hangup in the way it works, in that it dosnt use reactive data (changing the array you passed into the table, does not automatically update the table, unlike react and view, you have to bind watchers at the moment) but this will be coming in the next release. at which point they should all work harmoniously The biggest challenge is to ensure that things are drawn correctly at the correct time. Because Tabulator uses a virtual DOM it makes it a since to redraw parts of the table when needed |
|
Any suggestions for interesting parts of the code I should snoop around? ;)