Scratch

What? The feature of broadcasting Scratch-startclicked doesn't work.

TheGuyWithTheFace wrote:

I twon't let me edit costumes. but over all, it's really cool!

They probably don't have the 2.0 paint editor yet.

Last edited by zorket (2010-12-05 18:30:45)

It would be great if the decimal problem was fixed in the new viewer, preferably, by not limiting the results of operations with decimal to the tenth's place.  If not, it would be great if the JOIN hack worked error free on the viewer like it does offline.

My slow Internet is not going to like this.

Good - but I would like the stage to be bigger and on the right like it has always been, and the script panel and the script menu on the left. Nice idea of using coloured icons to represent the collections of code blocks.

<when green flag clicked><broadcast[loveit]and wait c>

<play sound[super cool]

Whats the difference?
ps. check out my projects.

2.0~! 2.0!

2.0~~~

I Wants Eet Naow

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

i noticed a little bug an object cant collide with another one when the object is hidden witch makes my bot not work (http://scratch.mit.edu/projects/killer64/1493124) it uses an invisible sprite that senses if its touching the edge but it wont work with experimental viewer

OK - here's my overall review of this.

To start off, you guys have done a great job building this from scratch, really. Must have taken a long time and a lot of work and I applaud you for that. 

The first thing to notice is that the rendering engine is blindingly fast in comparison to that of Online and Offline scratch. Sizing, movement of large sprites and rotations make little to no speed impact as they should. This is a very good point and means that scrolling games will work really well.

I noticed that Collision detection makes a massive impact on performance, much higher an impact than that of online or offline scratch which completely kills many games and renders them unplayable. Doesn't flash have a very fast "hittest" function for this?

Large scripts, be it in the sprite selected or another one cause a large performance impact *even when not activated*. If you run my latest project in the experimental viewer you'll see that the FPS variable jitters but stays at around the same numbers no matter how many shellcreepers are activated.

Editing large scripts is really painful because scrolling down and up on them is really slow. Even hovering your mouse over the scripts kills performance. Some games with large scripts don't even load.

I noticed I can't delete sprites, but I guess that's just temporary.

Will the engine be further optimised as we get closer to launch? Right now a lot of existing games will not run on the viewer because of performance issues or games that are too large.

This is a cool idea, but it's pretty glitchy, plus it takes a while to load, so I still prefer downloading it.

How do you make variables?

I found a bug! Space in a string isn't sensed properly. In Scratch 1.4 saying
if<letter (2) of [a dog] works fine
However, in the online viewer it does not...

This is a project a bit like Doodle Jump, where you jump up over a series of random platforms. But in the experimental viewer the platforms are all put in a single line. 

Is the experimental viewer still being worked on?