No comment. Sorry.

	initialization
	assurePauseTickControlsShow initializeFor: intoWorld: maybeRemovePauseTickControls

	mouse gestures
	mouseDownTick:onItem: mouseUpTick:onItem: offerTickingMenu: pausedUp:with: tickingUp:with:

	script status
	scriptIsPaused scriptIsTicking

	access	top
	scriptInstantiation Answer the scriptInstantiation object with which the receiver is associated
	updateStatus

	initialization	top
	assurePauseTickControlsShow Add two little buttons that allow the user quickly to toggle between paused and ticking state
	initializeFor: Answer a control that will serve to reflect and allow the user to change the status of the receiver
	intoWorld: The receiver has just appeared in a new world. Note: * aWorld can be nil (due to optimizations in other places) * owner is already set * owner's submorphs may not include receiver yet. Important: Keep this method fast - it is run whenever morphs are added.
	maybeRemovePauseTickControls If we're in the business of removing pauseTick controls when we're neither paused nor ticking, then do it now. The present take is not to remove these controls, which explains why the body of this method is currently commented out.

	mouse gestures	top
	mouseDownTick:onItem:
	mouseUpTick:onItem:
	offerTickingMenu:
	pausedUp:with: The paused button was hit -- respond to it
	tickingUp:with: The user hit the ticking control; make the status become one of ticking

	script status	top
	scriptIsPaused Answer whether the script is paused
	scriptIsTicking Answer whether the script is ticking