Letting people choose if they want to use the scratch 2.0, 1.0, or 3.0 interface

Fly_Techno

Can't we just have options to choose if we want to use different versions of scratch without having to download an offline editor

MrFluffyPenguins

YEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAH

Okay sorry for spam but seriously
SUPPORT

_Portavia_

Support, no further questions asked.

LionHeart70

I agree - I don't see why not. Plus, not everyone can download the offline editor due to the device they may have.. I can't, for instance..
It'd also make project making a lot easier and I think could potentially be a compromise for people who like 3.0 and people who don't. The only problem is.. I don't know if the ST is considering it..

DownsGameClub

The only reason why they aren't considering it is that they're all based off of different platforms. It's going to be some work if we were to implement this feature and convert projects all to a usable format that is readily available to all Scratchers while still keeping the former interfaces.

Shmaggie101

2.0

matthewscratch06

I see your point, but they have added new blocks, and new things, and if you go back a version or two, newer projects will not be compatible.
Think of minecraft, when a new update comes out, new blocks are added, but if you are in an older version, those blocks will be broken.
Offline editors dont have that problem as their is no project sharing.
I reccomend downloading whatever version you want as an offline version, making your projects on there, then upoading them to the current scratch version.

KrisBigK

matthewscratch06 wrote:

I see your point, but they have added new blocks, and new things, and if you go back a version or two, newer projects will not be compatible.

I think that if a newer project is opened in a older editor, just display the blocks that is added in a new version as an invalid block and simply skip it when executing the script. In this way, at least the problem of can't opening the project can be solved. Whether or not the project will always work is another thing though.

Za-Chary

KrisBigK wrote:
I think that if a newer project is opened in a older editor, just display the blocks that is added in a new version as an invalid block and simply skip it when executing the script. In this way, at least the problem of can't opening the project can be solved. Whether or not the project will always work is another thing though.

I think it's a little more complicated than that. After all, if I open a 3.0 project in 1.4, it wouldn't even be able to display the new blocks, I think. Then if you do some editing, how would it remember what blocks go where?

The only way to work around this would be to make a “skin” that changes between each interface, but that is something the Scratch Team is not considering at the moment:

thisandagain wrote:
We are not considering a “skin” that switches between the look of 2.0 and 3.0, but we may consider being able to toggle which side of the screen the stage is on.

DrifAssault

repeat ()
repeat ()
repeat ()
repeat ()
repeat ()
repeat ()
repeat ()
repeat ()
repeat ()
repeat ()
repeat ()

end

end

end

end

end

end

end

end

end

end

end

Fupicat

Flash is gonna be deprecated in 2020, so the 2.0 editor will be open for exploits when that year comes.
I don't think the 1.4 editor could even run on a browser.

If your device can't run 2.0 Offline, you could try downloading Whiskers.

unmissable

SUPPORT
2.0 is easier to use and I don't like vector

Last edited by unmissable (May 9, 2023 16:32:16)

Discuss Scratch