Open Daniel-Warner-X opened 1 year ago
Somehow, the proposed design to me just looks like text it doesn’t look like an obvious Status.
Take a look at how GitHub does build status. It’s in a consistent status area and it’s super clear whether is Passed, Running, or Failed.
@kgilpin Here is an updated design that displays status messages under the header on each step of the install flow.
This is what it looks like in context...
Cool. I think the instructions need to be more conceptual - like add the AppMap package. Because requirements.txt is a Pip file. We don’t know that they are using Pip.
Let’s just explain overall what happens in this step.
Updated status messages... https://docs.google.com/document/d/1GcCgW6Kpvp4NaL76aMADM_UY6-y_EGQ7dvXGDKgiU1M/edit#
@dustinbyrne FYI...
@dustinbyrne I got a chance to install and use the .vsix. -- it's looking awesome! Three things jumped out at me right off the bat.
@dustinbyrne now that we have the new status message I think we can remove this:
Do you agree @kgilpin ?
@dustinbyrne now that we have the new status message I think we can remove this:
Do you agree @kgilpin ?
Yup, we do not need that any more.
The status messages for each step of the installation instructions are inconsistent with each other and most are not dynamic.
The status message should prompt the user to the next step if the status of that step is complete.
Add AppMap view:
Record AppMap view:
Explore AppMap view:
Runtime Analysis view:
The status messages need to be clear and consistent (text needed) and the presentation needs to be consistent from view to view so that the user understands the state of their install (design needed).
Design suggestion...