Moving output records for fast translation

• To: pkarp@Sunset.AI.SRI.COM, clim@BBN.COM
• Subject: Moving output records for fast translation
• From: "John G. Aspinall" <JGA@stony-brook.scrc.symbolics.com>
• Date: Fri, 1 May 1992 15:32-0400
• In-Reply-To: <CMM.0.90.2.704741941.pkarp@Rockaway.AI.SRI.COM>

    Date: Fri, 1 May 1992 13:39 EDT
    From: Peter Karp <pkarp@ai.sri.com>

    Imagine that a program has drawn a very complex picture, and it must
    then translate some elements of that picture as quickly as possible.
    My theory is that it will be faster to get CLIM to redraw the output
    records associated with those picture elements, with a translation
    applied, than it will be to completely redraw those picture elements
    at the application level (particularly if much computation is required
    at the application level).

Certainly.  This is what (e.g.) dragging-output does.

    Function shift-output-record below applies a translation to an output
    record.  This implementation was quite difficult to figure out....

Part of the CLIM 2 spec is a clearer definition of things like --
exactly what *is* the "position" of an output record?  Under the
proposed CLIM 2 way-of-doing-things, you would not have to know about
implementation-dependent things like
clim:convert-from-relative-to-absolute-coordinates.

• Moving output records for fast translation
• From: Peter Karp <pkarp>

• Prev: Moving output records for fast translation
• Next: Re: Moving output records for fast translation
• Index: CLIM Mailing list (1-Jan-92 to 31-Aug-92)
• Thread: CLIM Mailing list Index (1-Jan-92 to 31-Aug-92)