|
Added another potential sortable table implementation
Hey Scott – thanks for the quick feedback, I understand how paginated tables and custom sort order will be a challenge. Not intractible, just as you say difficult.
For the majority of my usage, I don't actually have pagination. And I would gladly trade pulling down 300 rows if I knew I could them sort locally. Custom sorting for "non-natural" columns shouldn't be too difficult to hack... afterall, the server obviously has code that figures out the logic. FYI - Canoo.com's UltraThinClient (Java applet) tackles this problem in an interesting way. As I recall, Canoo dynamically loads data the user can "see" plus some extra rows for buffer. When the user scrolls, more rows are loaded. On column sort, the client sends a request to the server which sorts and then dynamically sends whatever rows would be seen post sort based on the users current row. Ex. view ten rows ID#20 to ID#30 out of 500, sort by ID descending, user would then see #490-480. Scroll up and user would see buffered lines 500 - 490. Scroll down and more rows would be dynamically loaded. Oh, and throw in JSON for the data transport to reduce the data transfer size... and maybe use Javascript Templates from Trimpath (http://trimpath.com/project Or maybe use AMASS to cache the entire 500+ issues locally and Trimpath Query to run SQL against that data. (http://trimpath.com/project/wiki/TrimQuery Admittedly more difficult in DHTML and AJAX... but doable, eh? |
||||||||||||||||||||||||||||||||||||||||||||||||
This is difficult to do when:
However, that doesn't mean we won't be trying to do it.
We are looking to rewrite the issue navigator, and this is one thing we want to address.
Cheers,
Scott