From Test-Scratch-Wiki

SandCastleIcon.png This page has links to outside of the Scratch website or Wikipedia. Remember to stay safe when using the internet as we can't guarantee the safety of other sites.


Archive.png This article or section documents a feature not included in the current version of Scratch (3.0). It is only useful from a historical perspective.

Wikipedia-logo.svg  For more information, see Adobe Flash Player on Wikipedia. Scratch 2.0 was a completely flash-based program, in which both the project editor and project page viewer used the same player, the Flash player. The Flash player was first introduced during the previous Scratch website as an alternative to the Java Player.

What showed under the download option when the project was running in the Java Player.
Allowed a Scratcher to use the Java Player instead of the Flash one.

History

  • On Tuesday, February 22, 2011, an announcement was made about the new player.[1] It asked for feedback and bug reports. Within an hour, there were more than 20 replies, many of them giving much praise to the new player.
  • On Thursday, October 18, 2012, an announcement was made about the flash player becoming the default, even for non-registered users.[2]
  • On Saturday, May 9, 2013, the Flash Player exited its beta stage, and became the official, only player available on the Scratch website.
  • On Wednesday, January 2, 2019, the Flash Player was terminated due to the release of Scratch 3.0 which runs with HTML5 and JavaScript. Support for the Flash Player ended on December 31, 2020.[3]

Changes

There were several noticeable changes from the Java player. Some of these included:

  • Scratch 2.0 styling
  • An enlarged screen mode that adjusted to one's web browser's size
  • Text in variables and lists were vector text
  • Variables and lists were displayed differently
  • The "ask" box showed a cursor
  • A new Flash loading bar
  • Shift-clicking the Green Flag would switch the project to Turbo Mode; shift-clicking the flag again will put the project back into regular mode. Turbo mode can be helpful for performing complicated computations rapidly
The old full screen bug.
  • Supported some blocks that would appear in Scratch 2.0[4]
  • Scratch projects could be opened from local files by shift-clicking the version number

Full Screen

This tur is about the version in Scratch 2.0. For the feature in Scratch 1.4, see Eng:Presentation Mode. For Presentation Mode, see Flash Player (disambiguation).
A project playing in full screen mode.

There was a full screen option in the Flash Player. If the browser is put into full screen mode, then Scratch is put into full screen. Full screen is very similar to presentation mode, except presentation mode doubled the stage's vertical and horizontal resolution, and full screen mode scales and fits to one's browser's displaying size.

When the Go Full Screen.png button is clicked, it goes into full screen, which almost fits the computer's resolution, through displaying tools; and when the Exit Full Screen.png button is clicked, the resolution adjusts back to normal size.

Bitmap graphics may look pixelated in full screen mode.

Crashing

A screen which pulled up when the Adobe Flash Player crashed on Firefox. (Obsolete as of Firefox 85, as Flash is no longer supported.)[5]
A screen which pulled up when Adobe Flash Player crashed on Chrome. (Obsolete as of Chrome 88, as Flash is no longer supported.)[6]

If the Flash Player runs something which causes too much lag, the Adobe Flash Player will crash. The user can reload the Flash Player by reloading the page. On certain browsers, there's an option to send a crash report. However, this isn't necessary.

In Internet Explorer, when the Flash Player crashes, it leads to a white screen with a circle containing an exclamation mark. On Firefox, it shows a sad plugin, as seen on the image on the right. On Google Chrome, it crashes to a black screen with a dead puzzle piece.

See Also

External Links

References

Cookies help us deliver our services. By using our services, you agree to our use of cookies.