Graphics development with vplot - Revision history

Sfomel at 23:10, 8 April 2014

2014-04-08T23:10:24Z

Show changes

Sfomel: /* Variables */

2014-04-08T23:08:08Z

Variables

Show changes

Sfomel: /* Program structure */

2014-04-08T23:04:22Z

Program structure

← Older revision		Revision as of 23:04, 8 April 2014
Line 66:		Line 66:
	<ol><li>		<ol><li>
	Declaration of the variables necessary to do self-documentation:		Declaration of the variables necessary to do self-documentation:
	<c>		<syntaxhighlight lang="c">
	char name[] = "Filter name";		char name[] = "Filter name";
	char *documentation[] = {...documentation...};		char *documentation[] = {...documentation...};
	int doclength = {sizeof documentation / sizeof documentation[0] };		int doclength = {sizeof documentation / sizeof documentation[0] };
	</c>		</syntaxhighlight>
	You may wish to include "gendoc.h" as part of your documentation string.		You may wish to include "gendoc.h" as part of your documentation string.
	</li><li>		</li><li>
Line 92:		Line 92:
	for all other functions. Figure 1 contains the device structure for the		for all other functions. Figure 1 contains the device structure for the
	Envision 220.		Envision 220.
	<c>		<syntaxhighlight lang="c">
	struct device dev =		struct device dev =
	{		{
Line 123:		Line 123:

	/* Figure 1: device structure for envipen */		/* Figure 1: device structure for envipen */
	</c>		</syntaxhighlight>

	==Variables==		==Variables==

Sfomel: /* Variables */

2010-07-27T15:06:37Z

Variables

← Older revision		Revision as of 15:06, 27 July 2010
Line 237:		Line 237:
	</c>		</c>
	If smart_clip=NO, then dovplot will do all clipping for you, with the exception of polygons supported at the dev.area level. If you can do your own clipping, then set smart_clip=YES. You must then handle dev.attributes(SET_WINDOW)!		If smart_clip=NO, then dovplot will do all clipping for you, with the exception of polygons supported at the dev.area level. If you can do your own clipping, then set smart_clip=YES. You must then handle dev.attributes(SET_WINDOW)!

			<c>
			int smart_background=NO;
			</c>
			If smart_background=YES, then dovplot will handle the background command for you by drawing a borderless polygon of color 0 to exactly fill the plottable area. If your device already handles setting the background color to match whatever color 0 has been redefined to, then you can set this variable to "YES". Dovplot will then call dev.erase(ERASE_BACKGROUND) when it encounters this command, which the device can use to implement the command if needed. Devices that naturally honor changes to color 0 can ignore this command.

	<c>		<c>

Nick at 23:16, 23 June 2009

2009-06-23T23:16:14Z

← Older revision		Revision as of 23:16, 23 June 2009
Line 1:		Line 1:
	This document has been originally distributed together with vplot as <tt>pens/docs/vplothacker.doc . It has been placed on this wiki for enhanced readability, for version control and for easy editing which will increase its chances of being kept up to date. All relative file paths referred to in this document refer to the location mentioned above. More information may be found [http://sepwww.stanford.edu/theses/sep60/60_25.pdf in SEP report nr. 60].		This document has been originally distributed together with vplot as <tt>pens/docs/vplothacker.doc</tt> . It has been placed on this wiki for enhanced readability, for version control and for easy editing which will increase its chances of being kept up to date. All relative file paths referred to in this document refer to the location mentioned above. More information may be found [http://sepwww.stanford.edu/theses/sep60/60_25.pdf in SEP report nr. 60].

	'''Hacker's guide to the innards of the Pen programs''',<br>		'''Hacker's guide to the innards of the Pen programs''',<br>

Nick at 23:15, 23 June 2009

2009-06-23T23:15:48Z

← Older revision		Revision as of 23:15, 23 June 2009
Line 1:		Line 1:
	This ~~page contains documentation included in the~~ vplot ~~distribution, (~~<tt>~~RSFSRC/~~pens/docs/vplothacker.doc~~</tt>)~~. ~~This documentation~~ has been placed on this wiki for enhanced readability, for version control and for easy editing which will increase its chances of being kept up to date. All relative file paths referred to in this document refer to the location mentioned above. More information may be found [http://sepwww.stanford.edu/theses/sep60/60_25.pdf in SEP report nr. 60].		This document has been originally distributed together with vplot as <tt>pens/docs/vplothacker.doc . It has been placed on this wiki for enhanced readability, for version control and for easy editing which will increase its chances of being kept up to date. All relative file paths referred to in this document refer to the location mentioned above. More information may be found [http://sepwww.stanford.edu/theses/sep60/60_25.pdf in SEP report nr. 60].

	'''Hacker's guide to the innards of the Pen programs''',<br>		'''Hacker's guide to the innards of the Pen programs''',<br>

Nick: link to SEP 60

2009-01-09T12:03:38Z

link to SEP 60

← Older revision		Revision as of 12:03, 9 January 2009
Line 1:		Line 1:
	This page contains documentation included in the vplot distribution, (<tt>RSFSRC/pens/docs/vplothacker.doc</tt>). This documentation has been placed on this wiki for enhanced readability, for version control and for easy editing which will increase its chances of being kept up to date. All relative file paths referred to in this document refer to the location mentioned above.		This page contains documentation included in the vplot distribution, (<tt>RSFSRC/pens/docs/vplothacker.doc</tt>). This documentation has been placed on this wiki for enhanced readability, for version control and for easy editing which will increase its chances of being kept up to date. All relative file paths referred to in this document refer to the location mentioned above. More information may be found [http://sepwww.stanford.edu/theses/sep60/60_25.pdf in SEP report nr. 60].

	'''Hacker's guide to the innards of the Pen programs''',<br>		'''Hacker's guide to the innards of the Pen programs''',<br>

Nick at 22:12, 4 November 2008

2008-11-04T22:12:54Z

← Older revision		Revision as of 22:12, 4 November 2008
Line 1:		Line 1:
	This page contains documentation included in the vplot distribution, (<tt>~~seplib-6.5.3~~/~~vplot~~/~~Docs~~/vplothacker.doc</tt>). This documentation has been placed on this wiki for enhanced readability, for version control and for easy editing which will increase its chances of being kept up to date. All relative file paths referred to in this document refer to the location mentioned above.		This page contains documentation included in the vplot distribution, (<tt>RSFSRC/pens/docs/vplothacker.doc</tt>). This documentation has been placed on this wiki for enhanced readability, for version control and for easy editing which will increase its chances of being kept up to date. All relative file paths referred to in this document refer to the location mentioned above.

	'''Hacker's guide to the innards of the Pen programs''',<br>		'''Hacker's guide to the innards of the Pen programs''',<br>

Nick: /* Being tricky about the order things are plotted */

2008-11-04T22:03:32Z

Being tricky about the order things are plotted

← Older revision		Revision as of 22:03, 4 November 2008
Line 1,186:		Line 1,186:
	<c>		<c>
	extern int (*genreader) ();		extern int (*genreader) ();
	<(c>		</c>
	can be changed in dev.open to point to your own routine for processing		can be changed in dev.open to point to your own routine for processing
	input files. You should only need to change this variable if for some		input files. You should only need to change this variable if for some
Line 1,198:		Line 1,198:
	already does the job of finding all the input files, verifying that		already does the job of finding all the input files, verifying that
	they exist, and opening them for reading.		they exist, and opening them for reading.
			<c>
	gen_do_dovplot (nn, inpltin, innames)		gen_do_dovplot (nn, inpltin, innames)
	int nn;		int nn;
Line 1,214:		Line 1,214:
	}		}
	}		}
			</c>
	"Nn" is the number of input files. "Inpltin" is an array of nn stream		"Nn" is the number of input files. "Inpltin" is an array of nn stream
	pointers each of which point to an open (but unread-upon) input stream.		pointers each of which point to an open (but unread-upon) input stream.
Line 1,240:		Line 1,240:
	time around.		time around.

	~~-------------------------------------------------------------------------~~		==Things that get reset between frames (and things that don't)==
	~~THINGS THAT GET RESET BETWEEN FRAMES~~ (~~AND THINGS THAT DON~~'T)

	Vplot has many "global" parameters. Some of these get reset between		Vplot has many "global" parameters. Some of these get reset between
Line 1,263:		Line 1,262:
	global otherwise. It has no libvplot command on purpose.		global otherwise. It has no libvplot command on purpose.

	~~-------------------------------------------------------------------------~~		==Groups==
	~~GROUPS~~

	The begin-end group commands are provided so that a "MacDraw"-like		The begin-end group commands are provided so that a "MacDraw"-like
	vplot editor may be created. The device knows when groups are		vplot editor may be created. The device knows when groups are
Line 1,297:		Line 1,294:
	open groups.		open groups.

	~~-------------------------------------------------------------------------~~		==SEPlib tricks==
	~~SEPLIB TRICKS~~

	If you don't use the seplib versions of the filters, you can ignore		If you don't use the seplib versions of the filters, you can ignore
Line 1,342:		Line 1,338:
	the header. (This is why Raspen uses fake headers.)		the header. (This is why Raspen uses fake headers.)

	~~-------------------------------------------------------------------------~~		==Frontend, and doing it yourself==
	~~FRONTEND~~, and ~~DOING IT YOURSELF~~

	The system-user interface is split among three routines, which together		The system-user interface is split among three routines, which together
	are called the "frontend".		are called the "frontend".
Line 1,390:		Line 1,384:
	in .../vplot/filters for an example of how to do this.		in .../vplot/filters for an example of how to do this.

	~~-------------------------------------------------------------------------~~		==Authors==
	~~AUTHORS~~
	The present generation of pen filters were created by Joe Dellinger.		The present generation of pen filters were created by Joe Dellinger.
	The original pen programs were written by Jeff Thorson and Rob Clayton.		The original pen programs were written by Jeff Thorson and Rob Clayton.
Line 1,399:		Line 1,392:
	has found and fixed obscure bugs.		has found and fixed obscure bugs.

	~~COPYRIGHT~~		==Copyright==
	Vplot is copyrighted. Please read the copyright in the accompanying		Vplot is copyrighted. Please read the copyright in the accompanying
	"Vplot" manual page. The copyright is not very restrictive. If you		"Vplot" manual page. The copyright is not very restrictive. If you
Line 1,408:		Line 1,401:
	it for themselves or trying to sell it.		it for themselves or trying to sell it.

	~~SEE ALSO~~		==See also==
	vplot(L) pen(L) plas(L) pldb(L) seplib(L) getpar(L)		vplot(L) pen(L) plas(L) pldb(L) seplib(L) getpar(L)

Nick: /* Being efficient */

2008-11-04T22:00:25Z

Being efficient

← Older revision		Revision as of 22:00, 4 November 2008
Line 1,144:		Line 1,144:
	Typical causes of such problems:		Typical causes of such problems:

	Drawing the vertices of a polygon in the "wrong" direction.		* Drawing the vertices of a polygon in the "wrong" direction.
			* Filling a polygon that is "too long and skinny".
	Filling a polygon that is "too long and skinny".		* Filling a polygon with "too complicated" a fill pattern.
			* Filling a polygon that doesn't end on the same point it started.
	Filling a polygon with "too complicated" a fill pattern.		* Filling a polygon that does end on the same point it started.
			* Doing "too many" draws in a row without a move.
	Filling a polygon that doesn't end on the same point it started.		* Hitting the same point several times in the same set of moves and draws.
			* Drawing "too near" the edge of the page.
	Filling a polygon that does end on the same point it started.		* Drawing lines "too close" together.
			* Drawing "too complicated" a plot.
	Doing "too many" draws in a row without a move.		* Trying to use the machine immediately after somebody else's job on it has bombed.
			* Having 2 computers try to talk to the same machine at the same time.
	Hitting the same point several times in the same set of moves		* Processing "too many" jobs without powering off and on the machine.
	and draws.		* Trying to do things that are more complicated than the simple examples in the documentation.
			* Trying to use the device at its rated baud rate.
	Drawing "too near" the edge of the page.

	Drawing lines "too close" together.

	Drawing "too complicated" a plot.

	Trying to use the machine immediately after somebody else's
	job on it has bombed.

	Having 2 computers try to talk to the same machine at
	the same time.

	Processing "too many" jobs without powering off and on the machine.

	Trying to do things that are more complicated than the simple
	examples in the documentation.

	Trying to use the device at its rated baud rate.

	Sometimes you can get around these problems in software, by checking for		Sometimes you can get around these problems in software, by checking for