Bugzilla – Bug 455
Bad links on public wiki
Last modified: 2011-03-30 12:08:46 PDT
The links on http://www.khronos.org/webgl/wiki/Tutorial to utils3d.js and CanvasMatrix.js are broken. I found utils3d.js It is now in https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/sdk/demos/common/. I have been unable to find CanvasMatrix.js, which is why I have not simply made an wiki account and fixed it myself.
It looks like that demo now uses Chris Marrin's J3DI library. The source code for the demo is checked in to the public WebGL repository, so the tutorial should just be updated to track it. Mark, it would be great if you could help update it.
I am happy to update the tutorial page. I have a couple of questions the answers to which will help me do a good job. One of the reasons there is a problem and for my confusion is that the page links to separate copy of the source, which is now completely outdated, that is shown when the view source link is clicked. Is there a way to write an href so that the document's source is shown? Then I can avoid the duplication. The tutorial page contains several <source lang="html4strict"> tags which are I think to guard against the <script> tags being interpreted by the page. Is there an html5 equivalent I should be use instead?
(In reply to comment #2) > I am happy to update the tutorial page. I have a couple of questions the > answers to which will help me do a good job. > > One of the reasons there is a problem and for my confusion is that the page > links to separate copy of the source, which is now completely outdated, that is > shown when the view source link is clicked. Is there a way to write an href so > that the document's source is shown? Then I can avoid the duplication. Sorry, I don't know how to do this, at least not portably. Some browsers use a "view-source:" scheme plus the URL. > The tutorial page contains several <source lang="html4strict"> tags which are I > think to guard against the <script> tags being interpreted by the page. Is > there an html5 equivalent I should be use instead? Those are to get proper syntax highlighting. They shouldn't be changed.