OpenEuphoria

Initial thoughts - printable parts

• Posted by Pete Lomax <petelomax at blueyonder.co.uk> Jan 03, 2003
• 394 views

Request for comments:

I am in the process of composing a list of items to be printed on a
report. I think this list is fairly complete. I am, for some unknown
reason, struggling to create an appropriate data structure for these
(expressed as a euphoria sequence) which remains unambiguous. Rather
than bore you with my errors,  maybe a fresh mind?
The items to be printed are:
1) field: x,y in pixels|%|inches|millimetres
	eg {200,100}, {"75%","10%"}, {"3 3/4\"","2.3\""},{"4cm","2.54cm"}
	record eg customer, order.
	field name/identifier
	formatting string eg "%f5.2"
	Font eg "Arial"	-- [1] kept in separate linked list
	Pitch eg "12"		-- [1] ""
	Colour
	Weight  - Normal/Bold/Italic/Both
	1.b) repeating fields
		columns, rows
		across or down	a c	or	a b
						b d		c d

[1] Note: for performance (ie setFont) reasons, all the fields of
     a specified font/pitch would best be printed all together for
     each page with the data redundancy suggested above also   =20
     eliminated.]

2) Fixed text: as field, but not repeating, probably
	Text
3) rectangles: x1, y1 as field, x2,y2 similar,
	colour, weight (line width in pixels/mm/inch/%)
4) bitmap: source file/ xpm constant (how to differentiate?)
	x1,y1,x2,y2 as rectangle.
	clip cx1,cy1,cx2,cy2
	paintmode
	background
	greyscale

Does this list contain all *needed* stuff for a report? (Obviously, if
i might need it, post a code snippet to display whatever it is you are
suggesting on screen, or you will be ignored.) Do not even thing of
posting {Arc, Circle, Ellipse, ... Zoid}, well, not without adequate
justification and/or asbestos undies anyway.=20

Pete