Issue with Tip.It's new "Worlds List" page

[D. V. Devnull]

Hello, Tip.It Crewbies... :)

 

I went over to have a look at the all-new "Worlds List" page @ http://www.tip.it/runescape/?worldlist that you put a news post up for... Very quickly, I ran into a major sorting issue with the "Players" sorting mode. Apparently, it doesn't understand that thousands are a greater value than hundreds, and that tens are less than hundreds, and so it does something like this:

 

963

817

78

765

648

532

471

386

210

196

1507

149

1388

110

I can only begin to imagine how chaotic this would look with single digits... :unsure:

 

As you can already figure, I'm thinking it should have looked more like:

 

1507

1388

963

817

765

648

532

471

386

210

196

149

110

78

... as that would have better allowed users of the page to select a world with more/less/middle amounts of people present on a given world at a given time. That, and it would behave similarly to the RuneScape Java Applet. So I thought I would come along, since no one else had already began a thread about this, and give you all a heads-up so you can change it quickly. That is, unless this sorting design was intentional, which I hope it wasn't? :blink:

 

~Mr. D. V. "This wasn't intentional, right?" Devnull

 

(p.s.: I'm not even sure where the "OFFLINE" ones fit...)

[Xena_Dragon]

Doh! That column has been set to sort alphanumeric instead of numeric. A fix is on it's way. Thanks for the heads-up! :thumbup:

[Hameigh]

Just came here since that was the first thing I noticed. Glad it is being sorted out. :grin:

[D. V. Devnull]

I get to add one more bug to this list... :?

 

Apparently, at least in FireFox 2.0.0.x-series, if you attempt to sort more than one criteria at a time, it doesn't take the request properly, and really messes up. For example, try sorting first by world number, and then try to stack F2P/P2P status with it. Or even try to do this process in reverse. What a mess... :sad:

 

I don't know if this is linked to the alphanumeric/numeric bug or what, but I thought I would post it up here so that it could be noticed and handled as soon as possible. I'm also not sure, but I think it also occurs to a lesser degree on FireFox 3.5.x-series. :|

 

~D. V. "Am I running into every bug in the world?" Devnull

[Xena_Dragon]

Apparently, at least in FireFox 2.0.0.x-series, if you attempt to sort more than one criteria at a time, it doesn't take the request properly, and really messes up. For example, try sorting first by world number, and then try to stack F2P/P2P status with it. Or even try to do this process in reverse. What a mess... :sad:

Thanks for your input. Because of issues like these, our disclaimer at the bottom of each web page mentions you need at least version 3.x of a Mozilla based browser. So rather than trying to make everything work on every browser, we chose to support only those versions that we can rely upon actually working with the level of Javascript code we throw at it. :rolleyes:

 

Besides that, the table sorter we implemented on that page does not support sorting on more than one column. If it seems to do so, it's just plain luck. I know there are other sorters which are able to do that, but those don't support the nifty filters we want to use on the worlds list page.

 

And finally; The fix for the sort problem on the Players column is on it's way. Patience, grasshopper. :ugeek:

[D. V. Devnull]

Apparently, at least in FireFox 2.0.0.x-series, if you attempt to sort more than one criteria at a time, it doesn't take the request properly, and really messes up. For example, try sorting first by world number, and then try to stack F2P/P2P status with it. Or even try to do this process in reverse. What a mess... :sad:

Thanks for your input. Because of issues like these, our disclaimer at the bottom of each web page mentions you need at least version 3.x of a Mozilla based browser. So rather than trying to make everything work on every browser, we chose to support only those versions that we can rely upon actually working with the level of Javascript code we throw at it. :rolleyes:

 

Besides that, the table sorter we implemented on that page does not support sorting on more than one column. If it seems to do so, it's just plain luck. I know there are other sorters which are able to do that, but those don't support the nifty filters we want to use on the worlds list page.

 

And finally; The fix for the sort problem on the Players column is on it's way. Patience, grasshopper. :ugeek:

Well, I do know how it could be improved then... First, make just one level previous of browser series a minimum compatibility line to shoot for. Second, use cookies to store the sorting method on all browsers, thereby allowing for much more complex sorting methods cross-platform, such as Jagex previously did with their own World Select page system prior to integration in the RS Java Applet. (Such worked all the way back with FireFox 1.5, which I used to use!) :thumbsup:

 

BTW, I won't be upset if the first of the two doesn't happen. Might be slightly upset (but not to the point I'd come annoy someone) if the second didn't happen. And don't worry, as I'm very patient... I could wait near forever for the bug to get fixed. Would be cool to see the bugfix include the improvement, though... *overkill hint* :-w

 

~D. V. "Always a way to improve... I'll leave the choice to the Tip.It Crew..." Devnull

[Cowman_133]

Well, I do know how it could be improved then... First, make just one level previous of browser series a minimum compatibility line to shoot for. Second, use cookies to store the sorting method on all browsers, thereby allowing for much more complex sorting methods cross-platform, such as Jagex previously did with their own World Select page system prior to integration in the RS Java Applet. (Such worked all the way back with FireFox 1.5, which I used to use!) :thumbsup:

 

~D. V. "Always a way to improve... I'll leave the choice to the Tip.It Crew..." Devnull

 

Hi there,

 

Tip.It will not be going back and attempting to support past versions of popular browsers when much newer ones have been out long enough for people to have had a change to upgrade. It is not recommended to use older versions of browsers as they could contain security flaws and other problems that would be fixed in later versions of the browser. It takes an incredible amount of time to ensure cross-browser compatibility and adding more browsers to verify things in wouldn't be a good solution to this problem, rather would cause more headaches for web designers and coders.

 

As for your idea on using cookies so secondary sorting, as I'll call it, can be done, I cannot comment on that, but as Xena already said it was not designed to do this. I am unsure if he plans to incorporate that or not into the world list, so I will let him respond to you on that himself.

 

Thanks for your understanding in the matter.

 

DK

[Xena_Dragon]

Well, I do know how it could be improved then... First, make just one level previous of browser series a minimum compatibility line to shoot for. Second, use cookies to store the sorting method on all browsers, thereby allowing for much more complex sorting methods cross-platform, such as Jagex previously did with their own World Select page system prior to integration in the RS Java Applet. (Such worked all the way back with FireFox 1.5, which I used to use!)

Cookies and storing sort settings or results is not the problem. It's the sorting mechanism itself that doesn't support sorting on more than one column. So we may someday improve that, or start using another library, but I cannot give an estimate on when that will be.

 

The good news is that the number of players column now properly sorts numeric instead of alphanumeric. Once again, thanks for reporting on that. :thumbup: