{"id":185,"date":"2010-04-21T15:33:00","date_gmt":"2010-04-21T19:33:00","guid":{"rendered":"http:\/\/www.blogseye.com\/?p=185"},"modified":"2010-04-22T14:17:44","modified_gmt":"2010-04-22T18:17:44","slug":"is-it-too-early-to-consider-3d-html","status":"publish","type":"post","link":"http:\/\/blogseye\/2010\/04\/is-it-too-early-to-consider-3d-html.html","title":{"rendered":"Is it too early to consider 3D html?"},"content":{"rendered":"
Note: About 1,000 people read this article in less than an hour, and it seems that they all thought it was about graphics. What I am talking about is markup and css to arrange html tags in a 3d space. I also discuss making some html objects such as tables into 3d objects.<\/em><\/p>\n Someone will market an affordable consumer based three dimensional video card and display. This will happen soon. Shortly afterward there will be three dimensional video format which will give rise to three dimensional websites and demand for three dimensional content.<\/p>\n There are high end flat screen TVs that can display 3D movies. Although there are very few 3D movies available, the sets are selling.<\/p>\n Current development in HTML 5 is all concerned with things like round corners, embedded media and drawing. These seem like more of the same rather than anything revolutionary. It is time to start thinking about 3D HTML.<\/p>\n The coordinate elements in HTML are simple X-Y Cartesian coordinates. Size is based on width and height, where location uses distances to top, left, right and bottom. Orientation is handled in some browsers with a transform css element that will do things like scale, rotate and translate values.<\/p>\n We have lots of built in 2D references where the dimensionality is hard coded by the syntax. If we have height and width do we really want to add depth? I would think not. As long as a designer is going to make a 3D web page using HTML I don\u2019t think anyone wants to use clunky nomenclature to describe positions in a 3D space.<\/p>\n In CSS there would probably be an array of dimensions. For example, instead of using:<\/p>\n #box { width:200px;height;320px;depth:400px; left:0;top:10px;deep:20px }<\/p>\n We could say:<\/p>\n #box { size(200px,320px,400px);position(0,10px,20px); }<\/p>\n In JavaScript we could access these by using an array:<\/p>\n elementID.style.position[2]=\u201d13px\u201d; (changes z dim);<\/p>\n Orientation could be three coordinates that translate into a vector. If the default vector is (0,0,1) then<\/p>\n #box {orientation(1,0,0);}<\/p>\n Would rotate the box to face right (I think).<\/p>\n Transformation in 3D could use similar methods:<\/p>\n #box {transform(1.2em,2em,.5em);}<\/p>\n This could be used to do simple resizing of shapes. You could use em or % or an absolute measurement to resize the shape.<\/p>\n You could use a deg, \u02da, or rad to indicate degrees or radians of rotation. This would nicely distort the shape. The plus or the minus sign could indicate translation in the space.<\/p>\n Using a 3X3 matrix, CSS could use orthogonal projection for transformation, although this might make hand coding html difficult without a good calculator. Although this is the most flexible, I would not even begin to try it.<\/p>\n A 4X4 matrix could be used for transforming an object with perspective.<\/p>\n Three dimensional tables might make life interesting for HTML coders. I doubt if anyone wants a <TF> (table file) tag to indicate where a file will be located. That would make the structure of tables look like this:<\/p>\n <table> It is a simple enough concept, but tables are out of style unless the data is actually tabular and CSS snobs eschew them.<\/p>\n The CSS for a three dimensional table using divs might look like this:<\/p>\n .table {display: table;} It might be more interesting a generic style and let the container determine the placement<\/p>\n <div style=\u201d display:table;dimensions:3\u201d> – table A table-element determines how it is displayed by how its container is displayed. Rows are inside tables. Files are inside rows. Cells are inside files. You could set the dimensions to 5 on the table and have a 5D table, but it would require special rules to display it.<\/p>\n The orientation and transformation of the entire 3D page could be controlled by styling the BODY tag. Zindex would be based on a virtual observer and so the display could be rotated to show the back of objects. The IE style Zoom would have more meaning when a coder could use it to scale a 3D page.<\/p>\n Using 3D it would be interesting to view the 3D tank from different perspectives. Browser scroll bars (three of them) would be used for moving around the box and another control could be used to change the viewpoint and possibly the zoom. The advances in 3D display architectures might also lead to 3D pointers or inputs that could read gestures in the same way the iPhone can sense more than one finger for scaling or rotating.<\/p>\n Javascript events would have to be expanded. Things like mouse-move and resize would have be expanded to return three dimensional units for orientation. Javascript should know when the user is zoomed in on an upside down 3D image.<\/p>\n I could go on.<\/p>\n I am now wondering if there is a 3D HTML and CSS committee meeting somewhere. Google has not yielded up anything so I am guessing that it meets in secret for the time being.<\/p>\n","protected":false},"excerpt":{"rendered":" Note: About 1,000 people read this article in less than an hour, and it seems that they all thought it was about graphics. What I am talking about is markup and css to arrange html tags in a 3d space. I also discuss making some html objects such as tables into 3d objects. Someone will […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"http:\/\/blogseye\/wp-json\/wp\/v2\/posts\/185"}],"collection":[{"href":"http:\/\/blogseye\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/blogseye\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/blogseye\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/blogseye\/wp-json\/wp\/v2\/comments?post=185"}],"version-history":[{"count":0,"href":"http:\/\/blogseye\/wp-json\/wp\/v2\/posts\/185\/revisions"}],"wp:attachment":[{"href":"http:\/\/blogseye\/wp-json\/wp\/v2\/media?parent=185"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/blogseye\/wp-json\/wp\/v2\/categories?post=185"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/blogseye\/wp-json\/wp\/v2\/tags?post=185"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n<tr>
\n<tf>
\n<td>data<\/td>><td>data<\/td>><td>data<\/td>
\n<\/tf>
\n<tf>
\n<td>data<\/td>><td>data<\/td>><td>data<\/td>
\n<\/tf>
\n<\/tr>
\n<tr>
\n<tf>
\n<td>data<\/td>><td>data<\/td>><td>data<\/td>
\n<\/tf>
\n<tf>
\n<td>data<\/td>><td>data<\/td>><td>data<\/td>
\n<\/tf>
\n<\/tr>
\n<\/table><\/p>\n
\n.tablerow {display:table-row;}
\n.tablefile {display:table-file;}
\n.tablecell {display:table-cell;}<\/p>\n
\n<div style=\u201d display:table-element\u201d >\u00a0 a row
\n<div style=\u201d display:table-element\u201d >\u00a0 a file
\n<div style=\u201d display:table-element\u201d >\u00a0 a cell<\/p>\n