Comments (3)
Can you cut down the explainer to just what you're planning to implement and why?
I think keeping it in sync with the evolving spec will waste time (and sometimes forgotten).
from model-element.
Can you cut down the explainer to just what you're planning to implement and why?
Depends... what gets implemented (i.e., exposed to the web) will depend on what we have consensus on in the CG/WG. Put differently, I don't know what the final shape is going to be until we all agree to it.
I think keeping it in sync with the evolving spec will waste time (and sometimes forgotten).
Generally, I would agree (and I'm totally guilty of this with other specs)... but a lot of people seem to appreciate them, and some folks ask for them, like that W3C's TAG, as part of the wide review process.
I think if we are disciplined, and enforce keeping it up to date with the pull request template, it might be ok.
I can take responsibility for keeping it up to date. If it fails spectacularly, we can just point people to the introduction of the spec and examples.
from model-element.
I would certainly appreciate it. I find it useful myself and use it as the resource to point developers to if they start asking for more details
from model-element.
Related Issues (20)
- Interactions with HTMLCanvasElement HOT 3
- models must not be allowed to download external content HOT 5
- filter CSS property HOT 1
- polyfill
- Enhanced API for Animations HOT 1
- High level scene graph manipulation API HOT 3
- Clarification: using dynamic/generated `src` values
- Let's define some more extensive use cases
- Specify fallback model for performance issues HOT 2
- TPAC Discussion Topics HOT 5
- Need for Planning and Justification HOT 9
- Supply an Image-based Light file HOT 4
- Specify a camera's pivot location HOT 5
- Making the `<model>` element compatible with modern web frameworks. HOT 2
- `ready` and `complete` events/Promises for responding to source file availability etc HOT 3
- Allow a <model> to specify a preference for spatial display
- Progress on the spec HOT 2
- Clarify scope
- immersive-web/model-element missing from IPR Checker HOT 2
- Per-view user toggle to adjust power preference for model
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from model-element.