All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ewan Mellor <ewan@xensource.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: ron minnich <rminnich@gmail.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	jason <fearthepenguin@jasonandjessi.com>
Subject: Re: 3.0.3 without X
Date: Thu, 4 Jan 2007 19:48:29 +0000	[thread overview]
Message-ID: <20070104194829.GA15265@leeni.uk.xensource.com> (raw)
In-Reply-To: <459D5661.6020004@codemonkey.ws>

On Thu, Jan 04, 2007 at 01:32:49PM -0600, Anthony Liguori wrote:

> Ewan Mellor wrote:
> >On Thu, Jan 04, 2007 at 03:01:08PM +0000, Keir Fraser wrote:
> >
> >>On 4/1/07 14:58, "ron minnich" <rminnich@gmail.com> wrote:
> >>
> >>>note that we're distributing an x11-free xen for plan 9 support, so I
> >>>sure hope that x11 dependencies are not about to start appearing in
> >>>xen.
> >>The dependencies are only in HVM-specific bits of the tools/ directory.
> >>Those are easily disabled, albeit with a smidgen of Makefile changes.
> >
> >They also aren't really X11 dependencies.  That code includes
> ><X11/keysymdef.h>, because VNC uses the same keysyms as X, but there's no
> >dependency upon X client libraries.
> 
> This dependency is actually a bug that was introduced in the Xen tree 
> (it isn't present in qemu CVS).
> 
> The VNC spec makes it pretty clear that you cannot rely on the symbolic 
> names of X keycodes to develop a portable VNC client.  Apparently they 
> change slightly across different X implementations.

>From www.realvnc.com/docs/rfbproto.pdf:

"The key itself is specified using the "keysym" values defined by the X Window
System.

For most ordinary keys, the "keysym" is the same as the corresponding
ASCII value.  For full details, see The Xlib Reference Manual, published by
O'Reilly & Associates, or see the header file <X11/keysymdef.h> from any X
Window System installation."


How do we choose which X keysyms to use, if they vary across X
implementations?

Ewan.

  reply	other threads:[~2007-01-04 19:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04 14:54 3.0.3 without X jason
2007-01-04 14:58 ` ron minnich
2007-01-04 15:01   ` Keir Fraser
2007-01-04 15:32     ` Ewan Mellor
2007-01-04 17:57       ` ron minnich
2007-01-04 18:11         ` jason
2007-01-04 18:12         ` Mark Williamson
2007-01-04 22:31         ` Ewan Mellor
2007-01-05  9:31           ` Dependency checking - early was " Steve Kemp
2007-01-04 19:32       ` Anthony Liguori
2007-01-04 19:48         ` Ewan Mellor [this message]
2007-01-04 21:17           ` Anthony Liguori
2007-01-04 22:38             ` Ewan Mellor
2007-01-04 14:59 ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070104194829.GA15265@leeni.uk.xensource.com \
    --to=ewan@xensource.com \
    --cc=anthony@codemonkey.ws \
    --cc=fearthepenguin@jasonandjessi.com \
    --cc=rminnich@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.