paint(1)		      Grass User's Manual		      paint(1)



NNAAMMEE
       ppaaiinntt  - Description of hardcopy color output system for GRASS.

IINNTTRROODDUUCCTTIIOONN
       The ppaaiinntt system allows the user to produce color hardcopy maps of vec-
       tor, raster, and sites file data at any scale.  For a discussion of the
       GRASS  ppaaiinntt  functions,  see the manual entries for _p_._c_h_a_r_t, _p_._c_o_l_o_r_s,
       _p_._i_c_o_n_s, _p_._l_a_b_e_l_s, _p_._m_a_p, and _p_._s_e_l_e_c_t.

PPAAIINNTT DDEEVVIICCEESS
       The GRASS paint system supports multiple color printers using a	_d_e_v_i_c_e
       driver  concept.   The paint (p.)  functions listed above send graphics
       requests to device-dependent paint drivers.   These  drivers  translate
       the  application  requests  into  device-dependent  requests to produce
       hardcopy maps.

IINNSSTTAALLLLIINNGG AA PPAAIINNTT DDRRIIVVEERR
       A number of paint  drivers  have  been  distributed  with  GRASS.   The
       installation of a driver is a 2 step process.  The first involves iden-
       tifying the driver(s) which correspond to printer(s) connected to  your
       system  and  compiling those drivers.  The second involves telling each
       driver which i/o port it is to use.

	      The   source   code   for   the	drivers   lives    in	 $GIS-
	      BASE/../src/paint/Drivers  (The  variable  GISBASE refers to the
	      directory in which GRASS is installed on your system.)
	      The selection and compilation of the drivers is done when  GRASS
	      is compiled as a whole.

	      The port configuration is handled using the UNIX _l_n command.

       Each  driver  expects  to send its output to /dev/_d_r_i_v_e_r.  For example,
       the tteekk44669955 driver expects to find a tektronix 4695 (or	4696)  printer
       on /dev/tek4695.


       Suppose	the  printer  is  actually  on /dev/tty10.  Then, a link named
       /dev/tek4695 is made to /dev/tty10: ln /dev/tty10 /dev/tek4695


NNOOTTEESS
       There are 2 drivers which do not use i/o ports.	 One  is  the  pprreevviieeww
       driver,	which  sends  its  output  to the graphics screen instead of a
       hardcopy printer.  This driver is very handy and should	definitely  be
       compiled on your system.


       The  other is the nnuullll driver, which is used for debugging purposes and
       probably should not be compiled on your system.


       If you compile either of these drivers, you  shouldn't  create  a  /dev
       file for them.

SSEEEE AALLSSOO
       _p_._c_h_a_r_t

       _p_._c_o_l_o_r_s

       _p_._i_c_o_n_s

       _p_._l_a_b_e_l_s

       _p_._m_a_p

       _p_._s_e_l_e_c_t

AAUUTTHHOORR
       Michael Shapiro, U.S.Army Construction Engineering Research Laboratory

       _L_a_s_t _c_h_a_n_g_e_d_: _$_D_a_t_e_: _2_0_0_2_/_0_1_/_2_5 _0_5_:_4_5_:_3_4 _$



GRASS 5.0							      paint(1)
