search

iTwin / viewer

Monorepo that contains the iTwin Viewer npm packages and their related packages
MIT License
25 stars 16 forks source link

use StandardFrontstageProvider from core instead of custom one #148

Closed aruniverse closed 2 years ago

aruniverse commented 2 years ago

Use StandardFrontstageProvider from core instead of our default which pre-populates many tools

use standard ui-providers from core to populate default items in the test -apps for now

Todo: In a separate pr add & export UiProviders to the base viewer to match existing look & behavior of the viewer (core's standard status bar provider doesnt match the viewer's defaults)

aruniverse commented 2 years ago

Yea I dont think this pr should complete until after we determine what the default ui should look like, merely opening this draft pr in prep for that call.

For the pre-canned templates, i was thinking responses would be used as props for the ui providers

Re blank/viewer consolidation, i think we could get away with it with some type magic, havent looked into it yet, but should be feasible i think. Also why i was bringing up the public models. One viewer component that handles all the different cases, all the real work is done by the IModelLoader anyway