Last updated at 3:36 am UTC on 29 August 2018
subclass of Model
The class Player may have many subclasses, each one associated with a Morph object.
The basic hookup is that every Morph can have, optionally, a Player as its "player", and every Player has an associated Morph that it "wears" as its "costume". Player itself is a class with lots of capability but very little instance state; user-defined Players are all implemented as compact, single-instance subclasses of Player
Scripting with Players -- The "User-Scripting" Style
The fundamental user-scriptable entity. Always represented by a user-specific subclass of Player;
instance vars and methods relate to user-defined structures.
costume is a Morph, the primary morph I am currently wearing for graphical display.
Scripts are defined in subclasses of Player. These are UniClasses.
Messages in scripts are sent to Players. A Player may delegate to its costume, or to an object the costume suggests. Or, a Player may designate some other object to receive the script messages it does not understand. (see doesNotUnderstand:)
Used in Etoys