Main menus, Menu items and context

[tparchambault]

Now that the Analyzer tab/tool is being fleshed out, it may be appropriate to revisit UX and tool workflow.

For example:

• The File menu items only make sense currently when one is in the Trust admin tool, as the Open, Save, Save As, Restore only apply to Trust edit sessions. Should File menu items change when in the Analyzer tool so that they are now relevant to Analysis.
• A separate top level menu with Fapolicyd specific operations. Nothing major but things like Restart, Status, Save State, Version, etc. Actions that leverage what we’ve already added under the hood but gives the user the ability to invoke them directly. Again all have to make sense from a UX perspective.
• Etc

An easy problem breakdown could be:

1. Does each tool get its own high level menu
2. Do all 'File' based operations go under the 'File' menu and then selectively grayed out depending on the current tool mode.

[tparchambault]

Based upon a CTC internal development discussion, File menu items will be (primarily) associated with user session files. The current json edit session files, which currently are focused on only saving Ancillary Trust Database Admin modifications, will be extended to support saving Analysis view state and any other tools embedded in the fapolicy-analyzer over its evolution.

A System menu is being consider to support user querying of the backend daemon.