Opening to the rules view is a much better user experience as it does not immediately incur the expense of the trust load.
Thinking about it though, depending on the user's workflow, any of the views may be a good starting point. It might be nice to allow customization of which view the app starts on.
One side effect of not starting with the trust admin view is that the initial system will not be checked. Other views, like the analysis view, may need access to a checked trust database to provide accurate insight. So the check still needs done somehow.
The following is probably a separate issue, but leaving it here for now.
What if the trust check for the initial system was a task separate from any view, that runs when the app opens. It runs once regardless of what view the app starts on. Perhaps a single progress bar somewhere, like down in the status area could show the status of the background process.
From what I understand then the trust view would need to have progress bars, like it does now, that would show the progress of loading the trust into the table views. These progress bars would only be indicating the status of the UI load, as the check was already completed.
The special case with that would be when the trust view is your opening view, there would be the disk check progress bar, plus the trust table progress bars. How do they wire together?
It wouldn't even have to be the trust view is the starting view, could just be that the trust view is switched to prior to the check completing.
This relates to a few things that need reported
Trust check continues after switching from view (UI)
Trust check impacts focus on other views (UI)
Trust check is repeated when switching back to trust view (UI)
Opening to the rules view is a much better user experience as it does not immediately incur the expense of the trust load.
Thinking about it though, depending on the user's workflow, any of the views may be a good starting point. It might be nice to allow customization of which view the app starts on.
One side effect of not starting with the trust admin view is that the initial system will not be checked. Other views, like the analysis view, may need access to a checked trust database to provide accurate insight. So the check still needs done somehow.
The following is probably a separate issue, but leaving it here for now.
What if the trust check for the initial system was a task separate from any view, that runs when the app opens. It runs once regardless of what view the app starts on. Perhaps a single progress bar somewhere, like down in the status area could show the status of the background process.
From what I understand then the trust view would need to have progress bars, like it does now, that would show the progress of loading the trust into the table views. These progress bars would only be indicating the status of the UI load, as the check was already completed.
The special case with that would be when the trust view is your opening view, there would be the disk check progress bar, plus the trust table progress bars. How do they wire together?
It wouldn't even have to be the trust view is the starting view, could just be that the trust view is switched to prior to the check completing.
This relates to a few things that need reported