9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Digby Tarvin digbyt@acm.org
Subject: [9fans] X device
Date: Tue, 25 Aug 1998 18:03:31 +0100	[thread overview]
Message-ID: <19980825170331.gW2vAbcPlsyDzb06Ti59m4iQNS_TFmfwiMLu-uWFPKU@z> (raw)

>
>I did this for Inferno, which has a different graphics protocol but
>the same overall architecture, so it can be done.  I don't wish the
>job on anyone; it's a nasty mess to get two unrelated graphics models
>to function together.
>
Hi Rob,

Thanks for the quick and detailed insights.

Did your work make it into the Inferno distribution?
Have you any idea if the VNC model (http://www.orl.co.uk/vnc/)
is any more compatible with Plan9? I have used it to get
a Windows machine console in a window on my X-Terminal
(and vice versa), although performance does suffer when
using the Internet to access a remote machine in Sydney
when using a display in London...

Is the Inferno implementation an improvement, as in a re-design
incorportating lessons learnt from Plan 9, or is there some
sort of trade off whereby both have merits?

>I did it by..
>
You have convinced me that it isn't a good learners project :-)

>Getting all this to go fast involved much trickery and analysis of X
>internals.  The result is barely satisfactory.  Plus, a huge piece of
>the code deals with the psychotic pas de deux of allocating a screen
>and color map in X. When it came to 16-bit X screens, we cut bait; it
>wasn't worth any more time.
>
Mine is a 24-bit 1600x1200 NCD - hence my preference for it over
the SPARCstation 2 screen. It seemed preferable to share
one good display amoungst all of my machines, rather than trying
to equip then all with usable displays. Even if I could afford
the latter, I would have nowhere to put them all. Of course that
relies on everything supporting the same network graphics protocol,
which fortunately most do, with the exception of Windows (and who cares!)
and Plan 9 :-(.

>Similar games can be done on Windows, but it's much easier there, at
>least conceptually, because you can write code that runs on (in X
>terminology) the server and also just paint data on the screen, in
>other words, decode the Plan 9 protocol on the machine with the frame
>buffer.
>
Would it be more practical to play with the X server extensions
mechanism, to decode the Plan 9 protocol, the same way postscript
etc is added to some X servers?

Is the reverse easier to achieve - translating X protocol
into Plan 9 or Inferno protocol?

It would be nice if the Plan 9 and Inferno protocols could converge,
and perhaps gain a wider acceptance as an alternate protocol
for networking graphics.

Regards,
DigbyT
-- 
Digby R. S. Tarvin                                              digbyt@acm.org
http://www.cthulhu.dircon.co.uk




             reply	other threads:[~1998-08-25 17:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-25 17:03 Digby [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-09-06 16:50 miller
1998-08-26 17:49 Russ
1998-08-26  8:59 forsyth
1998-08-26  8:18 Elliott.Hughes
1998-08-25 19:30 Scott
1998-08-25 18:56 Digby
1998-08-25 17:48 rob
1998-08-25 16:13 rob
1998-08-25 14:24 Digby

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=19980825170331.gW2vAbcPlsyDzb06Ti59m4iQNS_TFmfwiMLu-uWFPKU@z \
    --to=9fans@9fans.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).