User Settings: Rework Settings Dialog with extensible components

tjcouch-sil commented 1 year ago

As a user, I want to be able to adjust settings that affect how I use Platform.Bible so I can configure it how I like to use it.

As an extension developer, I want to be able to provide settings that the user can edit in a central dialog so they can configure Platform.Bible how they want, and my extension will adjust accordingly.

Reimplement the Settings dialog from #434 as a webview so it is sandboxed from main UI
Maybe goes in its own bundled extension? Or find a way to serve this webview from core somehow
Must accept settings object and components
Display settings groups and individual settings according to settings JSON
Provide components for settings created in #712

Tightly coupled with #712. See #510 which is very similar

Settings & State Design Doc

Sebastian-ubs commented 1 year ago

For reimplementation use https://github.com/paranext/paranext-core/issues/621

tjcouch-sil commented 8 months ago

How does https://github.com/sillsdev/config-r fit in?

Sebastian-ubs commented 8 months ago

How does https://github.com/sillsdev/config-r fit in?

We have had a quick look and were not sure about the benefits if we want

to use a different ui library
a different style

Are there technical /functional benefits of reusing this?

tjcouch-sil commented 7 months ago

I don't know but I imagine the UI and the functionality are separated in config-r. John Hatton told me something along the lines of that config-r might be useful in validating settings values based on a configuration input instead of having to build out a bunch of custom validation checking for it ourselves.

paranext / paranext-core

User Settings: Rework Settings Dialog with extensible components #503