Better Custom Blocks

lapisi

gosoccerboy5 wrote:
By the alternating caps lock and lowercase, it implies that I'm being sArCaStIc
I'm pointing out that the workarounds are dysfunctional and complex

how is using permanent variables complex? but I do agree that with temporary variables you don't have to fill the project with variables that are only used once

don't forget

why are humans so meaty?

gosoccerboy5

lapisi wrote:
gosoccerboy5 wrote:
By the alternating caps lock and lowercase, it implies that I'm being sArCaStIc
I'm pointing out that the workarounds are dysfunctional and complex
how is using permanent variables complex? but I do agree that with temporary variables you don't have to fill the project with variables that are only used once

Well, for one, it's wasteful, and second (probably more importantly) if you're running multiple functions at a time, any permanent variables used to report anything might get messed up by two functions using the variable at a time.

space_elephant

AHypnoman wrote:
gosoccerboy5 wrote:
I already said that. But the question is, why does
space_elephant wrote:
Return means that the functions stops immediantely.
? Is there any specific reason?
I don't think so… I think at this point it's just like that for historic reasons.

It's there because there is no reason you would use it without that, and because it helps prevent code that is usually unnecessary. If the point of a reporter is to return, then doing stuff after that will just waste time. It is possible to work around with local variables, something that all production programming languages have, and scratch should have.

red link

[url=redlink.com][color=red][u]red link[/u][/color][/url]

gosoccerboy5

Actually, that basic concept is in this suggestion too. In the form of “temporary variables”

SpaceIsEndless

Support! I hope this gets added.

gosoccerboy5

SpaceIsEndless wrote:
Support! I hope this gets added.

I've said this before, but legend has it that in the Suggestions forum, one must provide reasoning as to why they support

gosoccerboy5

bump - an acrostic poem

bring
up
my
post

sathvikrias

gosoccerboy5 wrote:
No SuPPoRt eaSy WORkaRouND

“Just use a custom stack block and a variable called ‘return’”

“For temporary variables why not just use permanent variables”

also bump

