Scratchaddons: More options for userscript matches (not only URLs)

[WorldLanguages]

Let's say a userscript only works on user profiles. The current match would currently be https://scratch.mit.edu/users/*/, why not just userprofile? And other potential filters for common use.

[WorldLanguages]

I believe it's too late to implement this. It's not a big deal, either. Closing

[Hans5958]

too late

[TheColaber]

I believe this one is worth reopening. Once we implement #390, addons that work on the editor/project page would also need to work on turbowarp's editor/project page. If we simply said for the match URL to be project, then we could have the match URL patterns for both turbowarp and scratch to link to htpps://scratch.mit.edu/projects/* and https://turbowarp.org/* (excluding the https://turbowarp.org/privacy.html page). And, if we end up supporting addons on another site, then it would be useful there too. This would also help with #646. And I think it's just easier if all the user needed to add in their addon, was just search or user

[RedGuy12]

And phosphorous

From: TheColaber [e-mail]
Sent: Friday, January 1, 2021 9:58 AM
To: ScratchAddons/ScratchAddons [e-mail]
Cc: Subscribed [e-mail]
Subject: Re: [ScratchAddons/ScratchAddons] More options for userscript matches (not only URLs) (#23)

I believe this one is worth reopening. Once we implement #390https://github.com/ScratchAddons/ScratchAddons/issues/390, addons that work on the editor/project page would also need to work on turbowarp's editor/project page. If we simply said for the match URL to be project, then we could have the match URL patterns for both turbowarp and scratch to link to htpps://scratch.mit.edu/projects/* and https://turbowarp.org/* (excluding the https://turbowarp.org/privacy.html page). And, if we end up supporting addons on another site, then it would be useful there too. This would also help with #646https://github.com/ScratchAddons/ScratchAddons/issues/646. And I think it's just easier if all the user needed to add in their addon, was just search or user

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/ScratchAddons/ScratchAddons/issues/23#issuecomment-753332609, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOT5DEQDTPZ3DOJW64VZXWLSXXWKLANCNFSM4PL5ILKA.

[WorldLanguages]

I believe this one is worth reopening. Once we implement #390, addons that work on the editor/project page would also need to work on turbowarp's editor/project page. If we simply said for the match URL to be project, then we could have the match URL patterns for both turbowarp and scratch to link to htpps://scratch.mit.edu/projects/* and https://turbowarp.org/* (excluding the https://turbowarp.org/privacy.html page). And, if we end up supporting addons on another site, then it would be useful there too. This would also help with #646. And I think it's just easier if all the user needed to add in their addon, was just search or user

I honestly doubt userscript made for the Scratch editor could work "as-is" on TurboWarp, so it wouldn't make sense to merge both origins into one permission - an addon might only work on the Scratch editor

[RedGuy12]

Well maybe userstyles

Paul Reid

---

From: World_Languages [e-mail]
Sent: Friday, January 1, 2021 3:15:04 PM
To: ScratchAddons/ScratchAddons [e-mail]
Cc: Paul Reid [e-mail]; Comment [e-mail]
Subject: Re: [ScratchAddons/ScratchAddons] More options for userscript matches (not only URLs) (#23)

I believe this one is worth reopening. Once we implement #390https://github.com/ScratchAddons/ScratchAddons/issues/390, addons that work on the editor/project page would also need to work on turbowarp's editor/project page. If we simply said for the match URL to be project, then we could have the match URL patterns for both turbowarp and scratch to link to htpps://scratch.mit.edu/projects/* and https://turbowarp.org/* (excluding the https://turbowarp.org/privacy.html page). And, if we end up supporting addons on another site, then it would be useful there too. This would also help with #646https://github.com/ScratchAddons/ScratchAddons/issues/646. And I think it's just easier if all the user needed to add in their addon, was just search or user

I honestly doubt userscript made for the Scratch editor could work "as-is" on TurboWarp, so it wouldn't make sense to merge both origins into one permission - an addon might only work on the Scratch editor

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/ScratchAddons/ScratchAddons/issues/23#issuecomment-753383169, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOT5DESCRGJABLPA6US4W6TSXY3NRANCNFSM4PL5ILKA.

[TheColaber]

I honestly doubt userscript made for the Scratch editor could work "as-is" on TurboWarp, so it wouldn't make sense to merge both origins into one permission - an addon might only work on the Scratch editor

I'm sure that most do, and some (like project-notes-tabs) could easily be fixed by adding an if statement to not run at all.