One of the impediments which has faced power-users and Artists alike has been, the fact that the most ecumenical way to distribute graphical content so far, has remained in some form of 2D image. This is so much the case, that some people may confuse 2D images with 3D scenes they represent, even if those 3D scenes have been rendered correctly.
The only real possibility to reassure ourselves as an audience, that we have in fact been given 3D content, is to be able to change the perspective in some way, from which we choose to experience it, and then to observe that the changes in the 2D images, effectively, are consistent according to their 3D meaning.
Of course, many people do experience this with 3D Games. But then one misinterpretation that comes with that territory is, ‘In order for a 3D Model or other Creation to be explored, some form of proprietary software must be used.’ I.e., .BLEND Files can only be explored using the application “Blender”, although that is a Free, Open-Source application, and likewise for .OBJ, .DXF, .3DS Files, the native applications for which were proprietary…
A sincere effort has been made by Internet developers to break that barrier, and it comes in the form of WebGL, which is a binary language by which powerful Web-browsers, when run on computers with hardware 3D graphics acceleration, can open 3D content, interactively in some cases, so that the user sitting in front of the browser can explore this content. This content is distributed in the form of .HTML Files, which should be familiar to Web developers, but it uses a new API.
The idea has existed before, but usually, in the form of some 3rd-party extension, and most of the older browser extensions which did this, are now defunct.
In the interest of pursuing this idea, I have created a sub-directory on this Server, which currently contains one real WebGL demo, again, in the form of the .HTML File. In the future, whenever I get the idea to create some more content, I will add it to this directory.
The way HTML Files normally work is, that they are accompanied by additional files, such as PNG Files that contain (2D) images, which are in turn binary by nature, while HTML tends to be text by nature. In recent years, my software has sometimes produced HTML Files that are self-contained, and that also contain binary data, Base-64 encoded. Typically, the way such data can be embedded into an HTML File, is with declarations of the form:
href="data:image/png;base64, ... "
In all honesty, I don’t tend to comprehend such HTML. Certain programs of mine generate it, and the software that I use, to generate WebGL, does so. My main concern is that certain Web-browsers in existence may just not be strong enough, to display such content adequately. I recommend that up-to-date Firefox or Chrome browsers be used with the WebGL on my site.
In theory, because all up-to-date OS/X computers should also be able to display WebGL, etc., their Safari browser should also be strong enough.