When you select an option in the menu (can't be bothered to make a mockup because i'm lazy), there would be an option called “Print Code”.
This would open up a printer dialog, where you could print out all the code of the sprite that was selected when you pressed “Print Code”. It would print one script per page.

Could you explain more?

Abstract- wrote:

Could you explain more?

Like what?

IgDegOo wrote:

Abstract- wrote:

Could you explain more?

Like what?

Okay, so what i understood, was that you can print code,one script per page.

1. Would it be black/white?
2. How would Scratch connect to the printer?
3. What if the script was:

when green flag clicked
hide

Does it still get it's own page? What about extra blocks you didn't delete?
4. What if the script is so long it needs more than one page?

Abstract- wrote:

IgDegOo wrote:

Abstract- wrote:

Could you explain more?

Like what?

Okay, so what i understood, was that you can print code,one script per page.

1. Would it be black/white?
2. How would Scratch connect to the printer?
3. What if the script was:

when green flag clicked
hide

Does it still get it's own page? What about extra blocks you didn't delete?
4. What if the script is so long it needs more than one page?

1-2: The printer dialog handles that, and I think Flash has it's own built-in printer dialog. (Stress the I think)

3. It prints it out, it doesn't run it!

And each lonely block(s) counts as a script.

4. Then it would make new pages whenever it went longer than the set paper until the script finishes, then it would continue.

No support for giving each script it's own page. Then we result with near-empty pages with just this-

move (10) steps

But I do support the idea of printing scripts. I think that printed scripts should not be reorganized, but instead should just be printed the way they are displayed in the editor.

This argument was terrible

MathlyCat wrote:

What benefit does this give the community?
Also, Flash is TERRIBLE. They're working on an HTML5 version of the site so…

No support.

No need to sound rude.

*cringe*

DaSpudLord wrote:

No support for giving each script it's own page. Then we result with near-empty pages with just {move (10) steps}
But I do support the idea of printing scripts. I think that printed scripts should not be reorganized, but instead should just be printed the way they are displayed in the editor.

This exactly.

Also, maybe the block categories should have slight, distinct dithering patterns in this feature, to optimize a bit more for grayscale printers.

DaSpudLord wrote:

No support for giving each script it's own page. Then we result with near-empty pages with just this-

move (10) steps

But I do support the idea of printing scripts. I think that printed scripts should not be reorganized, but instead should just be printed the way they are displayed in the editor.

Ah ok. Never mind the OP.
So I'm guessing it would keep printing as many scripts as it could on one page, and once the script went all the way to the end of the page, it would start another page?

MathlyCat wrote:

IgDegOo wrote:

MathlyCat wrote:

What benefit does this give the community?
Also, Flash is TERRIBLE. They're working on an HTML5 version of the site so…

No support.

No need to sound rude.

I'm not being rude. I only asked a question; don't draw conclusions so quickly my fellow.

Just because something won't make a big impact doesn't mean you should

MathlyCat wrote:

draw conclusions so quickly my fellow.

Support! I was making a game for Ludum Dare once in Processing, and ran into a stupid bug that I could only solve after I printed it out onto paper and traced out the code execution with my pencil. Sometimes it really helps. (Plus, Scratch blocks are pretty and it would be fun to print one out and hang it in my room. )

The browser and OS handle printing dialogs typically, all that Scratch needs to do is assemble a picture of them and request for them to be printed.

bump

IgDegOo wrote:

Abstract- wrote:

IgDegOo wrote:

Abstract- wrote:

Could you explain more?

Like what?

Okay, so what i understood, was that you can print code,one script per page.

1. Would it be black/white?
2. How would Scratch connect to the printer?
3. What if the script was:

when green flag clicked
hide

Does it still get it's own page? What about extra blocks you didn't delete?
4. What if the script is so long it needs more than one page?

1-2: The printer dialog handles that, and I think Flash has it's own built-in printer dialog. (Stress the I think)

3. It prints it out, it doesn't run it!

And each lonely block(s) counts as a script.

4. Then it would make new pages whenever it went longer than the set paper until the script finishes, then it would continue.

It would need to connect to Scratch to “See” (XD) the blocks.

*cringe*

bump

No support. I'm just wondering how (removed by moderator - please keep it polite) this would work though, and the practical application of this. I mean, for it to make sense you'd have to print out everything as it is, otherwise how would it know which to group on what page, in addition some scripts are massive and wouldn't fit. Even if you have it all printed out, what do you do with it? It won't help you visualise script, since it'll be decided up into pages and you're looking through a packet, not to mention packet for every sprite, it'd be a huge waste. So let's scrap the printing idea and go to lets have an option to screenshot all of a sprite's script and save that. Well problems there too, being the image would be massive and pretty high quality so the file would be ginormous. I do see some merit to this as a way of displaying your script and being able to see it without going into editor, but I just don't think it'd be worth it and it wound only benefit a small population

no support, just take a screenshot of the code and print that. i don't know what it is on windows, but on iOS it's command+shift+4, then drag the cursor over the area of code.

therealpsy wrote:

no support, just take a screenshot of the code and print that. i don't know what it is on windows, but on iOS it's command+shift+4, then drag the cursor over the area of code.

I was going to say that

It may be a bit difficult to screenshot everything but I don't think this printing feature will be used by a majority of the community anyway.