cookieclickerer33 wrote:

I would like to say this for all the people of this topic


This was LITERALLY A THING IN OLD SCRATCH VERSIONS
They removed it in 1.4 saying it would come back at a later point in time soon but not a single word sense then has been spoken about the feature

rdococ wrote:

cookieclickerer33 wrote:

I would like to say this for all the people of this topic


This was LITERALLY A THING IN OLD SCRATCH VERSIONS
They removed it in 1.4 saying it would come back at a later point in time soon but not a single word sense then has been spoken about the feature

Since when were custom reporters, etc in a 1.x version?

EngineerRunner wrote:

(#2479)
pre 1.x, originally there were both custom blocks and custom reporters where you just drag the “return” (or it might've been “report”) under the definition. custom blocks were readded in 2.0 but no custom reporters

he wrote:

TerryLeeStudio wrote:

ninjahanzo wrote:

TerryLeeStudio wrote:

-snip-

How is an input/reporter/boolean a block!?!?!?!

Maybe

tell it [1] :: custom cap

tell [] :: custom cap
say [] :: custom cap
report [] :: custom cap
return [] :: custom cap

EngineerRunner wrote:

rdococ wrote:

cookieclickerer33 wrote:

I would like to say this for all the people of this topic


This was LITERALLY A THING IN OLD SCRATCH VERSIONS
They removed it in 1.4 saying it would come back at a later point in time soon but not a single word sense then has been spoken about the feature

Since when were custom reporters, etc in a 1.x version?

pre 1.x, originally there were both custom blocks and custom reporters where you just drag the “return” (or it might've been “report”) under the definition. custom blocks were readded in 2.0 but no custom reporters

medians wrote:

(#2448)
12Jul04

ninjahanzo wrote:

TerryLeeStudio wrote:

ninjahanzo wrote:

TerryLeeStudio wrote:

-snip-

How is an input/reporter/boolean a block!?!?!?!

Maybe

tell it [1] :: custom cap

That's just weird in general. Ok, here is some better versions:

tell [] :: custom cap
say [] :: custom cap
report [] :: custom cap
return [] :: custom cap

definе (sgn(x :: custom) :: custom-arg) :: custom hat
{
if <(x :: custom-arg)=(0)> then
tell (sgn(x :: custom) :: custom-arg) [0] :: custom cap
else
tell (sgn(x :: custom) :: custom-arg) ((x :: custom-arg)/((abs v) of (x :: custom-arg))) :: custom cap
} (tell (sgn(x :: custom-arg) :: custom) () :: custom-arg cap) :: custom cap

mumu245 wrote:

medians wrote:

(#2448)
12Jul04

12Jul04???

medians wrote:

EngineerRunner wrote:

rdococ wrote:

cookieclickerer33 wrote:

I would like to say this for all the people of this topic


This was LITERALLY A THING IN OLD SCRATCH VERSIONS
They removed it in 1.4 saying it would come back at a later point in time soon but not a single word sense then has been spoken about the feature

Since when were custom reporters, etc in a 1.x version?

pre 1.x, originally there were both custom blocks and custom reporters where you just drag the “return” (or it might've been “report”) under the definition. custom blocks were readded in 2.0 but no custom reporters

That's not 1.4 though, custom blocks didn't exist in 1.x technically.
Also, to show what they mean (in 12Jul04):
https://scratch.mit.edu/discuss/post/7333838/

TerryLeeStudio wrote:

ninjahanzo wrote:

TerryLeeStudio wrote:

ninjahanzo wrote:

TerryLeeStudio wrote:

-snip-

-snip-

-snip-

-snip-

I see…I choose ‘tell it’ instead of ‘tell the reporter’ because new scratchers may not know what that mean, we want this to be as intuitive as the regular custom blocks, simply tell implies that it’s telling the stage to do so, don’t want to use ‘say’ because it will be confused with the speech bubble say ‘…’ block, maybe this?
-snip-

dogeiscut wrote:

(#2456)

TerryLeeStudio wrote:

I see…I choose ‘tell it’ instead of ‘tell the reporter’ because new scratchers may not know what that mean, we want this to be as intuitive as the regular custom blocks, simply tell implies that it’s telling the stage to do so, don’t want to use ‘say’ because it will be confused with the speech bubble say ‘…’ block, maybe this?
-snip-

The whole idea of changing “report” or “return” to something else because “new scratchers may not know what that means” is very silly to me. You didn't see the Scratch team changing the term “variable” or “mod” or “if”, because the whole point of Scratch is to introduce new scratchers to the fundamental concepts of programming. And a “return” statement is a big part of many programming languages.

when I start as a copy of myself:: hat control
set kind of spin to [ all around v]::motion
wait until <<mouse button pressed down ::sensing> and< mouse touching me::sensing> both happening now?::operators>
change up/down by (6)::motion
set left/right to (9)::motion
send a message that says [Clicked! v]::events
change the background image to [next v] one::looks

RobotChickens wrote:

dogeiscut wrote:

(#2456)

TerryLeeStudio wrote:

I see…I choose ‘tell it’ instead of ‘tell the reporter’ because new scratchers may not know what that mean, we want this to be as intuitive as the regular custom blocks, simply tell implies that it’s telling the stage to do so, don’t want to use ‘say’ because it will be confused with the speech bubble say ‘…’ block, maybe this?
-snip-

The whole idea of changing “report” or “return” to something else because “new scratchers may not know what that means” is very silly to me. You didn't see the Scratch team changing the term “variable” or “mod” or “if”, because the whole point of Scratch is to introduce new scratchers to the fundamental concepts of programming. And a “return” statement is a big part of many programming languages.

Yes, Scratch already has many words that new scratchers don't know. The point is to learn about them. Scratch would be trash if every programming word and term were substituted for something kids already knew.
-snip-
By the time people graduate from Scratch JR, they should be capable of learning a few new words, right?? And by the time they even come close to needing this kind of block, a simple “return” should be easy to understand. If the ST is that concerned about people misunderstanding blocks, they should bring back the side panel with all the block definitions.

TerryLeeStudio wrote:

(#2458)
Be honest, I have some question about this, in Python, turtle use Foward() instead of move () step, left() instead of turn ccw () and right() instead of turn cw (). In addition Python uses if <> instead of if <> then and for <> instead of repeat until <>. Scratch is still made with accessible language in mind. The report cap block should still be for scratch beginner in mind like maybe tell the report () will be less excessive

mumu245 wrote:

TerryLeeStudio wrote:

(#2458)
-snip-

if <> : is basically the same thing as if <> then.
for <>: is not the same as repeat until <> or even repeat <>, it is a loop that iterates automatically, which doesn't exist in Scratch. However Python doesn't have a repeat loop, so you use a for with a range.

Turtles are not the only drawing program in Python.
The arrows on Scratch's turn blocks are actually more commonly called “left” and “right” as well.

tell the reporter () makes no sense.

Easiest solution? Have a tutorial on custom functions using return.