DR2D IFF 2-D Objects - Revision history

Costel Mincea: Text replacement - "" to ""

2025-01-26T19:12:17Z

Text replacement - "<syntaxhighlight>" to "<syntaxhighlight lang="C" line>"

Steven Solie: /* FILL */

2013-05-27T18:47:37Z

FILL

← Older revision		Revision as of 18:47, 27 May 2013
Line 283:		Line 283:

	DR2D makes a "tile" out of the fill pattern, giving it a virtual bounding box based on the extreme X and Y values of the FILL's object		DR2D makes a "tile" out of the fill pattern, giving it a virtual bounding box based on the extreme X and Y values of the FILL's object
	(Figure A). The bounding box shown in ~~Fig.~~ A surrounding the pattern (the two ellipses) is invisible to the user. In concept, this		(Figure A). The bounding box shown in Figure A surrounding the pattern (the two ellipses) is invisible to the user. In concept, this
	rectangle is pasted on the page left to right, top to bottom like floor tiles (Figure B). Again, the bounding boxes are not visible. The		rectangle is pasted on the page left to right, top to bottom like floor tiles (Figure B). Again, the bounding boxes are not visible. The
	only portion of this tiled pattern that is visible is the part that overlaps the object (Figure C) being filled. The object's path is		only portion of this tiled pattern that is visible is the part that overlaps the object (Figure C) being filled. The object's path is

Steven Solie at 18:46, 27 May 2013

2013-05-27T18:46:23Z

← Older revision		Revision as of 18:46, 27 May 2013
Line 5:		Line 5:
	Description by Ross Cunniff and John Orr		Description by Ross Cunniff and John Orr

	A standard IFF FORM to describe 2D drawings has been sorely needed for a long time. Several commercial drawing packages have been available for some time but none has established its file format as the Amiga standard. The absence of a 2D drawing standard hinders the development of applications that use 2D drawings as it forces each application to understand several private standards instead of a single one. Without a standard, data exchange for both the developer and the user is difficult, if not impossible.		A standard IFF FORM to describe 2D drawings has been sorely needed for a long time. Several commercial drawing packages have been available for some time but none has established its file format as the Amiga standard. The absence of a 2D drawing standard hinders the development of applications that use 2D drawings as it forces each application to understand several private standards instead of a single one. Without a standard, data exchange for both the developer and the user is difficult, if not impossible.

	The DR2D FORM fills this void. This FORM was developed by Taliesin, Inc. for use as the native file format for their two-dimensional structured drawing package, ProVector. Saxon Industries and Soft Logik Publishing Corporation are planning to support this new FORM in		The DR2D FORM fills this void. This FORM was developed by Taliesin, Inc. for use as the native file format for their two-dimensional structured drawing package, ProVector. Saxon Industries and Soft Logik Publishing Corporation are planning to support this new FORM in
	the near future.		the near future.

	Many of the values stored in the DR2D FORM are stored as IEEE single precision floating point numbers. These numbers consist of 32 bits, arranged as follows:		Many of the values stored in the DR2D FORM are stored as IEEE single precision floating point numbers. These numbers consist of 32 bits, arranged as follows:

	_______________________________________________________________________		_______________________________________________________________________
Line 295:		Line 295:
	A DR2D project is broken up into one or more layers. Each DR2D object		A DR2D project is broken up into one or more layers. Each DR2D object
	is in one of these layers. Layers provide several useful features.		is in one of these layers. Layers provide several useful features.
	Any particular layer can be ``turned off'', so that the objects in the		Any particular layer can be "turned off", so that the objects in the
	layer are not displayed. This eliminates the unnecessary display of		layer are not displayed. This eliminates the unnecessary display of
	objects not currently needed on the screen. Also, the user can lock a		objects not currently needed on the screen. Also, the user can lock a
