Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!decwrl!shelby!helens!baroque!jim From: jim@baroque.Stanford.EDU (James Helman) Newsgroups: comp.sys.sgi Subject: Re: SGI's migration to X Message-ID: Date: 5 Sep 90 20:07:47 GMT References: <208@voodoo.UUCP> <1990Sep4.213844.9865@odin.corp.sgi.com> Sender: news@helens.Stanford.EDU Organization: Stanford University Lines: 22 In-reply-to: msc@ramoth.esd.sgi.com's message of 4 Sep 90 21:38:44 GMT Obviously, I'm not very familiar with Sun's graphics. From what Mark says, I take it that Sun's DGA does not allow XGL and X drawing calls to be made in the same window. Basically then, it just allows XGL and X/NeWS windows to share the same screen without trouncing on each other. Once SGI's current window coexistence problems are fixed, will SGI's GL/X dichotomy be pretty much the same as Sun's XGL/X split? That is once a window is opened either as a local X window or as a "direct" graphics window, there is no way to get a handle for applying the other's drawing calls on that window? I've heard Vicom's new image processor supports something like this, allowing very high performance imaging operations when a local X window is accessed via another library interface. My other question: shared memory X transport? It seems like it would be a big win for portable X imaging applications like LLNL's View. Jim Helman Department of Applied Physics Durand 012 Stanford University FAX: (415) 725-3377 (jim@KAOS.stanford.edu) Voice: (415) 723-9127