No comment. Sorry.

	camera actions
	addDolly: addFovAngle: panBy: rotateFrom:to: rotateX: rotateY: rotateZ: transformWithMatrix: updateHeadlight

	drawing
	renderOn:

	event handling
	handlesMouseDown: mouseDown: mouseMove:

	initialization
	createDefaultScene initialize

	private
	pointOnSphereCentered:radius:atPoint: updateSceneWithDefaults: updateUpVectorForCamera:

	properties
	beRotating beStill headLightIsOn isRotating switchHeadLightOff switchHeadLightOn switchHeadLightStatus switchRotationStatus

	stepping
	step

	accessing	top
	rotationAngle
	rotationAngle:
	scene:
	stepTime Answer the desired time between steps in milliseconds. This default implementation requests that the 'step' method be called once every second.
	stepTime:

	camera actions	top
	addDolly:
	addFovAngle:
	panBy:
	rotateFrom:to:
	rotateX:
	rotateY:
	rotateZ:
	transformWithMatrix:
	updateHeadlight

	drawing	top
	renderOn:

	event handling	top
	handlesMouseDown: Do I want to receive mouseDown events (mouseDown:, mouseMove:, mouseUp:)?
	mouseDown: Handle a mouse down event. The default response is to let my eventHandler, if any, handle it.
	mouseMove: Handle a mouse move event. The default response is to let my eventHandler, if any, handle it.

	initialization	top
	createDefaultScene
	initialize

	private	top
	pointOnSphereCentered:radius:atPoint:
	updateSceneWithDefaults:
	updateUpVectorForCamera:

	properties	top
	beRotating
	beStill
	headLightIsOn
	isRotating
	switchHeadLightOff
	switchHeadLightOn
	switchHeadLightStatus
	switchRotationStatus

	stepping	top
	step Do some periodic activity. Use startStepping/stopStepping to start and stop getting sent this message. The time between steps is specified by this morph's answer to the stepTime message. The generic version dispatches control to the player, if any. The nasty circumlocation about owner's transformation is necessitated by the flexing problem that the player remains in the properties dictionary both of the flex and the real morph. In the current architecture, only the top renderer's pointer to the player should actually be honored for the purpose of firing.

	parts bin	top
	descriptionForPartsBin If the receiver is a member of a class that would like to be represented in a parts bin, answer the name by which it should be known, and a documentation string to be provided, for example, as balloon help. When the 'nativitySelector' is sent to the 'globalReceiver', it is expected that some kind of Morph will result. The parameters used in the implementation below are for documentation purposes only!