when green flag clicked

do everything on list [ what to do]

when green flag clicked
Do Everything :: custom

TheUniversalWorld1 wrote:

I don't see the point in using just two blocks or what the bottom block would do, you can say you did it with two blocks by making a custom block that does everything like:

when green flag clicked
Do Everything :: custom

No support.

replace item ( v) of [  v] with [ ]

Mine-scratch wrote:

replace item ( v) of [  v] with [ ]

rollercoasterfan wrote:

Uh, this is impossible. This turns scratch into a text based coding language, because you have to type code into a list. I don't think it would recognize this very well, and would be hard to implent. It's not a competion to see who can use the fewest amount of blocks. No support.

PrincessPanda_test_ wrote:

rollercoasterfan wrote:

Uh, this is impossible. This turns scratch into a text based coding language, because you have to type code into a list. I don't think it would recognize this very well, and would be hard to implent. It's not a competion to see who can use the fewest amount of blocks. No support.

As per rollercoasterfan.

Pot-of-Gold wrote:

PrincessPanda_test_ wrote:

rollercoasterfan wrote:

Uh, this is impossible. This turns scratch into a text based coding language, because you have to type code into a list. I don't think it would recognize this very well, and would be hard to implent. It's not a competion to see who can use the fewest amount of blocks. No support.

As per rollercoasterfan.

as per this

rollercoasterfan wrote:

TheUniversalWorld1 wrote:

I don't see the point in using just two blocks or what the bottom block would do, you can say you did it with two blocks by making a custom block that does everything like:

when green flag clicked
Do Everything :: custom

No support.

No, he meant truly two blocks, because the second block does everything found in a certain list. Yeah, um, no.

Iditaroid wrote:

Sounds like something you could do in Snap/BYOB…

Doyousketch2 wrote:

I like the idea, but not for that reason.

The way it was explained might be hard for kids to follow,
because all your code would all be hidden in a list,
and the core reason for Scratch is to illustrate programs to kids.

However, I think converting a Scratch program to scratchblocks text
and/or vice versa would be interesting, and perhaps even beneficial.

Especially for the forums,
as you could output scratchblocks text and place it here for others to view,
then convert someones script back into Scratch,
perhaps through your your backpack, to place into your program.

This would make backpacks more versatile, and collaboration so much more open,
because information could be passed back-and-forth more easily this way.

When you right-click on the backpack, instead of just delete,
you'd get “import script” and “export script” as options,
and scratchblocks text would copy by way of your clipboard.

Also, there are times when text editing a program can be quite handy,
such as being able to use “find and replace.”

So again, I support the idea of text-to-scratch, and I think it's do-able,
as the scratchblocks code has been pretty thoroughly tested.

It would just need to be modified so that instead of converting to HTML,
scratchblocks convert actual blocks in the backback.

Doyousketch2 wrote:

I like the idea, but not for that reason.

The way it was explained might be hard for kids to follow,
because all your code would all be hidden in a list,
and the core reason for Scratch is to illustrate programs to kids.

However, I think converting a Scratch program to scratchblocks text
and/or vice versa would be interesting, and perhaps even beneficial.

Especially for the forums,
as you could output scratchblocks text and place it here for others to view,
then convert someones script back into Scratch,
perhaps through your your backpack, to place into your program.

This would make backpacks more versatile, and collaboration so much more open,
because information could be passed back-and-forth more easily this way.

When you right-click on the backpack, instead of just delete,
you'd get “import script” and “export script” as options,
and scratchblocks text would copy by way of your clipboard.

Also, there are times when text editing a program can be quite handy,
such as being able to use “find and replace.”

So again, I support the idea of text-to-scratch, and I think it's do-able,
as the scratchblocks code has been pretty thoroughly tested.

It would just need to be modified so that instead of converting to HTML,
scratchblocks convert actual blocks in the backback.