Skip to content
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

Music: support flyout toolbox #52941

Merged
merged 5 commits into from
Jul 21, 2023
Merged

Music: support flyout toolbox #52941

merged 5 commits into from
Jul 21, 2023

Conversation

breville
Copy link
Member

@breville breville commented Jul 21, 2023

This adds support for an optional Music Lab level property, "type": "flyout", which will show a toolbox with all blocks shown all the time, without categories.

It seems this could be helpful in early levels in a progression, when only a few blocks will be available.

The toolbox section of the level data has been changed a little, to have separate "blocks" and optional "type" entries.

flyout toolbox

Screenshot 2023-07-21 at 12 43 38 AM

categories toolbox (default)

Screenshot 2023-07-21 at 12 43 43 AM

@breville breville requested review from moneppo and a team July 21, 2023 07:55
Copy link
Contributor

@sanchitmalhotra126 sanchitmalhotra126 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few minor things but LGTM! Nice addition!

| http://studio.code.org/s/allthethings/lessons/46/levels/2 | music lab script level |
| http://studio.code.org/s/allthethings/lessons/46/levels/4 | music lab script level |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we change this to a standalone project URL (projects/music/new) so we don't need to worry about updating it if the allthethings progression changes?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We depend on allthethings for much of our UI testing, so I think it's reasonable to keep these particular levels in sync with UI tests.

Comment on lines 9 to 12
"toolbox": {
"Play": ["play_sound_at_current_location_simple2"]
},
"simpleToolbox": true,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor: should we nest this inside the "toolbox" field? Something like

"toolbox": {
   "blocks": { "Play": [...] },
   "simple": true,
   // alternatively
   "type": "flyout" / "category"
}

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea. I was opting for legacy compatibility, but we're still at the stage where we should build the ideal format, and this is closer to that!

@breville breville changed the title Music: simple toolbox Music: support flyout toolbox Jul 21, 2023
@breville breville merged commit 5f85549 into staging Jul 21, 2023
2 checks passed
@breville breville deleted the music-simple-toolbox branch July 21, 2023 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants