Tried that, problem is when viewing from mobile device, the stats in their table have some problems fitting a mobile screen.Seeing more and more websites, templates and even joomla components getting full responsiveness, making them fully viewable from any device.

Absolutely. Right now I just made it pass the same variables that are available to formulas. Tournament title isn't useful to a formula. But I knew I would be adding other items as requested. So request away.

I didn't tackle the date because that's the only built-in date format in Javascript (and it's locale-specific). To get a date formatted the way you like, you've got to build it yourself. I'm sure there are other alternatives, too, like using a JQuery plug-in.

For the format you specified, add the following code to the TournamentStatus.js file (you can just paste it at the end of the file):

And am i suppose to set the "update frequency" in TD3 to a very small number like 2 or 3 as well as in the TournamentStatus.js to get allmost instant uppdates?

You can set the update frequency in TD3 as low as 1 second. Since the TD basically does a "fire and forget" (it doesn't care really what the server says in response), you should be able to safely have it update once per second.

You'll have to experiment with the refresh setting in TournamentStatus.js. As I said, I didn't really examine how it might behave if your server is slow to respond, or timeouts occur. Might be fine, might not, I can't say. Probably will be fine, but again, I just can't really say. FYI, the refresh rate setting in TournamentStatus.js. is defined in seconds, but you can give it fractions, too. Set it to .5 to have it update every 1/2 second.

The refresh rate is the one concerning me, it works great but i don't want to get i trouble with my web space provider, thinking maby an very low rate could get flagged as some sort of "attack".Probably not thou, but I'm satisfied with leaving the rate at 5 sec to start with.

Once again, thanks for a lovely product and the fantastic respons on your users input.In the middle of the summer you might think someone would like to relax and enjoy life instead of typing code.Kudos to you Corey.

The refresh rate is the one concerning me, it works great but i don't want to get i trouble with my web space provider, thinking maby an very low rate could get flagged as some sort of "attack".Probably not thou, but I'm satisfied with leaving the rate at 5 sec to start with.

I wouldn't worry about it. Your hosting service should not only be able to handle it, but I think it's pretty unlikely to set off any alarms. I went back and looked at TournamentStatus.js a little more closely and I think it should behave just fine no matter what you set the refresh to be. It might get a little weird if you were to dynamically set it (there's a form built into the page to change the refresh rate, but it's not displayed by default; if you just change the refresh rate in TournamentStatus.js directly, there should be no trouble at all).

Once again, thanks for a lovely product and the fantastic respons on your users input.In the middle of the summer you might think someone would like to relax and enjoy life instead of typing code.Kudos to you Corey.

It really shouldn't be very hard. There's no coding, as the pages are already written for you. Probably the hardest part will be making sure your website is configured to allow the statusListener.php page to write to the folder/directory in which it is installed. So, setting it up should consist of:

It really shouldn't be very hard. There's no coding, as the pages are already written for you. Probably the hardest part will be making sure your website is configured to allow the statusListener.php page to write to the folder/directory in which it is installed. So, setting it up should consist of: