WebGL Demo
Andor Salga | 9 November, 2009 | 14:49
After talking to Dave, I realized I had the WebGL port almost done, demos working, but without a demo on the Web! Oops. So, for anyone running a Firefox nightly, check out this demo!
« WebGL VS. Canvas 3D
OSX + Minefield + WebGL + Points = :( »
Archives |
C3DL Development News |
Recent Comments |
|---|---|---|
|
|
[...] by giles on Nov.09, 2009, under Links Wow! I
WebGL around the net, 9 Nov 2009 – part 2 - Learning WebGL | 9 November, 2009 | 15:37[...] by giles on Nov.09, 2009, under Links Wow! I mentioned earlier today that the C3DL team were porting their stuff over to WebGL, but when I posted they hadn’t actually made anything live. They’ve fixed that, and the result’s fantastic: check it out here! [...]
It doesn't work in WebKit as you are using a
Oliver | 9 November, 2009 | 17:49It doesn’t work in WebKit as you are using a firefox only feature: the use of keywords as property names. Firefox is the only browser that allows const (and the other keywords) to be used as property names, so your use of const as a property name needlessly breaks everyone else.
You could get around this by doing ["const"] rather than .const, but that seems somewhat icky.
Could you make it work in WebKit nightlies too? Right
smfr | 9 November, 2009 | 21:52Could you make it work in WebKit nightlies too? Right now it hits: SyntaxError: Parse error on orbiter.js line 110.
We wanted to use const but couldn't use them in
Andor Salga | 12 November, 2009 | 4:11We wanted to use const but couldn’t use them in conjunction with namespaces. We also wanted to ensure users know the variables we had won’t be changed by the library so we have things like c3dl.const.TOLERANCE. However, because this is an issue, we’ll probably just remove our use of const altogether.
webgl = forced to use beta browser + 90 mb
wap-tek | 25 December, 2010 | 5:19webgl = forced to use beta browser + 90 mb video driver ,
= maybe see something
vrml/x3d = find a decent plugin or viewer ,
= all were less than 5 mb and worked over 10 years ago!
why cant mozilla just use a generic vrml / x3d plugin and make it
FAULT TOLLERANT = ignore the deliberate standards breaking
that the major players did 10 years ago
@wap-tek +90mb vid driver? never have to dload a driver
Phreak Nation | 3 January, 2011 | 12:12@wap-tek +90mb vid driver? never have to dload a driver if you are already updated. If that is the case that on you, imo…lol
Also the beta browser is just temporary until webgl becomes a standard which should be in the coming year i hope and in that case it will be in every browser(except ie i believe). Every web technology started this way.
The reason ‘why cant’ is because it should be a standard feature in all browsers.
sorry but ,, not good enough! if this cannot be
wap-tek | 11 February, 2011 | 21:14sorry but ,, not good enough!
if this cannot be made a plug in, (bad idea , but doable)
then it leaves its self open to FUD!
meanwhile a 10 year old standard sits gathering dust!
the same psudo stuborn crawl for DECADES!
screw it ,,, i will write it ,
I should point out that as of 3 Feb 2011,
peter | 14 February, 2011 | 10:36I should point out that as of 3 Feb 2011, Chrome 9 has WebGL enabled by default (without requiring a plug-in or any changes by the user).
I don’t have specific dates for Firefox or Safari, but I doubt they’re far behind.
As for not having a status bar, that was a choice Mozilla made for 4.07b, however it is fairly easy to re-enable (at least enough to see the address a link points to ). Just go to the menu bar and select view>toolbars>Add-on Bar. I think it is intended to show other information, but when you hover over a link the destination address pops-up above that bar (at the bottom of the window). Warning: I’m using a nightly build so it might be different in other versions.
UPDATE: Firefox 4 was released on 22 Mar 2011 and has WebGL enabled by default (again, without requiring a plug-in or any changes by the user). In addition, the pop-up bar at the bottom shows up automatically.
Firefox 4 was released today and it is by default
Cathy Leung | 22 March, 2011 | 18:44Firefox 4 was released today and it is by default WebGL enabled. Chrome had done it earlier.
Safari and Opera both have WebGL in their development versions.
I once again recommend that you check out the x3dom project (http://www.x3dom.org/). You can use it in your page and specify your scenes with X3D. The underlying rendering is done with WebGL but the scene declaration is done with X3D.
Hi there, just wanted to point out that Opera also
Patrick H. Lauke | 3 May, 2011 | 15:35Hi there, just wanted to point out that Opera also has (currently experimental) support for WebGL in a special labs build, available from http://my.opera.com/core/blog/2011/02/28/webgl-and-hardware-acceleration-2 – though your demos seem to fail there (something about inability to convert some objects, somewhere in your js code)