New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
live_cpu_graph does not work on Internet Explorer #50
Comments
The LiveCPU example is a more advanced example that relies on HTML5 canvas support, we could use excanvas to fix the rendering for IE but it is still using /proc/stats for getting the CPU info. I have no idea what the windows alternative for that would be. |
Unless you just want it to render properly on windows and don't mind not being able to develop it on windows |
ok, I ported this so development wise and rendering wise it should work on all platforms. I don't have IE 8 to test with so I'll leave that up to you. |
I think we should leave the server to be linux but focus on the client to be IE, FF, Chrome etc., otherwise the purpose of socket.io is lost |
Well development at least works under Linux and OSX and I included excanvas.js for IE less than or equal to 8 but don't have a way to test if excanvas fixes it. |
OK unfortunately I dont have the JS skills to make it work. Let us leave it open and see if someone else can fix it. |
Did you test the latest code? can you paste me the error? I pushed changes that should work, I just get test them since I don't have IE |
@sontek same problem as before. Something wrong with Flot maybe? Also you have to add to the instructions
|
I removed the pip requirements and added all dependencies in setup.py, so you just have to call python setup.py develop and it'll do it for you. It doesn't seem like it actually loaded the excanvas.js file, that should have generated the G_vmlCanvasManager that is needed |
Looks like flot.js is actually including excanvas by itself. |
can you git pull and try one more time? |
Yes!!! this works nice. On Fri, Jul 6, 2012 at 5:00 PM, John Anderson <
|
Here is the error from IE 8 browser - its triggers a JS exception
The text was updated successfully, but these errors were encountered: