Comments on: WebGL VS. Canvas 3D http://www.c3dl.org/index.php/c3dl-dev/webgl-vs-canvas-3d/ WebGL made easy! Tue, 16 Aug 2011 14:23:23 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Phreak Nation http://www.c3dl.org/index.php/c3dl-dev/webgl-vs-canvas-3d/comment-page-1/#comment-1335 Phreak Nation Tue, 11 Jan 2011 22:17:42 +0000 http://www.c3dl.org/?p=1943#comment-1335 There is no status bar in Minefield because it is a beta browser. Ever walk through a minefield? Not that easy to do. The status bar is not a big issue to me because I use the built in developer console which there you can explicitly track each file and where it is coming from. Also you keep comparing a beta technology to something that has been around a while. This thing is BRAND new, and not even a standard. Hence why you have to use a beta browser. Also chrome is not a beta browser. Just have to pass an argument and you got it. Also the reason this is being done is because with plugins come security risks and programming flaws. Always has been an issue with plugin vs native to browser. Also the browser does not monitor any plugin in the way you are wanting because not every plugin is made the same. That is going to be an impossibility. You say they jumped the shark. I say they are ahead of the curve. Simply because this is beta. If you had an issue with it you have the option of not using it at all. All in all, beta means it is not fully functional and may have glitches, or features not readily available, and to use caution with the release. I refer back to my other comment from your other very similar post. The reason ‘why cant’ is because it should be a standard feature in all browsers. There is no status bar in Minefield because it is a beta browser. Ever walk through a minefield? Not that easy to do. The status bar is not a big issue to me because I use the built in developer console which there you can explicitly track each file and where it is coming from.

Also you keep comparing a beta technology to something that has been around a while. This thing is BRAND new, and not even a standard. Hence why you have to use a beta browser. Also chrome is not a beta browser. Just have to pass an argument and you got it.

Also the reason this is being done is because with plugins come security risks and programming flaws. Always has been an issue with plugin vs native to browser. Also the browser does not monitor any plugin in the way you are wanting because not every plugin is made the same. That is going to be an impossibility.

You say they jumped the shark. I say they are ahead of the curve. Simply because this is beta. If you had an issue with it you have the option of not using it at all. All in all, beta means it is not fully functional and may have glitches, or features not readily available, and to use caution with the release. I refer back to my other comment from your other very similar post.

The reason ‘why cant’ is because it should be a standard feature in all browsers.

]]> By: Cathy Leung http://www.c3dl.org/index.php/c3dl-dev/webgl-vs-canvas-3d/comment-page-1/#comment-1333 Cathy Leung Mon, 03 Jan 2011 18:21:34 +0000 http://www.c3dl.org/?p=1943#comment-1333 @wap-tek - sorry for the extremely delayed reply. Been taking a break with Christmas and all that going on. Firstly, I don't think that webGL and X3D/VRML are really doing the same thing. From what I understood X3D/VRML is a high level declarative scene/model specification markup language. webGL on the otherhand is a low level api that allows web pages to make use of hardware accelerated 3D graphics on a person's computer to render scenes but it is not in itself a scene specification language. In fact, x3dom (http://www.x3dom.org/) has been doing some work in using making use of webGL to render x3d scenes. It is plug-in free and works with any webGL enabled browser. @wap-tek – sorry for the extremely delayed reply. Been taking a break with Christmas and all that going on. Firstly, I don’t think that webGL and X3D/VRML are really doing the same thing. From what I understood X3D/VRML is a high level declarative scene/model specification markup language. webGL on the otherhand is a low level api that allows web pages to make use of hardware accelerated 3D graphics on a person’s computer to render scenes but it is not in itself a scene specification language. In fact, x3dom (http://www.x3dom.org/) has been doing some work in using making use of webGL to render x3d scenes. It is plug-in free and works with any webGL enabled browser.

]]> By: wap-tek http://www.c3dl.org/index.php/c3dl-dev/webgl-vs-canvas-3d/comment-page-1/#comment-1331 wap-tek Sat, 25 Dec 2010 10:51:26 +0000 http://www.c3dl.org/?p=1943#comment-1331 NO status bar in the new firefox = now you are blind , the status bar made it easy to tell if a site link lied about where you were going and this was just not coperate / advertizer friendly webgl = require a beta browser = maybe see something vrml/x3d = use a plugin or viewer in any browser, = it worked over 10 years ago! why cant mozilla just use a generic vrml / x3d plugin BUT make it FAULT TOLLERANT = as in ignore the deliberate standards breaking that the major players did 10 years ago google , mozilla, and many other "good guys" jumped the shark or drank the flavoraid NO status bar in the new firefox = now you are blind ,
the status bar made it easy to tell if a site link
lied about where you were going and this was
just not coperate / advertizer friendly

webgl = require a beta browser = maybe see something

vrml/x3d = use a plugin or viewer
in any browser, = it worked over 10 years ago!

why cant mozilla just use
a generic vrml / x3d plugin
BUT make it FAULT TOLLERANT = as in
ignore the deliberate standards breaking
that the major players did 10 years ago

google , mozilla, and many other “good guys”
jumped the shark or drank the flavoraid

]]> By: Arun Suresh http://www.c3dl.org/index.php/c3dl-dev/webgl-vs-canvas-3d/comment-page-1/#comment-1184 Arun Suresh Fri, 04 Dec 2009 04:13:44 +0000 http://www.c3dl.org/?p=1943#comment-1184 Hey... I noticed that my Macbook Pro has the same configuration as your: OS X (10.5.8) 2.2GHz Intel Core 2 Duo 2GB DDR2 RAM GeForce 8600M GT 128MB yet I am not able to get Minefield (v3.7a1) or WebKit (r51580) to render anything for eg : http://www.peternitsch.net/demo/webgl/index.html For Minefield.. i have flipped the "webgl.enabled_for_all_sites" and the "html5.enable" switch in about:config.. And for webkit, I have set the following switch.. "defaults write com.apple.Safari WebKitWebGLEnabled -bool YES" For some reason.. nothing seems to work... Could you please let me know if I am missing something ? Thanks in advance -Arun Hey…

I noticed that my Macbook Pro has the same configuration as your:
OS X (10.5.8)
2.2GHz Intel Core 2 Duo
2GB DDR2 RAM
GeForce 8600M GT 128MB

yet I am not able to get Minefield (v3.7a1) or WebKit (r51580)
to render anything for eg : http://www.peternitsch.net/demo/webgl/index.html

For Minefield.. i have flipped the “webgl.enabled_for_all_sites” and the “html5.enable” switch in about:config..
And for webkit, I have set the following switch.. “defaults write com.apple.Safari WebKitWebGLEnabled -bool YES”

For some reason.. nothing seems to work…
Could you please let me know if I am missing something ?

Thanks in advance
-Arun

]]> By: WebGL around the net, 9 Nov 2009 - Learning WebGL http://www.c3dl.org/index.php/c3dl-dev/webgl-vs-canvas-3d/comment-page-1/#comment-1152 WebGL around the net, 9 Nov 2009 - Learning WebGL Mon, 09 Nov 2009 16:34:15 +0000 http://www.c3dl.org/?p=1943#comment-1152 [...] from the original Canvas3D (WebGL’s predecessor). The latest news is that they have some speed comparisons (in terms of teapots per second ;-) between the [...] [...] from the original Canvas3D (WebGL’s predecessor). The latest news is that they have some speed comparisons (in terms of teapots per second ;-) between the [...]

]]>