Toolbarmode
No edit summary
No edit summary
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Toolbarmode
<message>Write the content here to display this box</message>
If a TaggedValue of '''Toolbar=true''' is set on a ViewModel, toolbar mode is turned on for that ViewModel.


If a TaggedValue of Toolbar=true is set on ViewModel toolbar mode is turned on for that ViewModel.
If you set '''[[Documentation:SysMDrivenMiscSettingsSingleton|SysMDrivenMiscSettingsSingleton]].GlobalToolbarMode=true''', all views that do not have the TaggedValue of '''Toolbar=false''' will have gotten toolbar mode.


If you set [[SysMDrivenMiscSettingsSingleton]].GlobalToolbarMode=true all views that does not have TaggedValue of Toolbar=false will have get toolbar mode.
=== Main design ideas ===
ActionRenderPosition LeftSide, ContextMenu, ToolBarLeft, ToolBarRight


===== Implementation notes =====
Two distinct types of actions:
ActionRenderPosition LeftSide,ContextMenu,ToolBarLeft, ToolBarRight


Toolbar in Turnkey - Two distinct types of actions:
'''<nowiki>#</nowiki>1''' Those that DONTCHANGESTUFF+Navigates-> Stays on leftside,


<nowiki>#</nowiki>1 Those that DONTCHANGESTUFF+Navigates-> Stays on leftside,  
'''<nowiki>#</nowiki>2''' Others(data changers, even navigating) + save, cancel, Edit(ReadOnlySwitch) goes into new horizontal toolbar below mainmenu


<nowiki>#</nowiki>2 Others(data changers, even navigating)  + save,cancel,Edit(ReadOnlySwitch) goes into new horizontal toolbar below mainmenu
* End in mind : reduce left menu. It will only hold safe, ViewModel-top-level navigations without side effects - as such, it will not blink or act dynamic
* Nesting level actions are only available via context-menu in grid (context menu content will probably also be divided into the 2 types of actions)
* This new style is optional (since adoption is not the same for all projects)
* The ability to find #1 type of actions relies on the new ReadOnly-functionality(that can deduce if action changes data or not)


- End in mind : reduce left menu, it will only hold safe, ViewModel-top-level navigations without side effects, as such it will not blink or act dynamic
[[File:Documentation Toolbarmode 1727251023851.png|frameless|684x684px]]
 
- Nesting level actions are only available via context-menu in grid (context menu content will probably also be divided into the 2 types of actions)
 
- This new style must be optional (since adoption is not the same for all projects)
 
- The ability to find #1 type of actions relies on the new ReadOnly-functionality(that can deduce if action changes data or not)
 
- The suggested rendering position (topleftmenu,nestingleftmenu,toolbar) will need to be attached to actions sent to client so that client may use for filtering and rendering

Latest revision as of 07:57, 25 September 2024

If a TaggedValue of Toolbar=true is set on a ViewModel, toolbar mode is turned on for that ViewModel.

If you set SysMDrivenMiscSettingsSingleton.GlobalToolbarMode=true, all views that do not have the TaggedValue of Toolbar=false will have gotten toolbar mode.

Main design ideas

ActionRenderPosition LeftSide, ContextMenu, ToolBarLeft, ToolBarRight

Two distinct types of actions:

#1 Those that DONTCHANGESTUFF+Navigates-> Stays on leftside,

#2 Others(data changers, even navigating) + save, cancel, Edit(ReadOnlySwitch) goes into new horizontal toolbar below mainmenu

  • End in mind : reduce left menu. It will only hold safe, ViewModel-top-level navigations without side effects - as such, it will not blink or act dynamic
  • Nesting level actions are only available via context-menu in grid (context menu content will probably also be divided into the 2 types of actions)
  • This new style is optional (since adoption is not the same for all projects)
  • The ability to find #1 type of actions relies on the new ReadOnly-functionality(that can deduce if action changes data or not)

Documentation Toolbarmode 1727251023851.png

This page was edited 3 days ago on 09/25/2024. What links here