Comments on: TableSorter 2.0 http://www.ghidinelli.com/2007/08/15/tablesorter-20 Thu, 01 Jun 2017 18:51:00 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Samant http://www.ghidinelli.com/2007/08/15/tablesorter-20/comment-page-1#comment-41168 Samant Fri, 09 Nov 2007 22:28:30 +0000 http://www.ghidinelli.com/2007/08/15/tablesorter-20/#comment-41168 Hi, Not sure if the tablesorter still has the bug that i had found in 1.1.3 version. The bug is related to sorting of data in a table column with - sign. Eg, Order NO. OrderAmtDue 1234 -0.1 1235 -0.2 1236 -0.12 1237 -0.16 Hi,

Not sure if the tablesorter still has the bug that i had found in 1.1.3 version. The bug is related to sorting of data in a table column with – sign. Eg,

Order NO. OrderAmtDue
1234 -0.1
1235 -0.2
1236 -0.12
1237 -0.16

]]> By: haylo75 http://www.ghidinelli.com/2007/08/15/tablesorter-20/comment-page-1#comment-39037 haylo75 Thu, 30 Aug 2007 15:52:36 +0000 http://www.ghidinelli.com/2007/08/15/tablesorter-20/#comment-39037 brian - Thanks for the quick reply. I did some benchmarking using debug output and the performance difference is negligible. That makes perfect sense since the loop is for the column list of the first record. brian – Thanks for the quick reply. I did some benchmarking using debug output and the performance difference is negligible. That makes perfect sense since the loop is for the column list of the first record.

]]> By: brian http://www.ghidinelli.com/2007/08/15/tablesorter-20/comment-page-1#comment-39035 brian Thu, 30 Aug 2007 15:31:10 +0000 http://www.ghidinelli.com/2007/08/15/tablesorter-20/#comment-39035 @haylo75: Thanks for catching the typo, we're going to fix that! As for setting the column parser, Christian said there would be a very small performance gain because the detect routine only looks at the first row inside the tbody. You can test for yourself by setting "debug: true" which will give statistics on everything when it runs. Let us know what you find! @haylo75: Thanks for catching the typo, we’re going to fix that! As for setting the column parser, Christian said there would be a very small performance gain because the detect routine only looks at the first row inside the tbody. You can test for yourself by setting “debug: true” which will give statistics on everything when it runs. Let us know what you find!

]]> By: haylo75 http://www.ghidinelli.com/2007/08/15/tablesorter-20/comment-page-1#comment-39030 haylo75 Thu, 30 Aug 2007 11:59:35 +0000 http://www.ghidinelli.com/2007/08/15/tablesorter-20/#comment-39030 tablesorter 2.0 is amazing. Thanks for your work on the docs. They are easy to read and got me up and running in no time. I did notice what appears to be a typo in the <a href="http://tablesorter.com/docs/example-meta-parsers.html" rel="nofollow">Setting column parser using metadata</a> example. I see "{sorter: 'procent'}" for the discount column whereas I believe it should be "{sorter: 'percent'}". I didn't see a "procent" sorter in the tablesorter code, but I did see one named "percent". Quick question. If I hardcode the sorter type for each column, is there a large performance impact as opposed to allowing the detectParserForColumn method take control? tablesorter 2.0 is amazing. Thanks for your work on the docs. They are easy to read and got me up and running in no time. I did notice what appears to be a typo in the Setting column parser using metadata example. I see “{sorter: ‘procent’}” for the discount column whereas I believe it should be “{sorter: ‘percent’}”. I didn’t see a “procent” sorter in the tablesorter code, but I did see one named “percent”.

Quick question. If I hardcode the sorter type for each column, is there a large performance impact as opposed to allowing the detectParserForColumn method take control?

]]> By: brian http://www.ghidinelli.com/2007/08/15/tablesorter-20/comment-page-1#comment-38754 brian Sun, 19 Aug 2007 04:01:34 +0000 http://www.ghidinelli.com/2007/08/15/tablesorter-20/#comment-38754 @Diego, at the moment, the sortForce only takes a single column to act on, unlike the sortList parameter. I chatted with Christian today and he is going to modify it to take the same parameter type as sortList so you'll be able to handle this use case. @Diego, at the moment, the sortForce only takes a single column to act on, unlike the sortList parameter. I chatted with Christian today and he is going to modify it to take the same parameter type as sortList so you’ll be able to handle this use case.

]]> By: Diego http://www.ghidinelli.com/2007/08/15/tablesorter-20/comment-page-1#comment-38737 Diego Sat, 18 Aug 2007 10:18:01 +0000 http://www.ghidinelli.com/2007/08/15/tablesorter-20/#comment-38737 Hi, the "sortforce" is an important improvement. However, the script doesn't work very well: the most important thing that the "sortforce" should do is to memorize the hierarchics criterions. I mean: imagine a common soccer ranking, with points, match won, loss, gol... For example, if two or more team with the same points have also the same gol average (COLUMN 3), the team in the first place should be the team that according to alphabetical order have an "advantage" (COLUMN, 2). Then the "sortforce" code should be [[3,1],[2,0]] Unfortunately the example doesn't work (http://tablesorter.com/docs/example-option-sort-force.html). I write Christian in order to resolve this problem. Can you help me? Hi,
the “sortforce” is an important improvement.

However, the script doesn’t work very well: the most important thing that the “sortforce” should do is to memorize the hierarchics criterions.

I mean: imagine a common soccer ranking, with points, match won, loss, gol…

For example, if two or more team with the same points have also the same gol average (COLUMN 3), the team in the first place should be the team that according to alphabetical order have an “advantage” (COLUMN, 2).
Then the “sortforce” code should be [[3,1],[2,0]]

Unfortunately the example doesn’t work (http://tablesorter.com/docs/example-option-sort-force.html).

I write Christian in order to resolve this problem. Can you help me?

]]>