You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, a user must right-click a block to display help for that single specific block but there doesn't seem to be a way to browse all block help at once.
If this exists, I think it should be either made more clear or I am missing something (wouldn't put it past me tbh) - I know there is a manual on how to use MB which contains all 'block' help but I don't this accessible enough. Moreover, I feel like it is bad user flow if the user can only view help for a block after dragging it out / right-clicking.
Mixing the 'browsability' of:
with:
could work quite well
I think we could (1) aggregate existing block help into the 'normal' HelpWidget (containing information about toolbar buttons and palette buttons) or (2) make a separate HelpWidget just for block help alone.
In favour of minimising the number of modals and dialogs MB, and to keep it simpler, I am leaning towards (1)
The text was updated successfully, but these errors were encountered:
aust-n
changed the title
Ability to browse 'block' help like 'normal' help
Suggested feature: Browse 'block' help like 'normal' help
Dec 20, 2018
One suggestion would be that there is an indication for where to find the block in the palette. Perhaps the palette opens to reveal the block location for block shown in help, or perhaps it shows only when the user clicks a show button.
I spend a lot of class time telling kids where to find blocks. If there is a way to assist the kids through design, I am all for it.
I think we don't want to rely on a list of blocks in turtledefs.js. We should figure out from the palettes what blocks are defined and walk through that list.
At the moment, a user must right-click a block to display help for that single specific block but there doesn't seem to be a way to browse all block help at once.
If this exists, I think it should be either made more clear or I am missing something (wouldn't put it past me tbh) - I know there is a manual on how to use MB which contains all 'block' help but I don't this accessible enough. Moreover, I feel like it is bad user flow if the user can only view help for a block after dragging it out / right-clicking.
Mixing the 'browsability' of:
with:
could work quite well
I think we could (1) aggregate existing block help into the 'normal' HelpWidget (containing information about toolbar buttons and palette buttons) or (2) make a separate HelpWidget just for block help alone.
In favour of minimising the number of modals and dialogs MB, and to keep it simpler, I am leaning towards (1)
The text was updated successfully, but these errors were encountered: