specializing CLIM windows ...

• To: buff@cc.gatech.edu, clim@BBN.COM
• Subject: specializing CLIM windows ...
• From: "William M. York" <York@chuck-jones.west.dialnet.ila.com>
• Date: Sun, 29 Mar 1992 22:22-0800
• In-Reply-To: <19920327223124.6.BUFF@kant.gatech.edu>

    Date: Fri, 27 Mar 1992 14:31 PST
    From: Richard Billington <buff@cc.gatech.edu>

    The doc. for CLIM:open-window-stream option :window-type says:

	    The name of the clas of window to create. The default
	    is the class normally used by CLIM for the parent win-
	    dow. This argument is provided so that you can special-
	    ize CLIM window classes, but should be used sparingly.

    Ok. Now, if I look at what it opens without this parameter, it's
    CLIM::SHEET-WINDOW-STREAM, which looks like it is composed of CLIM::WINDOW
    STREAM and CLIM::SHEET-IMPLEMENTATION-MIXIN. I (apparently incorrectly)
    assumed that I needed to specialize the CLIM::WINDOW-STREAM class so I could
    remain device independent - I figured that the :PARENT option would make it
    clear that I needed to have the sheet stuff mixed in. Yea, it sounds like
    magic, but I was hoping that I could specialize a CLIM window class that was
    device independent. Is this doable in some way?

This is one of the architectural limitations of CLIM 1.  It is
what led us to split out the device-dependent stuff into the
"port" and "medium" components in the CLIM 2 design.  That allows
you to specialize the portable "window" object class, which then
incorporates the correct  device-dependent component (e.g. a
medium that implements graphics via CLX or via Mac Toolbox
calls).

For now, you have to define SHEET-MY-CLASS and CLX-MY-CLASS and
so on.

• specializing CLIM windows ...
• From: Richard Billington <buff@cc.gatech.edu>

• Prev: scroll-bars
• Next: scroll-bars
• Index: CLIM Mailing list (1-Jan-92 to 31-Aug-92)
• Thread: CLIM Mailing list Index (1-Jan-92 to 31-Aug-92)