Gabby Getz
Gabby Getz
CesiumJS is an extensive library with a lot of functionality that, depending on the app or use case, goes unused. Installing the `cesium` npm package also syncs third party libraries...
The current CesiumJS distribution consists of a single, bundled JS entry point, `Cesium.js`, which inlines all library JS code. It also ships with several other static files, including standalone `Worker`...
Model outlines are not showing up in the following example in any browser. [Sandcastle example](http://localhost:8080/Apps/Sandcastle/index.html#c=dVRtb9s2EP4rB39SAIdymm5FXTdY67RYgAUeZnfBMA0rTZ0kohQpkCenbpH/vqNkOXLSfRHFu+cePvdCKmcDwU7jPXp4CxbvYYlBt7X4s7Ml2UR1+6WzJLVFn02m8D2zAITes+V373Y6Rz8fApVHSXjnvMk3PSQ5m8YAXcsS/X4IiAfcuhxNmMPf0Q/j45+hku89hlGyxjlkkzXxj4WN61UNbq2c/eRNRKRr13qF6Z3OS6SQ3kQFh+VRSEhDx9QRicaWIzJyzpBuItk7qHRZAbOTl1y0rZHqC0ibw32lCaGWjcgyWxE18zTlXRA9r1CuHlEqrk7p/D5yrqg60d7VTjv7sbUqrnMoDn+QnMGxAgAeqfV2XLBVg3ZNHpFuZfMkw2QUCdD2xYlCAyvtRZ6TNhiEFCEYUXB+Zi8sUkqxKOlI4kFmrmk+NgEz8sHQ0cB2D4fuXLO60k6htawDlkt4/xdcipmAa0ky4k50n+LW78TJwQ9nb4bNw8H8cBbXfzLb+TKrunlWbSBXryuZP53q5cjTV6XwsmSh1Ns2+JXm8Dk6dk7nR+9tHOOPh82NbVqCInTrFLR1vFXf6n/rOKi33F+vpeGB6H+OjRsMItdF0QZkaTtUl8lMzIbMjpDQoGqN9I+Yi2cY79qyshgCg5ijcz/Ez+cn9XChjjzdjRZBoUXReF1r0rvY8zxPTu7uKtTvW21ybcvQFwmt3Brs7uGHrw2fHssgeYzIt9i1IlTuftWS4SdiZHW9ZemMe3wgup24+/Vm86EDjbsVhUflrJhvz97EGsWRKJgl7zI6yULxjHkpCrPfuF5pjoG0lf3lGQ6UnvhP2ktReFdfY8njFpLzVy/F7OL1FF7OxM+vL15M4dVPs/6pcl7HBHuWQ/cqlLEiR1bucyXI/cFWaUPy4hAK0GhS1f/BzgdcnGBuEkymk0WX6dUw27/ounGe4j1NhEgJ68ZwV0K6bdUXJKFCGEZhkY5DF7negc7f/uDNBmVkCOwpWmPW+htmk6tFyvhnocZ1aa526I3cR1h1cfVbbxRCLFLe/jgyvpVb6Z8w/wc) Browser: Chrome, Firefox Operating System: MacOS 10.14.6
Modules which are simply imported and exported in [`Source/ThirdParty`](https://github.com/CesiumGS/cesium/tree/main/Source/ThirdParty) are not strictly needed now that we no longer need to package them ahead of time for development, and most likely...
There are certain newer browser features that will not work using http and require https instead. Moving to https/2 may also give us a performance benefit when developing locally.
Convert `KHR_materials_common` glTF 1.0 extension properties to PBR in `updateVersion`. CC #330
Add support for gltf 2.0 [Sparse Accessors](https://github.com/KhronosGroup/glTF/tree/master/specification/2.0#sparse-accessors)
These stages needed to optimize glTF need to target glTF 2.0. https://github.com/AnalyticalGraphicsInc/gltf-pipeline/blob/master/lib/Pipeline.js#L121-L137 They must be tested against 2.0 and updated if necessary. Furthermore, some are slow and may need to...
These stages need to be rewritten to target glTF 2.0
Support upgrading glTF 1.0 materials to PBR in `updateVersion`. This means removing shaders and techniques and making some best guesses for upgrading to PBR. CC #330