Talk:JSOM/object reference
From Wiki
(Created page with "==What is this doing here?== I am just basically trying to get all of this written down while it is still fresh in my head. Hopefully some code examples can be added in the near ...") |
(→Clearance? or: new section) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
==What is this doing here?== | ==What is this doing here?== | ||
I am just basically trying to get all of this written down while it is still fresh in my head. Hopefully some code examples can be added in the near future... just for posterity sake. FYI: The information here is interesting, but it's really only useful if you want to develop for / against the JSOM schema or are looking for ideas for a similar such schema. IMO this schema is pretty damn good, but I don't expect it to be widely adopted for generic graphics on the web... but you never know. --[[User:Holy|Holy]] 12:23, 20 February 2012 (CST) | I am just basically trying to get all of this written down while it is still fresh in my head. Hopefully some code examples can be added in the near future... just for posterity sake. FYI: The information here is interesting, but it's really only useful if you want to develop for / against the JSOM schema or are looking for ideas for a similar such schema. IMO this schema is pretty damn good, but I don't expect it to be widely adopted for generic graphics on the web... but you never know. --[[User:Holy|Holy]] 12:23, 20 February 2012 (CST) | ||
| + | |||
| + | == Clearance? or == | ||
| + | |||
| + | As a reminder: I want to change "clearance" to "container" and use two 3D values rather than three 2D values. This desire grew out of forking Assimp, where I just prefer the way the GetContainer methods work, which I developed for the fork; Assimp used a difference system--which involved specializing std::min/max to produce mixed values that were not in the spirit of min/max--but that's just a historical note. Also I learned about glTF last week. I guess JSOM is still interesting, but it's not withstanding very similar to glTF, which is a proper standard backed by Khronos Group.--[[User:Holy|Holy]] 14:51, 15 March 2016 (UTC) | ||
Latest revision as of 14:51, 15 March 2016
What is this doing here?[edit]
I am just basically trying to get all of this written down while it is still fresh in my head. Hopefully some code examples can be added in the near future... just for posterity sake. FYI: The information here is interesting, but it's really only useful if you want to develop for / against the JSOM schema or are looking for ideas for a similar such schema. IMO this schema is pretty damn good, but I don't expect it to be widely adopted for generic graphics on the web... but you never know. --Holy 12:23, 20 February 2012 (CST)
Clearance? or[edit]
As a reminder: I want to change "clearance" to "container" and use two 3D values rather than three 2D values. This desire grew out of forking Assimp, where I just prefer the way the GetContainer methods work, which I developed for the fork; Assimp used a difference system--which involved specializing std::min/max to produce mixed values that were not in the spirit of min/max--but that's just a historical note. Also I learned about glTF last week. I guess JSOM is still interesting, but it's not withstanding very similar to glTF, which is a proper standard backed by Khronos Group.--Holy 14:51, 15 March 2016 (UTC)
