		  PaintJet Problem

Paintjet support has many choices, could involve much time/effort to do a
complete job.

Full support  =		"dump graphics" key color dump graphics for 236C, 
			Moonunit, topcat color, catseye color
	      + 	color dump via DGL for same
	      + 	mono (black) dump for 216, 226, 236A, 327A, 217A, mono 
			topcat, mono catseye
	      (full ready-to-run code)
	      + 	"hackable" source ?
	  including 2 different algorithms, 2 rotations, etc

Library support   = 	no "dump" key
		  +	Auxiliary library for DGL dump, only color CRTs
		  + 	some ready-to-run code, but missing capability
		  + 	"hackable" source ?

Marginal support  =	"hackable" source, not smart about configuration
			(eg--what CRT am I? , etc)
			no ready-to-run code

Costs (preliminary estimate):
	Full support:	6 - 10 engr-weeks
	Library:	4 - 8 engr-weeks
	Marginal:	2 - 4 engr-weeks

The problem: by analogy to 3.2 product, where HFS development held up shipment,
		and we couldn't support 330/350 for 7-8 months. The analogy
		here is that PaintJet support could hold up CATSEYE shipments
		on PAWS for significant time, if we put PaintJet support in
		the critical path for 3.21.
		PAWS has 2 engrs, and wants to MR 3.21 in mid-March to 
		Mid-April '88. Any PaintJet work is in the critical path.

Some alternatives:
	Delay 3.21 MR
	Back off from full support to reduce development time
	Move PaintJet to later rev of PAWS
	Get help with Paintjet (eg SDD, Mktg)
	Find 3rd party developer for PaintJet support


Suggestions, ideas, bitches???