Line 449:		Line 449:

	FORM xxxx DR2D {		FORM xxxx DR2D {
	XTRN xxxx { X_RESIZE \| X_MOVE, 10, ~~"~~Dimension~~"~~ }		XTRN xxxx { X_RESIZE \| X_MOVE, 10, "Dimension" }
	ATTR xxxx { 0, 0, 1, 0, 0, 0, 0.0 }		ATTR xxxx { 0, 0, 1, 0, 0, 0, 0.0 }
	FORM xxxx DR2D {		FORM xxxx DR2D {
	GRUP xxxx { 2 }		GRUP xxxx { 2 }
	STXT xxxx { 0, 0.5, 1.0, 6.0, 5.0, 0.0, 4, ~~"~~3.0~~"~~ }		STXT xxxx { 0, 0.5, 1.0, 6.0, 5.0, 0.0, 4, "3.0" }
	OPLY xxxx { 2, { 5.5, 5.5, 8.5, 5.5 } }		OPLY xxxx { 2, { 5.5, 5.5, 8.5, 5.5 } }
	}		}
Line 464:		Line 464:
	parameters are described below.		parameters are described below.

	X_CLONE ``appl CLONE objID dx dy''		X_CLONE "appl CLONE objID dx dy"
	X_MOVE ``appl MOVE objID dx dy''		X_MOVE "appl MOVE objID dx dy"
	X_ROTATE ``appl ROTATE objID cx cy angle''		X_ROTATE "appl ROTATE objID cx cy angle"
	X_RESIZE ``appl RESIZE objID cx cy sx sy''		X_RESIZE "appl RESIZE objID cx cy sx sy"
	X_CHANGE ``appl CHANGE objID et ev ft fv ew jt fn''		X_CHANGE "appl CHANGE objID et ev ft fv ew jt fn"
	X_DELETE ``appl DELETE objID''		X_DELETE "appl DELETE objID"
	X_CUT ``appl CUT objID''		X_CUT "appl CUT objID"
	X_COPY ``appl COPY objID''		X_COPY "appl COPY objID"
	X_UNGROUP ``appl UNGROUP objID''		X_UNGROUP "appl UNGROUP objID"

	where:		where:
Line 585:		Line 585:
	important connection between a polygon and its subpolygon.		important connection between a polygon and its subpolygon.
	Subpolygons make it possible to create holes in polygons. An example		Subpolygons make it possible to create holes in polygons. An example
	of a polygon with a hole is the letter ``O''. The ``O'' is a filled		of a polygon with a hole is the letter "O". The "O" is a filled
	circular polygon with a smaller circular polygon within it. The		circular polygon with a smaller circular polygon within it. The
	reason the inner polygon isn't covered up when the outer polygon is		reason the inner polygon isn't covered up when the outer polygon is
	filled is that DR2D fills are done using the even-odd rule.		filled is that DR2D fills are done using the even-odd rule.

	The even-odd rule determines if a point is ``inside'' a polygon by		The even-odd rule determines if a point is "inside" a polygon by
	drawing a ray outward from that point and counting the number of path		drawing a ray outward from that point and counting the number of path
	segments the ray crosses. If the number is even, the point is outside		segments the ray crosses. If the number is even, the point is outside
Line 806:		Line 806:
	DRHD 16 { 0.0, 0.0, 10.0, 8.0 }		DRHD 16 { 0.0, 0.0, 10.0, 8.0 }
	CMAP 6 { 0,0,0, 255,255,255 }		CMAP 6 { 0,0,0, 255,255,255 }
	FONS 9 { 1, 0, 1, 0, ~~"~~Roman~~"~~ } 0		FONS 9 { 1, 0, 1, 0, "Roman" } 0
	DASH 12 { 1, 2, {1.0, 1.0} }		DASH 12 { 1, 2, {1.0, 1.0} }
	ATTR 14 { 0, 0, 1, 0, 0, 0, 0, 0.0 }		ATTR 14 { 0, 0, 1, 0, 0, 0, 0, 0.0 }
Line 813:		Line 813:
	GRUP 2 { 2 }		GRUP 2 { 2 }
	BBOX 16 { 3.0, 4.0, 7.0, 5.0 }		BBOX 16 { 3.0, 4.0, 7.0, 5.0 }
	STXT 36 { 0,1, 0.5, 1.0, 3.0, 5.0, 0.0, 12, ~~"~~Hello, World~~"~~ }		STXT 36 { 0,1, 0.5, 1.0, 3.0, 5.0, 0.0, 12, "Hello, World" }
	BBOX 16 { 2.0, 2.0, 8.0, 6.0 }		BBOX 16 { 2.0, 2.0, 8.0, 6.0 }
	OPLY 42 { 5, {2.0,2.0, 8.0,2.0, 8.0,6.0, 2.0,6.0, 2.0,2.0 }		OPLY 42 { 5, {2.0,2.0, 8.0,2.0, 8.0,6.0, 2.0,6.0, 2.0,2.0 }

Steven Solie: /* FILL */

2013-05-27T18:42:49Z

FILL

← Older revision		Revision as of 18:42, 27 May 2013
Line 268:		Line 268:
	FILL (0x46494C4C) /* Object-oriented fill pattern */		FILL (0x46494C4C) /* Object-oriented fill pattern */

	The FILL chunk defines a fill pattern. This chunk is only valid		The FILL chunk defines a fill pattern. This chunk is only valid inside nested DR2D FORMs. The GRUP object chunk section of this article contans an example of the FILL chunk.
	inside nested DR2D FORMs. The GRUP object chunk section of this
	article contans an example of the FILL chunk.

	<syntaxhighlight>		<syntaxhighlight>
	struct FILLstruct {		struct FILLstruct {
	ULONG ID;		ULONG ID;
	ULONG Size;		ULONG Size;
	USHORT FillID; /* ID of the fill */		USHORT FillID; /* ID of the fill */
			};
	};
	</syntaxhighlight>		</syntaxhighlight>

	FillID is the number by which the ATTR object attribute chunk		FillID is the number by which the ATTR object attribute chunk references fill patterns. The FILL chunk must be the first chunk inside a nested DR2D FORM. A FILL is followed by one DR2D object plus any of the object attribute chunks (ATTR, BBOX) associated with the object.
	references fill patterns. The FILL chunk must be the first chunk
	inside a nested DR2D FORM. A FILL is followed by one DR2D object plus
	any of the object attribute chunks (ATTR, BBOX) associated with the
	object.

	[[File:dr2d-2.png\|frame\|center\|Fill Patterns]]		[[File:dr2d-2.png\|frame\|center\|Fill Patterns]]

	DR2D makes a ``tile'' out of the fill pattern, giving it a virtual		DR2D makes a "tile" out of the fill pattern, giving it a virtual bounding box based on the extreme X and Y values of the FILL's object
	bounding box ~~based~~ on the ~~extreme~~ X ~~and~~ Y ~~values~~ of the ~~FILL's~~ ~~object~~		(Figure A). The bounding box shown in Fig. A surrounding the pattern (the two ellipses) is invisible to the user. In concept, this
		⚫	rectangle is pasted on the page left to right, top to bottom like floor tiles (Figure B). Again, the bounding boxes are not visible. The
	(Fig. A). The bounding box shown in Fig. A surrounding the pattern
		⚫	only portion of this tiled pattern that is visible is the part that overlaps the object (Figure C) being filled. The object's path is
	(the two ellipses) is invisible to the user. In concept, this
		⚫	called a clipping path, as it "clips" its shape from the tiled pattern (Figure D). Note that the fill is only masked on top of
⚫	rectangle is pasted on the page left to right, top to bottom like
		⚫	underlying objects, so any "holes" in the pattern will act as a window, leaving visible underlying objects.
	floor tiles (Fig. B). Again, the bounding boxes are not visible. The
⚫	only portion of this tiled pattern that is visible is the part that
	overlaps the object (Fig. C) being filled. The object's path is
⚫	called a clipping path, as it ``clips'' its shape from the tiled
	pattern (Fig. D). Note that the fill is only masked on top of
⚫	underlying objects, so any ``holes'' in the pattern will act as a
	window, leaving visible underlying objects.

	=== LAYR ===		=== LAYR ===

Steven Solie: /* DASH */

2013-05-27T18:41:11Z

DASH

← Older revision		Revision as of 18:41, 27 May 2013
Line 213:		Line 213:
	</syntaxhighlight>		</syntaxhighlight>

	DashID is the number assigned to this specific dash pattern.		DashID is the number assigned to this specific dash pattern. References to this dash pattern by other DR2D chunks are made using
	References to this dash pattern by other DR2D chunks are made using
	this number.		this number.

	The Dashes[] array contains the actual dash pattern. The first number		The Dashes[] array contains the actual dash pattern. The first number in the array (element 0) is the length of the "on" portion of the
	in ~~the~~ ~~array~~ (element 0) is the ~~length~~ of the ~~``on''~~ ~~portion~~ of the		pattern. The second number (element 1) specifies the "off" portion of the pattern. If there are more entries in the Dashes array, the
		⚫	pattern will continue. Even-index elements specify the length of an "on" span, while odd-index elements specify the length of an "off"
	pattern. The second number (element 1) specifies the ``off'' portion
			span. There must be an even number of entries. These lengths are not in the same units as specified in the PPRF chunk, but are multiples of the line width, so a line of width 2.5 and a dash pattern of 1.0, 2.0 would have an "on" span of length 1.0 x 2.5 = 2.5 followed by an "off" span of length 2.0 x 2.5 = 5. The following figure shows several dash pattern examples. Notice that for lines longer than the dash pattern, the pattern repeats.
	of the pattern. If there are more entries in the Dashes array, the
⚫	pattern will continue. Even-index elements specify the length of an
	``on'' span, while odd-index elements specify the length of an ``off''
	span. There must be an even number of entries. These lengths are not
	in the same units as specified in the PPRF chunk, but are multiples of
	the line width, so a line of width 2.5 and a dash pattern of 1.0, 2.0
	would have an ``on'' span of length 1.0 x 2.5 = 2.5 followed by an
	``off'' span of length 2.0 x 2.5 = 5. The following figure shows
	several dash pattern examples. Notice that for lines longer than the
	dash pattern, the pattern repeats.

	[[File:dr2d-1.png\|frame\|center\|Dash Patterns]]		[[File:dr2d-1.png\|frame\|center\|Dash Patterns]]

	By convention, DashID 0 is reserved to mean `No line pattern at all',		By convention, DashID 0 is reserved to mean "No line pattern at all", i.e. the edges are invisible. This DASH pattern should not be defined by a DR2D DASH chunk. Again by convention, a NumDashes of 0 means that the line is solid.
	i.e. the edges are invisible. This DASH pattern should not be defined
	by a DR2D DASH chunk. Again by convention, a NumDashes of 0 means
	that the line is solid.

	=== AROW ===		=== AROW ===

Steven Solie at 17:07, 27 May 2013

2013-05-27T17:07:25Z

Show changes

Steven Solie: /* A Simple DR2D Example */

2013-05-27T17:03:15Z

A Simple DR2D Example

← Older revision		Revision as of 17:03, 27 May 2013
Line 816:		Line 816:
	[[File:dr2d-4.png\|frame\|center\|Simple DR2D drawing]]		[[File:dr2d-4.png\|frame\|center\|Simple DR2D drawing]]

		⚫	= The OFNT FORM =

			== OFNT ==
	<pre>
⚫	The OFNT FORM


	OFNT (0x4F464E54) /* ID of outline font file */		OFNT (0x4F464E54) /* ID of outline font file */
Line 827:		Line 826:
	fonts defined in the OFNT form.		fonts defined in the OFNT form.

			== OFHD ==

	OFHD (0x4F464844) /* ID of OutlineFontHeaDer */		OFHD (0x4F464844) /* ID of OutlineFontHeaDer */
Line 853:		Line 853:
	character width.		character width.

			== KERN ==

	KERN (0x4B45524C) /* Kerning pair */		KERN (0x4B45524C) /* Kerning pair */
Line 873:		Line 874:
	supply the baseline shift from Ch1 to Ch2.		supply the baseline shift from Ch1 to Ch2.

			== CHDF ==



	CHDF (0x43484446) /* Character definition */		CHDF (0x43484446) /* Character definition */
Line 880:		Line 880:
	This chunk defines the shape of ProVector's outline fonts.		This chunk defines the shape of ProVector's outline fonts.

			<syntaxhighlight>
	struct CHDFstruct {		struct CHDFstruct {
	short Ch; /* The character we're defining (ASCII) */		short Ch; /* The character we're defining (ASCII) */
Line 887:		Line 888:
	/* IEEE Points[2NumPoints]/ /* The actual points */		/* IEEE Points[2NumPoints]/ /* The actual points */
	};		};


	#define INDICATOR 0xFFFFFFFF /* If X == INDICATOR, Y is an action */		#define INDICATOR 0xFFFFFFFF /* If X == INDICATOR, Y is an action */
Line 894:		Line 894:
	#define IND_STROKE 0x00000004 /* Stroke previous path */		#define IND_STROKE 0x00000004 /* Stroke previous path */
	#define IND_FILL 0x00000008 /* Fill previous path */		#define IND_FILL 0x00000008 /* Fill previous path */
			</syntaxhighlight>

	Ch is the value (normally ASCII) of the character outline this chunk		Ch is the value (normally ASCII) of the character outline this chunk
Line 917:		Line 918:
	attributes of the line. These two bits apply only to the OFNT FORM		attributes of the line. These two bits apply only to the OFNT FORM
	and should not be used in describing DR2D polygons.		and should not be used in describing DR2D polygons.
	</pre>

Steven Solie at 16:07, 14 May 2013

2013-05-14T16:07:18Z

← Older revision		Revision as of 16:07, 14 May 2013
Line 792:		Line 792:
	rendered. The points of Path[] are in the same format as the points		rendered. The points of Path[] are in the same format as the points
	of a DR2D polygon.		of a DR2D polygon.


		⚫	= A Simple DR2D Example =
⚫	<pre>
⚫	A Simple DR2D Example

	Here is a (symbolic) DR2D FORM:		Here is a (symbolic) DR2D FORM:
Line 815:		Line 814:


	[~~Figure~~ 4 - Simple DR2D drawing]		[[File:dr2d-4.png\|frame\|center\|Simple DR2D drawing]]


		⚫	<pre>
	The OFNT FORM		The OFNT FORM

Steven Solie: /* CPLY and OPLY */

2013-05-14T16:05:22Z

CPLY and OPLY

← Older revision		Revision as of 16:05, 14 May 2013
Line 686:		Line 686:


			=== GRUP ===
⚫	<pre>

	GRUP (0x47525550) /* Group */		GRUP (0x47525550) /* Group */

Line 725:		Line 726:
	}		}

			=== STXT ===


	STXT (0x53545854) /* Simple text */		STXT (0x53545854) /* Simple text */
Line 754:		Line 755:
	comparable to an X and Y font size.		comparable to an X and Y font size.

			=== TPTH ===


	TPTH (0x54505448) /* A text string along a path */		TPTH (0x54505448) /* A text string along a path */
Line 792:		Line 793:
	of a DR2D polygon.		of a DR2D polygon.

		⚫	<pre>


	A Simple DR2D Example		A Simple DR2D Example

Steven Solie: /* CPLY and OPLY */

2013-05-14T16:03:14Z

CPLY and OPLY

← Older revision		Revision as of 16:03, 14 May 2013
Line 563:		Line 563:
	coordinates and the odd index elements are Y coordinates.		coordinates and the odd index elements are Y coordinates.

	[~~Figure~~ 3 - Bezier curves]		[[File:dr2d-3.png\|frame\|center\|Bezier curves]]

	DR2D uses Bezier cubic sections, or cubic splines, to describe curves		DR2D uses Bezier cubic sections, or cubic splines, to describe curves