Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!uunet!comp.vuw.ac.nz!actrix!templar!jbickers
From: jbickers@templar.actrix.gen.nz (John Bickers)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re: (Video) Hardware Idiots ?
Message-ID: <4315.tnews@templar.actrix.gen.nz>
Date: 10 Jun 91 10:01:21 GMT
References: <1991Jun8.085839.3556@news.iastate.edu> <1991Jun8.191231 <1991Jun10.040317.25396@ncsu.edu> <1991Jun10.065129.4135@mintaka.lcs.mit.edu>
Organization: TAP, NZAmigaUG.
Lines: 25

Quoted from <1991Jun10.065129.4135@mintaka.lcs.mit.edu> by rjc@wookumz.gnu.ai.mit.edu (Ray Cromwell):
>   No, I think DIG could be fairly fast if some assumptions are made
> to trade flexibility for speed. Like assuming planes are in bitplane
> format, assuming the video card has a data mover (blitter) or 

    What about the library accepting data in either format, and
    providing functions to convert (and not render) this data into some
    format good for the board that the app. doesn't necessarily know
    about?

    For example, an animation player might call a type checking function
    to see whether the data could do with conversion, then run each
    delta chunk through the conversion routine(s) before starting to
    display them. Seperate programs could just do conversion (of
    animations, pictures, etc) from one type to another.

    The valid formats for each type within each kind of data would have
    to be standardised, and the library would have to do a whole lot
    more than the current one does (like "take this delta chunk and
    update the current frame with it").

> / INET:rjc@gnu.ai.mit.edu     *   // The opinions expressed here do not      \
--
*** John Bickers, TAP, NZAmigaUG.        jbickers@templar.actrix.gen.nz ***
***         "Endless variations, make it all seem new" - Devo.          ***