Scratch

Jem12 wrote:

WOW    I haven't seen 2.0 prototype but reading "video sensing" is really bringing up my Curiosity (but curiosity killed the scratch cat    ) Also Just A quick Question- will we still be able to view old projects on the website or just new ones? + can we still create projects like the old(ish) ones. Thanks.

do you know the rest of the phase

curiosity killed the cat but satisfaction brought her back.

off-topic-this comes from two mythical gods (curiosity and satisfaction) curiosity is evil god of cats and satisfaction is the good god of cants

scimonster wrote:

Jem12 wrote:

WOW    I haven't seen 2.0 prototype but reading "video sensing" is really bringing up my Curiosity (but curiosity killed the scratch cat    ) Also Just A quick Question- will we still be able to view old projects on the website or just new ones? + can we still create projects like the old(ish) ones. Thanks.

You will be able to view projects made in older versions of Scratch, and even make them.

Oh good you can. 
I am interested with the video sensing the most probably. :3 I've seen block creating stuff before, but never video sensing.

this was the only part I liked.

I am kinda dissapointed there still arent <When I recieve { }> and {Show List} {Hide List}

rabbit1131 wrote:

My first question,
What is this "Scene" block?

I think "Backround" is now "Scene"

scimonster wrote:

WillieD wrote:

rabbit1131 wrote:

My first question,
What is this "Scene" block?

I think "Backround" is now "Scene"

Yep. There's also a new When Scene [] Starts in Events. 

But still no < When I recieve {} > D:

randomgamemaker wrote:

It may just be my computer, but when I tried video [motion] on [stage] a dialog box came up asking if scratch could have access to a camera. But when I clicked yes, nothing happened, and when I clicked no nothing happened. So now the page is frozen.

I'm not sure that was you, a just now I couldnt drag any blocks at all or do anything

i think that you should have some blocks with clones like a new (clone?) sensing block just true or false and it determines if it is being run in a clone

my next idea can be used without a new block but, it would make things essayer.It is another sensing block this time its the (number of clones) this sprite has or the number or twins the clone has (counting himself)

cpumaster930 wrote:

Regarding cloud data: Will you eventually be able to make persistent variables and lists so that, for example, your progress in a game could be saved and loaded automatically when you play the game again?

Additionally, is it possible to have a hardcoded variable (like timer, volume, etc.) that always reports the Scratch username of the currently logged in user?  This would be extremely useful for high score lists 

Probably not, because cloud variables are the same for everyone.

i do like it but i think you should make the byob thing more like it is here http://snap.berkeley.edu/snapsource/snap.html

cpumaster930 wrote:

Additionally, is it possible to have a hardcoded variable (like timer, volume, etc.) that always reports the Scratch username of the currently logged in user?  This would be extremely useful for high score lists 

Excellent idea! We have considered adding a "'user name" block. It would definitely be useful, but it also raises privacy concerns.

For a high score list, you can use the "ask" block and let the user type in whatever name they want.

One might also use a "user name" block to keep people from voting more than once in a survey. We're thinking about ways to solve that problem without violating people's privacy.

Last edited by johnm (2012-05-17 11:09:55)

cpumaster930 wrote:

Regarding cloud data: Will you eventually be able to make persistent variables and lists so that, for example, your progress in a game could be saved and loaded automatically when you play the game again?

Additionally, is it possible to have a hardcoded variable (like timer, volume, etc.) that always reports the Scratch username of the currently logged in user?  This would be extremely useful for high score lists 

It's great that you are thinking about a username reporting block  . We thought about it during our design process, and decided not to go with it, mainly for a couple of reasons.

One reason is privacy - with a username block, a Scratcher may be able to record every action that other Scratchers take on his project (for example, every click), and sometimes this can be done without the other Scratchers knowing that they are being recorded.

Another reason is that we do not want code that is specifically tailored for someone in the community - one could easily have a project that says something inappropriate for a specific user through a if block:

when gf clicked
if <(username) = [sdg1]>
  be mean
else
  act normal
end

Considering these possible drawbacks, we decided not to implement the username block, though we agree with you that username blocks will make things much easier for certain type of projects.