Is TableTools worth using without the Buttons?

Is TableTools worth using without the Buttons?

wxkevinwxkevin Posts: 11Questions: 0Answers: 0
edited November 2011 in TableTools
I am currently in the processing of prototyping switching out our current tables for DataTables instead. Our tables are scrollable, row selectable and sortable. DataTables provides the sorting and scrolling very well out of the box. TableTools contains row selecting but also comes with the buttons. We won't be using the buttons since we have our own set of toolbar buttons already. I just want to hook the row selection up when our current buttons are selected.

So my question: Is it worth using TableTools just for row selection? Am I better off just writing a function to add or remove the "row_selected" class?

Replies

  • dnagirldnagirl Posts: 36Questions: 2Answers: 0
    It's much easier to manipulate table data with TableTools. The functions in TableTools api are much more reliable and flexible than class checking.
  • allanallan Posts: 63,489Questions: 1Answers: 10,470 Site admin
    I'd agree (even although I am the developer ;-) )! TableTools should make row selection handling for DataTables much easier, and abstracts out some of the problems that you might encounter along the way. There are of course advantages to writing your own library for it, as there are when considering using any 3rd party library, but I've used TableTools for just row selection on many a table and found it useful :-)

    Allan
This discussion has been closed.