Skip to content
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

feat(globe): migrate to custom globe implementation #1236

Merged
merged 22 commits into from
Jun 2, 2023

Conversation

usefulthink
Copy link
Contributor

No description provided.

 - removes cesium dependency
 - remove old code referencing the cesium globe
 - replaced cesium specific GlobeView type with CameraView type from @ubilabs/esa-webgl-globe
Copy link
Contributor

@pwambach pwambach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool! For changing one of the most important parts of the app the changes are relatively small and clean! Looks really good!

@@ -48,7 +48,6 @@
"@datapunt/matomo-tracker-react": "^0.5.1",
"@reduxjs/toolkit": "^1.9.0",
"@ubilabs/esa-webgl-globe": "^1.0.0",
"cesium": "^1.73.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice!

* Manages a single state-variable indicating wether the first tiles of the
* basemaps have been loaded.
*/
function useInitialBasemapTilesLoaded(globe: WebGlGlobe | null) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can this be integrated in the globe itself

sceneMode,
imageryProvider: defaultBasemapImageryProvider
};
// fixme: right now @ubilabs/esa-webgl-globe doesn't support the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think these events are handled by react in line 88+89 so no need to implement this in the globe itself. These are just listeners on the containing div to decide which of the two globes is the active one if I remember correctly.

If we set the selected layer before the details are available, the globe will - for a few frames - render the default globe, which leads to flickering.
@usefulthink usefulthink changed the title feat(webgl-globe): initial working revision, not feature complete feat(globe): migrate to custom globe implementation Jun 2, 2023
@usefulthink usefulthink merged commit 10cccac into develop Jun 2, 2023
@usefulthink usefulthink deleted the feat/webgl-globe branch June 2, 2023 08:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants