Some sprites need to contain a lot of code. However, because all the code is on one giant “canvas”, it inevitably becomes very messy, and trying to view on most computers will cause Scratch to freeze.

My solution is to allow the code in sprites to be organized into “pages”, each of which can contain one or more scripts. Pages can be named, code can be moved between pages, and pages in the same sprite share their custom blocks.

Need to find a custom block? No more scrolling through an endless sea of blocks. Just find the page that it's in.
Need to edit the code? The computer doesn't need to render all 5000 blocks in the sprite's code, only the 200 or so in the page that you're working with. Now you don't have to wait for lag spikes to pass.

support, it's good to tidy the code up

It sounds like it would be effective for all reasons listed.

Dupe?

fdreerf wrote:

Dupe?

Seems like it.

Underrated.

Full support -
(1) Makes it more clean, and easy to use
(2) Similar to actual Programming
(3) You can keep custom-block definitions in one page/sheet, which makes it easier to edit code and the definition.
This should definitely be implemented.

Duped? Oh.