Scratch

Text to speech isn't as easy as looks, you know. There's loads of different algorithms etc., and the Scratch Team have enough things to concentrate on as it is; building a text to speech feature would probably take about half a year, at the least. And could you give some examples for when we'd need to print a list?

Ideas part 2: (more practical)
I think that we should be able to create different kinds of variables.
i.e.

if <variable>//boolean (see note 1)
whatever
end

wait until <variabletimer=[whatever]>//timer (see note 2)
repeat until <variabletimer=[whatever]>
do this
end

1. Boolean variables would be helpful in that you would no longer have to use the <[]=[]> operator for broadcast received variables, circumventing the need for a broadcast received block (though having to make one anyway  ).
2. Timer variables would be useful because you could set the variable to have different increments than the currently available timer.

Last edited by technoboy10 (2012-02-03 13:06:14)

RedRocker227 wrote:

Huh?

If <(Variable)>

doesn't make any sense. How would you define whether the boolean is true or false?

set [booleanvar v] to [true v]

There you go.

If you wanted to make your own broadcast recieved block, I think it would be easier to set a Boolean. It also would set you up better for typed languages.

The user would be able to change the value to true or false, instead of a pre-defined set of circumstances when it would be true.

RR227, learn something more advanced and then you'll see the need. 

veggieman001 wrote:

RedRocker227 wrote:

You don't "set" a boolean though; it's either true or false, and the user can't edit it.

You set it to true or false, in regular programming.
If <boolean> would be if the boolean is true and if <not <boolean>> would be if it's not true.

I know, but he/she's suggesting the ability to turn a reporter into a boolean, which just doesn't make any sense.

technoboy10 wrote:

RedRocker227 wrote:

veggieman001 wrote:

You set it to true or false, in regular programming.
If <boolean> would be if the boolean is true and if <not <boolean>> would be if it's not true.

I know, but he/she's suggesting the ability to turn a reporter into a boolean, which just doesn't make any sense.

No... I'm saying that we should be able to create different classes of variables.

I'm talking about the "if <variable>" idea.

RedRocker227 wrote:

technoboy10 wrote:

RedRocker227 wrote:

I know, but he/she's suggesting the ability to turn a reporter into a boolean, which just doesn't make any sense.

No... I'm saying that we should be able to create different classes of variables.

I'm talking about the "if <variable>" idea.

That reporter is supposed to be a Boolean.

make server with the name of (answer)

[permanently v] ban user (answer)

join server (answer)

technoboy10 wrote:

gunsguns wrote:

[permanently v] ban user (answer)

That doesn't seem like a good idea. What if you got banned by a troll for no reason?

there is a drop down menu so you can permanently or temporlily ban a user + there should be a pop up menu saying 'why do you want to ban user'.

T

scimonster wrote:

gunsguns wrote:

technoboy10 wrote:

That doesn't seem like a good idea. What if you got banned by a troll for no reason?

there is a drop down menu so you can permanently or temporlily ban a user + there should be a pop up menu saying 'why do you want to ban user'.

No. Only the Scratch Team can ban people. See Banning on the Scratch Wiki.

I think it's to be banned from the server.