NickyNouse wrote:

superben100 wrote:

scratchyone wrote:

I have heard people talking about scratch 3.0 using JSON as the file format, but it currently uses xml. Which one will it be?

I believe XML. There was once a non-functional Javascript conversion button, but it was removed before it could be coded.

Blockly (the code they're basing their code off of) uses XML, but as far as I can tell they're gonna write a converter and still use JSON eventually

technoboy10 wrote:

stillitchy wrote:

I do not want Scratch to be a part of Google.

Scratch isn't getting taken over by Google, it looks like the ST is just basing S3 off of blockly's JS code.

liam48D wrote:

You could say it's.. Scratch Blocks 3?

ayyyyyy

technoboy10 wrote:

The renderer repo is now public on GitHub. Have fun!

Error: WebGL: texImage2D: Incurred CPU-side conversion, which is very slow. (render.js:13794:10)
Error: WebGL: texImage2D: Incurred CPU pixel conversion, which is very slow. (render.js:13794:10)
Error: WebGL: texImage2D: Chosen format/type incurred an expensive reformat: 0x1908/0x1401

repeat (30)
move (10) steps
end

technoboy10 wrote:

The renderer repo is now public on GitHub. Have fun!

junebeetle wrote:

Could someone please explain exactly what these 4 different parts of Scratch do, and how they're going to come together?
I mean, I know the horizontal and vertical ones are the editor UI, and the Scratch VM and renderer are what actually run the project, but is there any way to actually make and then test a project right now?
Thanks in advance.

chooper100 wrote:

So I've read that Scratch 3 is going to be at 60 fps, but wouldn't that break all the existing Scratch projects that rely on repeat loops being 30 fps?

Eg. even something as simple as

repeat (30)
move (10) steps
end

would suddenly move loads faster

I presume backwards compatibility is a high priority issue so does anyone know how this change will be made?

superben100 wrote:

Are there going to be stretch blocks in 3.0?

chooper100 wrote:

So I've read that Scratch 3 is going to be at 60 fps, but wouldn't that break all the existing Scratch projects that rely on repeat loops being 30 fps?

Eg. even something as simple as

repeat (30)
move (10) steps
end

would suddenly move loads faster

I presume backwards compatibility is a high priority issue so does anyone know how this change will be made?

chooper100 wrote:

I presume backwards compatibility is a high priority issue so does anyone know how this change will be made?

superben100 wrote:

Are there going to be stretch blocks in 3.0?

superben100 wrote:

chooper100 wrote:

So I've read that Scratch 3 is going to be at 60 fps, but wouldn't that break all the existing Scratch projects that rely on repeat loops being 30 fps?

Eg. even something as simple as

repeat (30)
move (10) steps
end

would suddenly move loads faster

I presume backwards compatibility is a high priority issue so does anyone know how this change will be made?

Well, I think that 30 FPS is just as fast as 60 FPS. Only 60 FPS just adds an extra 30 FPS in case it runs into a situation when it needs more FPS. Though I could be wrong.

technoboy10 wrote:

superben100 wrote:

Are there going to be stretch blocks in 3.0?

I'm not sure what you mean?

liam48D wrote:

technoboy10 wrote:

The renderer repo is now public on GitHub. Have fun!

Well, I'm getting about one frame every three seconds running that, and that's actual browser frame lag, not just delayed stuff!

technoboy10 wrote:

superben100 wrote:

Are there going to be stretch blocks in 3.0?

I'm not sure what you mean?

-SuperScratch- wrote:

Could someone tell my what all the 3.0 tests are for? Scratch VM ect

superben100 wrote:

-SuperScratch- wrote:

Could someone tell my what all the 3.0 tests are for? Scratch VM ect

The Scratch Blocks horizontal and vertical tests are for the switchable editor that is going to release in Scratch 3.0, Scratch VM is for sending the commands to the stage when a block function is triggered, and the Scratch Render test is for sprite testing on the stage.