immersive-web / immersive-web/model-element
Specify the view on model contents
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 86
- Forks
- 12
- Avg merge
- 7h 12m
- Merged PRs (30d)
- 1
Description
At TPAC we discussed the necessity to point the view into a <model> element at specific locations within it, e.g. to focus on specific features of a car.
We also agreed that for both reasons of complexity for the author and compatibility across platforms, that supplying view information like a 4x4 projection matrix were not appropriate. Instead, to follow something closer to the style indicated with the existing proposed JS syntax, i.e setCamera({pitch:10, yaw:10, scale:1}).
My suggestion is to specify an {x,y,z} object as an optional origin or pivot parameter on that setCamera call:
myShelf.setCamera( {
pitch:0,
yaw:20,
scale:1,
pivot: {x:0, y:1, z:0}
} );
and in fact for the other parameters to be made optional as well, with the presumption that no supplied value implies to retain the same one.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with this issue and the existing proposed JavaScript setCamera syntax. Review the suggested pivot/origin object and the optional-parameter behavior, then check the discussion for an agreed direction. Done means the view-control API and its semantics are specified clearly enough for implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100