Skip to content

Move project player addons to a top-level category - #3955

Merged
Samq64 merged 24 commits into
ScratchAddons:masterfrom
Samq64:player
Dec 27, 2024
Merged

Move project player addons to a top-level category#3955
Samq64 merged 24 commits into
ScratchAddons:masterfrom
Samq64:player

Conversation

@Samq64

@Samq64 Samq64 commented Dec 19, 2021

Copy link
Copy Markdown
Member

Resolves #3014

Changes

Moves project player addons to a new top-level category under the Scratch Editor Features category. Since other the other top-level category tags are short, the projectPlayer tag has been renamed to just player.

Reason for changes

It's confusing for project player addons to be a subcategory of editor addons since those addons also affect the project page and embeds.

Tests

Tested on Edge 96.

Comment thread webpages/settings/data/tags.js Outdated
@WorldLanguages

Copy link
Copy Markdown
Member

@mxmou Do you like this? I'm not convinced. (asking you since you made the issue that suggested this)

@Samq64

Samq64 commented Dec 22, 2021

Copy link
Copy Markdown
Member Author

There's only one theme in the project player themes, so maybe it would be better to get rid of the project player themes category completely.

@lisa-wolfgang lisa-wolfgang added the scope: webpages Related to the web pages (settings page, pop-up, etc) label Dec 23, 2021
@WorldLanguages

Copy link
Copy Markdown
Member

Honestly I don't really like this. IMO the project player is part of the editor.

@mxmou

mxmou commented Dec 24, 2021

Copy link
Copy Markdown
Member

Honestly I don't really like this. IMO the project player is part of the editor.

It's also part of the website.

@apple502j

Copy link
Copy Markdown
Member

Manifest: ScratchAddons/manifest-schema#56

@danielgallab

danielgallab commented Jan 16, 2022

Copy link
Copy Markdown
Member

