Scratch

when gf clicked
say 
[hi]
end

if [i] [want to v] ([sing a song about properties v] of [matter])
 (then) [I'll v] say [that I am going to sing about matter.]
else
(then) [I won't v] say [that I am going to sing about matter.]

Last edited by awesomeness321 (2012-11-08 21:17:12)

Don't really know where to go to submit some good ideas for the next version of scratch, but here are some:

when <> is true
start timer
repeat (10) or until <touching [sprite2 v]?>
  move at speed (10) steps every (1) secs
  rotate at speed (15) degrees every (1) secs
end
if touching [sprite2 v], bounce
stop timer
point away from [sprite2 v]
go back (1) costumes
hide list [times v]
stop all sprite scripts

Credit to me.

baxter_03 wrote:

spam
spam
spam
spam
spam
spam
say [now im bord of spaming]

spam
spam
spam
spam
spam
spam
say [now im bord of spaming]

fixed           

Cool!

Zro716 wrote:

Don't really know where to go to submit some good ideas for the next version of scratch How about SUGGESTIONS?, but here are some:

when <> is true
start timer
repeat (10) or until <touching [sprite2 v]?>
  move at speed (10) steps every (1) secs
  rotate at speed (15) degrees every (1) secs
end
if touching [sprite2 v], bounce
stop timer
point away from [sprite2 v]
go back (1) costumes
hide list [times v]
stop all sprite scripts

Credit to me.

1. Eh, reasonable i guess.
2. Not a bad idea
3. Not bad, but probably won't be in 2.0 because you can do:

repeat until <<(count) = [10]> or <touching [sprite2 v]?>>
whatever
whatever
change [count v] by (1)

4. Pretty easy to just do:

move (speed) steps 
wait (amount) secs

5.Same thing
6. Possible to do with the current blocks, but I'd still like it. (But I'd prefer a 'bounce' block.)
7. Not a bad idea.
8. Pretty good idea.
9. Not a bad idea, but you can do:

switch to costume ((costume #) - (amount))

10.There will be blocks to show and hide lists in scratch 2.0. 
11. There will be a block in 2.0 called 'stop other scripts in this sprite' (to avoid unexpected glitches). 


These are my opinions on your ideas.

Last edited by awesomeness321 (2012-11-09 19:43:21)

when I receive [divide by zero v]
grab [calculator v] out of [pocket v]
put [7] [/ v] [0] in [calculator v]
click [= v] button on [calculator v]
set [calculator blowup v] to [100]
blow up [calculator v]

Fibonacci Sequence Script:

when gf clicked
set [x v] to [1]
delete (all v) of [fibonacci sequence v]
add [0] to [fibonacci sequence v]
add [1] to [fibonacci sequence v]
forever
  add [(((item (((x) - (1))) of [fibonacci sequence v])) + ((item ((x)) of [fibonacci sequence v])))] to [fibonacci sequence v]
  change [x v] by (1)
end

when [not v] gf clicked [for] (5) [secs]
forever
 if [I v] [wanna v] [read v] (a) [book v] [about v] [life before the dinosaurs v] 
  (then) [I v] [will v] [read a book about v] (life before the dinosaurs) say
 else
  [I v] (will not read a book about life before the dinosaurs) say
 end
end

Last edited by sakafitrady (2012-11-10 14:32:40)

when gf clicked
if <(ZorchyGroxFox) = (new)>
say [hello everyone] for (2) secs

when gf clicked 
set [var1 v] to (0)
set [var2 v] to (0)
set [var3 v] to (0)
set [var4 v] to (1)
set [var5 v] to (0)
forever
change [var1 v] by (var2)
change [var2 v] by (var3)
change [var3 v] by (var4)
change [var4 v] by (var1)
end

when gf clicked
forever
if <(var1) > [∞]>
set [var5 v] to <[999] / [0]>

I think blocks should be accesible from the right like the program-but on the right.