cursor.js -- translate cursor menu

[SharkPool-SP]

Resolves: #1987

I changed some naming or cursors, lmk if some others should be changed as well...

[Brackets-Coder]

Looks great

[yuri-kiss]

If you are going to do this preferably add an index for each item like native scratch, so people who dont know english (or the right value cause you changed the naming) can still use the block effectively.

that or we need to make a new block and use a field instead

[SharkPool-SP]

If you are going to do this preferably add an index for each item like native scratch, so people who dont know english (or the right value cause you changed the naming) can still use the block effectively.

that or we need to make a new block and use a field instead

done

[SharkPool-SP]

!format

[github-actions]

The formatting bot didn't find any formatting issues. It currently only checks the extensions folder. The author or a maintainer can run terminal command 'npm run format' manually to format all files.

[NexusKitten]

GarboMuffin in #1987:

if the names don't match the internal CSS names anymore, a lot of them could have much better names

The current names are meant to parody those used in the CSS "cursor" attribute. These names are not localized to any language except English, and so there's not really a reason to translate them unless we plan to change the names to make them more descriptive. I don't see anything wrong with doing so.

[GarboMuffin]

I don't think numbers will work here so we shouldn't suggest people to put numbers in

[SharkPool-SP]

Okay so just revert to the last commit

[NexusKitten]

preferably find a way to make the numbers work, as the issue stated in #2076 (review) still applies. probably would need to create a new block and hide the old version, since swapping from string values to indexes would change the extension's core functionality

[SharkPool-SP]

preferably find a way to make the numbers work, as the issue stated in #2076 (review) still applies. probably would need to create a new block and hide the old version, since swapping from string values to indexes would change the extension's core functionality

talk to garbo about it. Im not going back and forth with this

[yuri-kiss]

preferably find a way to make the numbers work, as the issue stated in #2076 (review) still applies. probably would need to create a new block and hide the old version, since swapping from string values to indexes would change the extension's core functionality

or just support both