🚀 go-pugleaf

In article <280@joevax.UUCP>, sdh@joevax.UUCP (The Doctor) writes:
> 
> stack it, else nothing. Repeat until all pixels have been hit.  Go through
> the stack and make the changes.
> 
> This should be very efficient on images with plenty of consistent background,
> and not too many objects in the foreground.  It will use up more memory than
> you'd really like on complex pictures.
> 
> Ways to eliminate this problem:
> 
> Forget the stack entirely and just put the image out to a file, or an
> alternate graphics display.  This will have a memory consumption that will
> be a constant, which is far smaller than the worst case of stacking.
> 
> Do separate passes for red, green and blue, thus reducing the data that has
> to be stacked.
> 
> Don't do the whole screen in one pass.  Just do it in blocks of 3 scan lines
> The reasoning behind this is that the fourth line down only needs to know
> about line 3 and line 4, so it can forget about line 1 and 2.
> 
> I have no idea whether or not any of this is valid.  I started thinking about
> anti-aliasing about 5 minutes ago, so this is just off the top of my head.
> It seems to be a pretty brute force way of doing it, but swift.  If you
> only stack 3 lines at a time, it will be very memory efficient too.
> 

	Awe, come on..... This should all be done in *HARDWARE*



-- 

	UUCP : ihnp4!ptsfa!gilbbs!apnsys!root

	VOICE:	+1 707 433 0202 (work)
		+1 707 575 9616 (home)
		+1 707 538 1175 (more work)

{* War does not determine who is right or wrong........ only who is left *}
{* Only those who attempt the absurd   ...   will achieve the impossible *}