[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #7568 [Compass]: Investigate use of datatables in compass
#7568: Investigate use of datatables in compass
---------------------+------------------------------------------------------
Reporter: gsathya | Owner: gsathya
Type: task | Status: new
Priority: minor | Milestone:
Component: Compass | Version:
Keywords: | Parent:
Points: | Actualpoints:
---------------------+------------------------------------------------------
Comment(by gsathya):
Replying to [comment:3 karsten]:
> But isn't that easy to change, so that datatables does the sorting?
Such an approach would only fail if datatables doesn't have ''all'' data
to sort (i.e., when setting the number of displayed rules to something
other than -1). But in that case Compass would know that it needs to send
a new request instead of letting datatables do the sorting. (Or maybe
that means simply removing the display limit from the web app.)
Yep, it should be easy enough to change. I was afraid that if we start
caching data client side then, next we'll start wanting to do all the work
client side and quickly start looking like Atlas. But I guess sorting is
important enough to make an exception.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7568#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs