-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Completion Report #223
Comments
This would be interesting to narrow down what information the user is interested in. Firstly I would imagine they would like to know the success state of the publish, so http://fontawesome.io/icon/check/
Do you mean when validation is done, or when integration and all processing is finished? |
I'm not sure if sliding to a different panel will be the best solution. Will validation then also bring you to that panel? And what if you'd still want to trigger the actions quickly? We'll need to ensure whatever we do doesn't get in the way with how users are currently using it. How about something like this?
The bottom bar could slide up after it finishes processing. It could even be up, directly after Collecting and show something like "Ready to process" or alike, but that might be a bit too much clutter. |
Oo, that looks very nice. 👍 |
Like that too 👍 |
I would suggest an intermediate stage before attempting to implement that exact look, depending on how much time investment you are interested in making versus the amount of gain from solving the problem. Initially, getting a static status bar with "Finished" displayed until any button is pressed would be much easier. There are signals already in place, and a new bar could be added and hooked up relatively easily. |
Note that this is almost an exact copy of the top of the "Inspector" (or what's the panel called when you inspect a plug-in or instance?) |
Goal
Provide a summary of publish to the end user.
Implementation
Upon finishing validation of publish, slide the user to a panel dedicated to providing an overview of what happened.
The text was updated successfully, but these errors were encountered: