Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!bloom-beacon!EXPO.LCS.MIT.EDU!rws From: rws@EXPO.LCS.MIT.EDU Newsgroups: comp.windows.x Subject: Re: R3 Selection Mechanism Message-ID: <8905241501.AA01105@expire.lcs.mit.edu> Date: 24 May 89 15:01:29 GMT References: Sender: daemon@bloom-beacon.MIT.EDU Organization: The Internet Lines: 15 Show how to utilize the X selection mechanism to implement the above user interface. I kinda doubt anyone's going to take you up on this. I think it's pretty clear that the Andrew UI is tightly coupled with the cut buffer mechanism (which is why RotateProperties exists in the protocol, and why cut buffers are described in the ICCCM). Given the particular constraints, I doubt there's any elegant way to use the selection mechanism for this UI. But, as I said, there was no expectation that the selection mechanism would be suitable for all UIs. On the other hand, I think the selection mechanism is quite suitable for a range of UIs (both inside and outside X) that are on the market today, and many product UIs in the X environment will use it. To maximize "interoperability" between different applications, I do believe we should encourage use of the mechanism.