Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!utcsri!utegc!utai!garfield!john13
From: john13@garfield.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Program-independent rastports
Message-ID: <3904@garfield.UUCP>
Date: Wed, 26-Aug-87 22:24:23 EDT
Article-I.D.: garfield.3904
Posted: Wed Aug 26 22:24:23 1987
Date-Received: Sun, 30-Aug-87 07:24:02 EDT
References: <3878@garfield.UUCP> <329@l5comp.UUCP>
Organization: CS Dept., Memorial U. of Newfoundland, St. John's
Lines: 27
Summary: finding a system structure

In article <329@l5comp.UUCP>, scotty@l5comp.UUCP (Scott Turner) writes:
  
[ syntactical and implementation notes for a "graphics-handler" ]

>Much nicer though would be to have named pictures so that multiple draw's could
>be open at once.

Naming pictures is a win, with the easiest way being to use an actual screen
or window name and having the Intuitionbase->FirstScreen to scan for that name.
As far as informing DPaint about some pre-existing graphics memory to work on,
I can imagine having a window named "Address = $00370a0" just so I have the
address of the rastport structure for reference. So "dpaint -address $00370a0"
becomes possible (although this looks ugly even to me, I'll do anything to be
able to draw a better picture with less work :-).

Using programs like copy, type, and such to pass info back and forth is of
course highly desirable. I guess these would always be necessary from the
CLI, while opening a "draw:foo" file and reading/writing to it would be the
preferred mode of access from within Basic, C, Modula, Lisp, Forth, Smalltalk
et al. Hmmm, yeah, I'll write my fractal code in Lisp, that's the ticket. So
what if this version doesn't support graphics - all you need be able to do is
calculate coordinates and write to a file.

John
-- 
"Gimme ten puddings."
	-- Dan Fielding