In my opinion, I agree with this being a separate category. The player which can be found in 3 places (projects/*/, projects/*/editor, projects/*/embed). I don't think that to change something in an embed, you have to look under the editor section. And @mxmou argued that this could technically also be a website addon since you can find it there too. I think that when most people think of an "editor" addon, they think of scripts that can run on projects/*/editor. However, all of these scripts that run, run on "projects", which are all 3, project page, project editor, and project embed. This is why I think they should have their own category.

@WorldLanguages

Copy link
Copy Markdown
Member

I'm not convinced this should be merged, but I was more skeptical a few months ago.

Some issues I see:

  1. There's less than 10 projectPlayer addons. And I'm not sure if clones and mouse-pos should be counted, because they only appear when inside the editor, and aren't helpful when viewing someone else's project.
  2. The "Scratch Editor Features" would have 3 subcategories instead of four, making it less consistent with Scratch Website Features.
  3. The sidebar of the settings page is already filled on low resolution screens. Adding one more button would hide the "more settings" button for some users.

@mxmou

mxmou commented Apr 6, 2022

Copy link
Copy Markdown
Member
  1. There's less than 10 projectPlayer addons. And I'm not sure if clones and mouse-pos should be counted, because they only appear when inside the editor, and aren't helpful when viewing someone else's project.

Clones and mouse-pos are editor addons. I don't think this is an issue - there aren't many popup addons either.

  1. The "Scratch Editor Features" would have 3 subcategories instead of four, making it less consistent with Scratch Website Features.

Why is that important? More subcategories can be added later if there are enough addons for the same part of the editor.

  1. The sidebar of the settings page is already filled on low resolution screens. Adding one more button would hide the "more settings" button for some users.

The category buttons are very big - reducing all of them to the size of "small" ones (Credits, Help Translate, Send Feedback) would add enough space for adding another button. The header could be slightly smaller too.

@WorldLanguages

Copy link
Copy Markdown
Member

Sorry, I forgot to reply.

Clones and mouse-pos are editor addons. I don't think this is an issue - there aren't many popup addons either.

I think I created the popup category because having "message count in extension icon" as a website addon was too weird. It did involve the Scratch website in a way, because the message count is taken from there, but in no way it modifies the Scratch website and it doesn't even link to it.
Having project player addons inside editor addons isn't as weird as that.

Why is that important? More subcategories can be added later if there are enough addons for the same part of the editor.

Okay, good point. We have tags such as comments but they aren't shown as different subcategories because there's not enough addons with those tags.

The category buttons are very big - reducing all of them to the size of "small" ones (Credits, Help Translate, Send Feedback) would add enough space for adding another button. The header could be slightly smaller too.

That could work.

@WorldLanguages

Copy link
Copy Markdown
Member

Am I missing any addon that could fit into this category? I previously said clones and mouse-pos are targeted for developing a project, not for watching projects, so those don't really fit. Also, please see what I say at the end about remove-curved-stage-border.

  • 60fps
  • fullscreen
  • gamepad
  • mute-project
  • pause
  • remove-curved-stage-border (would this addon stay as a theme? would we need to create a "themes for project player" subcategory? this one is very confusing)

@Samq64

Samq64 commented Apr 15, 2022

Copy link
Copy Markdown
Member Author

Done. The project player themes sub-category already existed, but I removed it.

@mxmou mxmou added the status: pending A PR is still not ready to merge, or an issue is being worked on/on consideration label Jun 12, 2022
@mxmou

mxmou commented Jun 12, 2022

Copy link
Copy Markdown
Member

Added "pending" because the spacing of the category selector needs to be reduced first.

@Samq64 Samq64 removed the status: needs review PR needs 1 more approval label Dec 7, 2023
@Samq64

Samq64 commented Feb 3, 2024

Copy link
Copy Markdown
Member Author

This is still on the v1.36 milestone but Vue 3 is on v1.38. Is that the case or is this one also being pushed back to 1.38? I don't mind fixing the merge conflicts.

@Samq64 Samq64 removed the status: pending A PR is still not ready to merge, or an issue is being worked on/on consideration label Feb 3, 2024
@WorldLanguages WorldLanguages modified the milestones: v1.36.0, v1.37.0 Feb 6, 2024
@Samq64

Samq64 commented Mar 11, 2024

Copy link
Copy Markdown
Member Author

Is this still planned for 1.37? Both Mxmou and DNin previously approved.

@WorldLanguages

Copy link
Copy Markdown
Member

Hmm, I'll be looking at this after the MV3 release. Sorry.

@WorldLanguages WorldLanguages modified the milestones: v1.37.0, v1.39.0 Mar 17, 2024
@Samq64 Samq64 added the status: needs review PR needs 1 more approval label Jul 22, 2024
@Samq64 Samq64 modified the milestones: v1.39.0, v1.40.0 Aug 3, 2024
@Samq64 Samq64 modified the milestones: v1.40.0, v1.41.0 Aug 18, 2024
@Samq64
Samq64 requested a review from mxmou December 26, 2024 21:48
@mxmou

mxmou commented Dec 27, 2024

Copy link
Copy Markdown
Member

The getEnabledAddons("editor") calls in turbowarp-player and live-featured-project should probably be changed to getEnabledAddons("player").

@mxmou mxmou removed the status: needs review PR needs 1 more approval label Dec 27, 2024
@Samq64
Samq64 merged commit 74d35a3 into ScratchAddons:master Dec 27, 2024
@Samq64
Samq64 deleted the player branch December 27, 2024 15:14
@Samq64

Samq64 commented Dec 27, 2024

Copy link
Copy Markdown
Member Author

@Hans5958 For the manifest schema does it need to be a new version or do I edit the existing one?

@DNin01

DNin01 commented Dec 27, 2024

Copy link
Copy Markdown
Member

@Hans5958 For the manifest schema does it need to be a new version or do I edit the existing one?

I'm pretty sure we should bump the schema to a new version. The last schema hasn't changed for a few releases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

scope: addon.json About the addon.json file structure scope: user experience Related to the user experience (UX) aspect of the extension scope: webpages Related to the web pages (settings page, pop-up, etc)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Separate project player addons from editor addons

10 participants