Add the ability to hide the mini map by default

[frouene]

[florianbarbin]

Questions for discussion before implementation:

• Scope of Preference: Currently, the minimap toggle is a global setting stored in localStorage. Should we keep it global, or should the visibility preference be stored per individual diagram?
• DSL vs. User Interaction: If we allow the default behavior to be set via the View DSL, should this value act as a fallback that is overridden once a user manually toggles the toolbar for that specific diagram?
• Global Default: If we move toward DSL-defined defaults, should we remove the global preference entirely? Under this model, visibility would default to true unless explicitly defined otherwise in the DSL or through the specific user interaction.

[sbegaudeau]

Scope of Preference: Currently, the minimap toggle is a global setting stored in localStorage. Should we keep it global, or should the visibility preference be stored per individual diagram?

Given that this improvement will make us move to some control of the mini map per diagram by the specifier. I don't mind seeing the control of the mini map by the end user being saved per diagram.

DSL vs. User Interaction: If we allow the default behavior to be set via the View DSL, should this value act as a fallback that is overridden once a user manually toggles the toolbar for that specific diagram?

I don't see any reason to absolutely prevent end users from activating the mini map at all cost. The specifier may want to hide it by default but I don't think they should be able to prevent the end users from using it. For me the specifier will control the initial state of the mini map when the diagram is created. After that, the end user can update this state (which will then be persisted).

Global Default: If we move toward DSL-defined defaults, should we remove the global preference entirely? Under this model, visibility would default to true unless explicitly defined otherwise in the DSL or through the specific user interaction.

I think we can remove the global default preference but it would just be replaced by a diagram instance specific preference. It would default to the state specified by the backend and then be updated by user interactions. These interactions will be saved in the local storage.

Can you create a pitch using the template in doc/iterations/YYYY-MM/shapes/shape.adoc and submit a PR for that. It will allow us to capture these choices and evaluate their impact. Thanks.

[florianbarbin]

Can you create a pitch using the template in doc/iterations/YYYY-MM/shapes/shape.adoc and submit a PR for that. It will allow us to capture these choices and evaluate their impact. Thanks.

Done here: #6302