Basic88 wrote:

Is this what you mean?

From what I understand, that's what @HTML-Fan means.
But you can still clarify.

Basic88 wrote:

Comment Blocks? I don't understand this much :P
Like text based syntax?

function (what?)
–comment mwahaha
end
I see. Could you create a mockup so we can understand better? I don't know if I support

Yeah, sure:
https://pic.useful.fi/zIz_ITE0s.png

Basic88 wrote:

Is this what you mean?

Yes, you are correct, but just know that u could also add text.

Would this use the /scratchblocks plugin? I get the idea, but I'm a little confused on if it's possible to implement with the current layout. How would the editor detect if the block is just being put somewhere or if it's being put in a comment?

qrcool wrote:

Would this use the /scratchblocks plugin? I get the idea, but I'm a little confused on if it's possible to implement with the current layout. How would the editor detect if the block is just being put somewhere or if it's being put in a comment?

1. No, you just drag the blocks in
2. The same way when you have multiple scripts close together.

Ok. Probably possible, as similar detection code has been done before, but how would the transition from text to block and vice versa go? Would be like quotes on the forums, where it starts a new line?

It would probably help people who know those programming languages and also want to learn Scratch (or vice versa) learn the (programming language) to Scratch function. Support.

qrcool wrote:

Ok. Probably possible, as similar detection code has been done before, but how would the transition from text to block and vice versa go? Would be like quotes on the forums, where it starts a new line?

Yes, exactly.

bump… don't quote this… bad things happen…

Workaround:

define comment 1
if < (1) = (0) > then // so it skips
 comments :: grey stack
end
stop [this script v]
when gf clicked
... :: grey stack
comment 1 // look up!

I know it's a little troublesome, but it's all I can think of. Maybe you can put it beside the main script?

EDIT: Fixed some logic errors.

TheColaber wrote:

As you may know…
https://en.scratch-wiki.info/w/images/thumb/Scratch_3.0_Comment_Programming.PNG/320px-Scratch_3.0_Comment_Programming.PNG
… Currently in scratch, you can only comment text. I think it would be great to also be able to comment blocks, like in other programming languages… I guess in order to comment blocks, you could drag and drop them into a comment…

Here is a little example: (by @Basic88)
https://mv-ezproxy-com.ezproxyberklee.flo.org/get_image/project/413020675_200x180.png


What do you think… Support, or No Support and why? (support recommended)

I support this

Byron_Inc wrote:

Workaround:

define comment 1
if < (1) = (0) > then // so it skips
 comments :: grey stack
end
stop [this script v]
when gf clicked
... :: grey stack
comment 1 // look up!

I know it's a little troublesome, but it's all I can think of. Maybe you can put it beside the main script?

EDIT: Fixed some logic errors.

Uh… this isn't it… my OP was stating to have the option to have blocks in a comment like this:

The end result would be something like this:

bump

Bump

There is an issue with this:
In the example above, there is a hat block there.
Should blocks in comments get executed? If no, that might confuse people. If yes, that kind of defeats the point of commenting the code to show, but not run it.

I don't really see how this would be useful, so I semi-support.

thr565ono wrote:

There is an issue with this:
In the example above, there is a hat block there.
Should blocks in comments get executed? If no, that might confuse people. If yes, that kind of defeats the point of commenting the code to show, but not run it.

If in a comment, it will not run. Btw, how would this confuse people, all programming languages allow you to comment code…

donotforgetmycode wrote:

I don't really see how this would be useful, so I semi-support.

This would be useful for testing things and writing comments about a snip of code. Plus, you can write and add blocks on the same comment above and under code.

bump… it's been a while hasn't it?

bump