This addon has already been submitted in #7748 but I haven't checked the differences in the implementation yet.

This addon has already been submitted in #7748 but I haven't checked the differences in the implementation yet.

Hmm. Mine only supports english, but does give better (and less buggy) output.

Also, there's another implementation that might be possible - just reading the fields in the blocks instead of hardcoding everything. This would give complete language support too.

I tried this a while ago when the forums were still using 2.0 scratchblocks. It didn't work, because a lot of 3.0 blocks have different text from their 2.0 counterparts, and language support was an issue too - but I think it could work with the 3.0 scratchblocks.

@WorldLanguages could you review?

If this will only support English, it might be a good thing to add a note to the addon explaining that that's intentional (for users of other languages)?

When copying from a language other than English, the dropdowns are not translated, leading to a weird mix of languages:

When copying from a language other than English, the dropdowns are not translated, leading to a weird mix of languages:

Fixed.

If this will only support English, it might be a good thing to add a note to the addon explaining that that's intentional (for users of other languages)?

How should it be worded? It needs to be clear that users can use it no matter what their editor language is.

Edit: is this alright?

How should it be worded? It needs to be clear that users can use it no matter what their editor language is.

I don't think it's necessary to clarify that.

Edit: is this alright?

Sure, looks alright to me. Something along the lines of This addon can only output English scratchblocks code. as an info (no need to make it a notice!)

This conflicts with the other editor-copy-scratchblocks addon I'm working on in PR #7748. There is this addon by just-a-hriday, and another version by me with different code but the same basic features and addon ID.

There are advantages of both versions of the addon. My addon uses the parse-sb3-blocks library by apple502j for block conversion, it has a few bugs but support for (almost?) every block and language in the Scratch editor.

On the other hand, hriday's addon accesses blocks more directly and uses less code, but does not support other languages. I think language support is important for non-English Scratchers who write Forum posts, Scratch Wiki pages and other things, though most parts of the Forums only support blocks in English.

It's fine if you want to use this version of the addon instead of mine. I just don't know if I should keep working on this or not.

@Samq64 How should I add support for turbowarp blocks? Is there a way to check whether the addon is being run in turbowarp? It doesn't make much sense to add hardcoded turbowarp blocks inside the scratch editor too.

I think mainatining return [], <is compiled>, etc. in Turbowarp's fork of Scratch Addons is fine. If you want to support all of Turbowarp's extensions though then the mapping approach isn't really feasible since there are almost 100 of them now.

The mapping is significantly simpler for turbowarp. With vanilla scratch blocks you have to work around all the inconsistencies and idiosyncrasies of scratchblocks. With the turbowarp blocks you have to override them all to make them render correctly anyways, so it's much simpler. In fact I think it's possible to automate mapping the extension blocks, and I believe that's the best solution here.

For turbowarp blocks Lu Yifei's approach works well too. However it is not reliable for vanilla scratch blocks, so a complicated hybrid approach would have to be used in order to use that method for turbowarp extension blocks and mine for the vanilla blocks. On the other hand there's no need to build mappings for those 100+ extensions if it's done that way.

If you used the scratch-translations then you'll get most of the mapping for free. But it would require quite a large change to how you're doing things. It is quite a different approach to things.

But you should be able to do most of it dynamically instead of having to hardcode things anymore.