No comment. Sorry.

	parts bin
	initializeToStandAlone

	visual properties
	canHaveFillStyles couldHaveRoundedCorners defaultColor

	as yet unclassified	top
	areasRemainingToFill: Could be improved by quick check of inner rectangle
	canDrawBorder: Return true if the receiver can be drawn with the given border style.
	containsPoint:
	doesBevels To return true means that this object can show bevelled borders, and therefore can accept, eg, #raised or #inset as valid borderColors. Must be overridden by subclasses that do not support bevelled borders.
	drawOn:
	initialize

	parts bin	top
	initializeToStandAlone Set up the receiver, created by a #basicNew and now ready to be initialized, as a fully-formed morph suitable for providing a graphic for a parts bin surrogate, and, when such a parts-bin surrogate is clicked on, for attaching to the hand as a viable stand-alone morph. Because of historical precedent, #initialize has been expected to handle this burden, though a great number of morphs actually cannot stand alone. In any case, by default we call the historical #initialize, though unhappily, so that all existing morphs will work no worse than before when using this protocol.

	visual properties	top
	canHaveFillStyles Return true if the receiver can have general fill styles; not just colors. This method is for gradually converting old morphs.
	couldHaveRoundedCorners subclases unhappy with rounded corners reimplement
	defaultColor Return the default fill style for the receiver

	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!