A cheezy morph that simply steps a Nebraska server instance over and over.

	drawing
	updateCurrentStatusString

	initialization
	initialize rebuild setColorsAndBorder toggleFull

	object fileIn

	stepping and presenter
	stepTime update:

	structure
	delete step

	accessing	top
	currentBacklogString
	currentStatusString
	server

	drawing	top
	updateCurrentStatusString

	initialization	top
	initialize
	rebuild
	setColorsAndBorder
	toggleFull

object fileIn

top

	stepping and presenter	top
	stepTime Answer the desired time between steps in milliseconds. This default implementation requests that the 'step' method be called once every second.
	update: Receive a change notice from an object of whom the receiver is a dependent. The default behavior is to do nothing; a subclass might want to change itself in some way.

	structure	top
	delete Remove the receiver as a submorph of its owner and make its new owner be nil.
	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.

	as yet unclassified	top
	killOldServers
	serveWorld:
	serveWorld:onPort: