TableTools cdn?
TableTools cdn?
dnagirl
Posts: 36Questions: 2Answers: 0
Today I discovered that TableTools and the recently released jQuery-UI v1.9.0 have a major problem working together. I've resolved it by downgrading jQuery-UI to v1.8. But I would have liked to show you what was happening. Unfortunately, all of my webspace is IP-limited so I can't use DataTables Debug.
If TableTools were available by cdn like DataTables core is, I could replicate the issue on jsFiddle (http://jsfiddle.net/). Is there any intent to make TableTools available by cdn?
Thanks,
Jen
If TableTools were available by cdn like DataTables core is, I could replicate the issue on jsFiddle (http://jsfiddle.net/). Is there any intent to make TableTools available by cdn?
Thanks,
Jen
This discussion has been closed.
Replies
TableTools, has you have seen, isn't on any CDN, and there isn't a plan to make so yet, although that will likely change as DataTables progresses (v1.11's modularisation for example opens up options). However, you could use the file that sits on datatables.net for testing: http://datatables.net/download/build/TableTools.js . I would VERY strongly suggest to anyone reading this DO NOT use datatables.net as a CDN. It is not designed to be a CDN, and I might change the file locations in future site updates. So with that warning, its fine for a test like this :-)
Allan
Allan
You can use these two files for testing:
http://datatables.net/release-datatables/extras/TableTools/media/js/ZeroClipboard.js
http://datatables.net/release-datatables/extras/TableTools/media/js/TableTools.js
It is worth noting that I would say categorically do not use DataTables.net as a CDN! It is not designed for such access and will not perform well on any other site - indeed, maintenance on the server could take it offline or I might move file locations! Fine for testing (as long as bandwidth levels are sensible), but most certainly not suitable for production.
Allan
After much fiddling around and fair amount of blue air, I've figured out what the problem was. It turns out that my TableTools issue was a symptom not a problem. The issue is that jquery-ui 1.9 no longer allows for IE's atypical handling of basehref.