(I know you're being sarcastic)

but for people who think that, you will clutter up the variables category.

Moving from Scratch? Don't learn C or Java, try Snap!

space_elephant

sathvikrias wrote:
gosoccerboy5 wrote:
No SuPPoRt eaSy WORkaRouND

“Just use a custom stack block and a variable called ‘return’”

“For temporary variables why not just use permanent variables”

also bump
(I know you're being sarcastic)

but for people who think that, you will clutter up the variables category.

Also, that doesn't work for concurrency or recursion. Careful uses of lists can fix recursion, the common case, but it still breaks with other concurrent threads.

red link

[url=redlink.com][color=red][u]red link[/u][/color][/url]

SpaceIsEndless

gosoccerboy5 wrote:
SpaceIsEndless wrote:
Support! I hope this gets added.
I've said this before, but legend has it that in the Suggestions forum, one must provide reasoning as to why they support

Ah, right

I support because there are so many applications. There are workarounds for this, but they're very complex and get very messy if you have multiple functions and/or are using the same one multiple times. Literally all other languages have this for that reason. Anyways, that's my reason

space_elephant

SpaceIsEndless wrote:
gosoccerboy5 wrote:
SpaceIsEndless wrote:
Support! I hope this gets added.
I've said this before, but legend has it that in the Suggestions forum, one must provide reasoning as to why they support
Ah, right I support because there are so many applications. There are workarounds for this, but they're very complex and get very messy if you have multiple functions and/or are using the same one multiple times. Literally all other languages have this for that reason. Anyways, that's my reason

Basic doesn't. Neither does assembler. Scratch is a lot like assembler.

red link

[url=redlink.com][color=red][u]red link[/u][/color][/url]

AHypnoman

space_elephant wrote:
SpaceIsEndless wrote:
gosoccerboy5 wrote:
SpaceIsEndless wrote:
Support! I hope this gets added.
I've said this before, but legend has it that in the Suggestions forum, one must provide reasoning as to why they support
Ah, right I support because there are so many applications. There are workarounds for this, but they're very complex and get very messy if you have multiple functions and/or are using the same one multiple times. Literally all other languages have this for that reason. Anyways, that's my reason
Basic doesn't. Neither does assembler. Scratch is a lot like assembler.

What relation to Scratch does Assembly Code have?

I don't think that it's the best thing to compare it to. Nor is Basic.

Last edited by AHypnoman (Dec. 17, 2020 17:34:19)

~ AHypnoman (Use Shift+Down Arrow to see the rest of my signature)

Go use Linear Scratch, a port of BrainF that makes programming easier!

I am an evil kumquat, and your siggy looks tasty…
Hello there, I'm AHypnoman, If you write my name remember to capitalize the “H”. “When you don't create things, you become defined by your tastes rather than ability. your tastes only narrow & exclude people. so create.” I write though as tho.
According to the Chrome Console, my viewbox attribute is “Garbage”. Very nice, Chrome.
#TrendyHashtag
Gib internneeet

Play Retorquebit!

Go see my most recent animation!

Maximouse

AHypnoman wrote:
What relation to Scratch does Assembly Code have?

I don't think that it's the best thing to compare it to. nor is Basic.

High-level interpreted languages, such as Python and JavaScript, are much more similar to Scratch.

This is Maximouse's signature. Learn more about signatures.

IndianRuby718

I know I've posted on here before, but I come back with two small things to add:
Custom booleans should have options for boolean and reporter inputs. (reporters just with reporters)

<custom <condition :: custom-arg> or (reporter :: custom-arg) :: custom>

And the report block for booleans should be a drop-down, since it's either true or false:

report [true v] :: custom-arg cap

I don't know if anyone has said these already, but if not. *gestures*
And this could also count as a bump I guess :P

So… I didn't update my signature for over a year XP But… I left the forums, and I'm not coming back anytime soon
(and I'm not updating my signature)

Both stickied Suggestions Directories currently have 138 replies.
Only fdreerf can break the equilibrium.

________________

Za-chary wrote:
I get more frustrated with people telling me about “mass reporting” than I do about “mass reporting” itself.

source
good luck digging up the original reply in the comments
ctrl+f exists

https://scratch.mit.edu/discuss/post/6961734/

Bug with the color effect I would really like to see fixed

EEEEEEE   DDDDDD    IIIIIIII  TTTTTTTT           NNN    NN     OOOOO
EE        DD    DD     II        TT     ::       NNNN   NN   OO     OO
EEEEEEE   DD    DD     II        TT              NN NN  NN   OO     OO 
EE        DD    DD     II        TT     ::       NN  NN NN   OO     OO
EE        DD    DD     II        TT              NN   NNNN   OO     OO
EEEEEEE   DDDDDD    IIIIIIII     TT              NN    NNN     OOOOO

Hand-done.

< :: extension>
< :: custom-arg>
< :: motion>

Don't click this link…

gosoccerboy5

IndianRuby718 wrote:
I know I've posted on here before, but I come back with two small things to add:
Custom booleans should have options for boolean and reporter inputs. (reporters just with reporters)
<custom <condition :: custom-arg> or (reporter :: custom-arg) :: custom> 
And the report block for booleans should be a drop-down, since it's either true or false:
report [true v] :: custom-arg cap 
I don't know if anyone has said these already, but if not. *gestures*
And this could also count as a bump I guess :P

No, it should be so that you can type in “true”
also of course custom booleans and reporters should have inputs, that's the whole point

IndianRuby718

I know it was mentioned to have inputs, but I don't know if it was specifically mentioned that booleans can have boolean inputs. (I thought I saw a post showing both booleans and reporters having reporter inputs, but not boolean inputs. I could be wrong though)

So… I didn't update my signature for over a year XP But… I left the forums, and I'm not coming back anytime soon
(and I'm not updating my signature)

Both stickied Suggestions Directories currently have 138 replies.
Only fdreerf can break the equilibrium.

________________

Za-chary wrote:
I get more frustrated with people telling me about “mass reporting” than I do about “mass reporting” itself.

source
good luck digging up the original reply in the comments
ctrl+f exists

https://scratch.mit.edu/discuss/post/6961734/

Bug with the color effect I would really like to see fixed

EEEEEEE   DDDDDD    IIIIIIII  TTTTTTTT           NNN    NN     OOOOO
EE        DD    DD     II        TT     ::       NNNN   NN   OO     OO
EEEEEEE   DD    DD     II        TT              NN NN  NN   OO     OO 
EE        DD    DD     II        TT     ::       NN  NN NN   OO     OO
EE        DD    DD     II        TT              NN   NNNN   OO     OO
EEEEEEE   DDDDDD    IIIIIIII     TT              NN    NNN     OOOOO

Hand-done.

< :: extension>
< :: custom-arg>
< :: motion>

Don't click this link…

Maximouse

IndianRuby718 wrote:
I know it was mentioned to have inputs, but I don't know if it was specifically mentioned that booleans can have boolean inputs. (I thought I saw a post showing both booleans and reporters having reporter inputs, but not boolean inputs. I could be wrong though)

All custom blocks should have all types of inputs.

This is Maximouse's signature. Learn more about signatures.

gosoccerboy5

This is a half serious, half joking question: why don't they just rehire Jens into the ST if they ever want to add this?

Maximouse

gosoccerboy5 wrote:
This is a half serious, half joking question: why don't they just rehire Jens into the ST if they ever want to add this?

They could implement this themselves, the hard part is design.

This is Maximouse's signature. Learn more about signatures.

sathvikrias

IndianRuby718 wrote:
-snip-
And the report block for booleans should be a drop-down, since it's either true or false:
report [true v] :: custom-arg cap 
I don't know if anyone has said these already, but if not. *gestures*
And this could also count as a bump I guess :P

better if it is

 report [] :: custom-arg cap

or

 report <> :: custom-arg cap

so if you wanted to make a custom block, like

 <[] = []>

even though we already have it, you could do

define <(string :: custom-arg) = (other string :: custom-arg) :: custom> :: #8258ae boolean
report <<not <(string :: custom-arg) > (other string :: custom-arg)>> and <not <(string :: custom-arg) < (other string :: custom-arg)>>> :: custom-arg cap

// instead of

define <(string :: custom-arg) = (other string :: custom-arg) :: custom> :: #8258ae boolean
if <<not <(string :: custom-arg) > (other string :: custom-arg)>> and <not <(string :: custom-arg) < (other string :: custom-arg)>>> then
report [true v] :: custom-arg cap
else
report [false v] :: custom-arg cap
end

Last edited by sathvikrias (Dec. 19, 2020 20:58:19)

Moving from Scratch? Don't learn C or Java, try Snap!

Discuss Scratch