-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
ENA-115: Overview: Redesign save alerts to provide more info when project can’t save (Phase I) #6069
Comments
Technical stuff from a person who tried to implement it ( #5768 ) It's important to know that one asset can have multiple names. If you just have Also, Finally the big problem is: there are many ways this can fail. It can be a number from FetchTool (e.g. 403 (invalid session), 413 (too big), 500 (server error)), it can be These are tricky parts but I'm sure ST can do it. |
Wow! This looks great! The mockups are really great and the new styles also look helpfull. I also like being able to exit the alert. |
One design comment:
Perhaps a small "..." ellipsis bubble could be shown beneath the third reminder, if there is more than three present at once? |
Also this may be unrelated, but why is there "see community" instead of "see project page"? |
@Explosion-Scratch It's a slightly different design from the actual implementation (out of date probably); you can spot more slight inconsistencies in places like the costume editor toolbox. But yeah, those don't have anything to do with the slide notes regarding the save alerts project. |
The bitmap/vector switch and big block category names actually seem better than what we currently have. |
@mxmou, Probably lol. |
Yeah good observation :) It is a bit inconsistent based on what files I was using. You can ignore anything that doesn't look like what's in production right now |
Is it worth considering adding a confirmation on delete of sprite, and
sharing of your project while you are looking into these?
…On Fri, 7 Aug 2020 at 21:41, kathy wu ***@***.***> wrote:
@Explosion-Scratch <https://github.com/Explosion-Scratch> It's a slightly
different design from the actual implementation (out of date probably); you
can spot more slight inconsistencies in places like the costume editor
toolbox. But yeah, those don't have anything to do with the slide notes
regarding the save alerts project.
Yeah good observation :) It is a bit inconsistent based on what files I
was using. You can ignore anything that doesn't look like what's in
production right now
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#6069 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABTM3PTH64VVNORQEGDJN7TR7RRIJANCNFSM4PWEHO4A>
.
|
@griffpatch Probably but those might be for another issue, however, I would love those features as well. |
Any progress on this? |
Has any progress been made towards fixing this problem since the last posts? |
Any updates? |
Any progress on this? |
this shouldn't be too hard to implement, any more progress yet? |
Due to how saving works (and how it is done on three different components - WWW, GUI and Storage) this is actually more complicated than you imagine. But, this is not impossible; should definitely be implemented. |
Links
Specs: Customized alerts
Specs: Changes to nav
General spec
Background
Currently...
This design I made is what is currently implemented.
Here is an overview of the issues and pain points that we are solving in Phase I.
(There is a 4th pain point not listed in this image, which is that you can't create or upload a different project because you get stuck on this error.)
Related filed issues
#4045
#4225
#3764
Overview of Proposed Changes
Goals
— User can know how to debug or seek help
— User can continue working offline if they want, without alert as distraction
— User knows they're offline, separate from save status
Goal 1: Customize alerts to each situation
An asset is too big (most common and most problematic)
User gets signed out
Connectivity, can be Scratch side, or user side
Generic alert for any other case
What about multiple alerts?
There will generally be no situations where there are more than 1 of EACH TYPE of alert.
This is the order of operations in which they should appear:
HOWEVER...
There is a case within Use Case 1 where the user may encounter multiple "Asset too big" issues. On average it's between 1-3, but we've seen cases of ~5 or more on occasion.
In this case, follow this defined behavior for multiple alerts. Max alerts we will show at once is 3.
Goal 2 & 3 (changes to nav)
Goal 2: Show save status clearly in nav
Goal 3: Show connectivity more clearly
What is in Phase II?
At this time, we have decided to readdress the issues below in Phase II. Not yet scheduled.
Resolve File menu action behaviors
Asset too big: Preventative alerts
Revisit decision around sound editor buttons
Revisit nav state when your account session changes
Revisit "Save now" in nav
The text was updated successfully, but these errors were encountered: