-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DataSource API design #2114
Comments
Good API cleanup in 1, and interesting thought in 2. @mramato and I have talked about bringing |
For item 1, I agree it would be a convenient addition. The existing |
Also, just to be clear, I expect most of the code will still live outside of |
The reason we were not doing 1 was because it only allowed you to easily add data with the Cesium default styling, which is pretty useless. However, now that I added support for the simplstyle spec, it's much more useful. I added it as part of #2162 For 2. I'm all for "promoting" it to scene, but does that mean if I add a data source to scene.dataSources then it automatically get rendered? Right now there is a |
I would imagine so. Perhaps primitives and data sources can have very similar paradigms (which could mean changes for either).
Sounds good. I'm happy to discuss. |
Sorry if this is already planned. Looking at this example:
1 . Can this be as concise as primitives like
Model
:2 . Are we sure
viewer
should owndataSources
? Shouldn't this be part ofscene
so users reach into the same object to access terrain, imagery, primitives, data sources, camera, and so on? Isn'tviewer
a UI container, not really part of the animation/rendering engine?The text was updated successfully, but these errors were encountered: