Re: /* STUPID QUESTION */
Re: /* STUPID QUESTION */
- Subject: Re: /* STUPID QUESTION */
- From: Matthew Klahn <email@hidden>
- Date: Fri, 16 May 2003 10:30:34 -0500
On Friday, May 16, 2003, at 10:09 America/Chicago, David Brown wrote:
On Fri, May 16, 2003 at 08:37:59AM -0500, Matthew Klahn wrote:
Having said all of that, I do wish that they would make X11 windows
conform to the Carbon or Cocoa APIs so that we could get more of
CodeTek VirtualDesktop working with X11... :)
As I understand it, that is more just an issue of getting Apple's X
server to work well with VirtualDesktop. There is even another server
that they have modified to support it quite well.
Dave
Hi, David.
I'm not sure that I was very clear, or maybe I just don't understand
your mail. I work here at CodeTek, the company that writes CodeTek
VirtualDesktop, and I know all about the incompatibilities w/ X11 and
the compatibility with OroborOSX. :)
My point was that we cannot modify CodeTek VirtualDesktop to get
information that is not provided by Apple's X11 windows, such as the
title of the window, nor can we act upon them in the same way that we
do Carbon/Cocoa windows, such as giving them focus (for the
Focus-Follows-Mouse feature, and during desktop switching), for another
example.[1] If Apple would be kind enough to make X11 windows work like
(or actually be) Carbon windows or Cocoa windows, we could just ask the
window what it's title was, for example, or make it the key window
directly ourselves. I'm not sure how hard this would be, but Apple told
us that they are looking into this and will let us know how feasible
this would be.
This isn't only a problem with CodeTek VirtualDesktop; any application
that would like to get window information from the window list and
global window IDs would have the same problems that we do. I can't
think of any apps off the top of my head, but that doesn't mean that
they aren't there... :)
By the way, we didn't modify OroborOSX to work with CodeTek
VirtualDesktop, Adrian Umpleby (the OroborOSX developer) worked with us
to find ways that we both (CodeTek and Adrian) could make changes to
CTVD and OroborOSX, respectively, to work together well. Now that we
have explicit support for OroborOSX in CTVD, we would like Apple to
adopt similar changes in X11 to those in OroborOSX so that X11 would be
more CTVD 'aware', but that's something different entirely. (And,
again, they have said that they are looking into this as well.)
Hope this helps to clear up my previous email. :)
--
Matthew S. Klahn
Software Architect, CodeTek Studios, Inc.
http://www.codetek.com
[1] Well, _maybe_ we can, and we are researching how to do this.
However it appears to be very difficult, since we have to get a handle
to the actual X server and find the info we need (such as window
titles, etc.) or perform the necessary actions via the X Window API
(something that we're not familiar with, and depends on how well each
application conforms to the X Window standards; for example, it's up to
the application to register window titles with the X Server, etc.).
We've done some preliminary analysis of this, but are stuck on some
unresolved issues.
_______________________________________________
x11-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/x11-users
X11 for Mac OS X FAQ: http://developer.apple.com/qa/qa2001/qa1232.html
Report issues, request features, feedback: http://developer.apple.com/bugreporter
Do not post admin requests to the list. They will be ignored.