9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Joseph Stewart <joseph.stewart@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Understanding /dev/draw
Date: Thu, 18 Apr 2019 12:30:09 -0700	[thread overview]
Message-ID: <CANGQBe5+T2essJ1p3-iqdwTe8udY_q-nH9na-0TyBMo3T9aJTw@mail.gmail.com> (raw)
In-Reply-To: <CAOk9ws1LivgZf_k5vruwLFybK+URddygKB=egCBCy+koFZbFUw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]

I'm greedily watching this space... if you need testers, please let me
know. I have an interest in how/if this could be applied to Inferno was
well.

On Thu, Apr 18, 2019 at 12:05 PM Chris McGee <newton688@gmail.com> wrote:

> Hi All,
>
> I managed to get it running after all of these years. In case anyone tries
> it again here's a few things that I had to do to get it to work on the
> latest 9front.
>
> * Copy the latin1.h header file from the bell labs distribution and copy
> it into /sys/src/9/port
> * Run ip/httpd/httpd -w /sys/web/9wd (this is where the installation
> copies the web app)
> * Patch /usr/web/9wd/js/draw/data.js by commenting out the "delete
> conn.imgs[id];" line
>     * Future draw commands come in referring to the old image for some
> reason and the server doesn't handle it well
>
> Yes, when I coerce the websocket tool to launch rio instead of acme
> there's some oddness when I launch new graphical apps within rio from the
> windows, such as acme. They tend to think that they should occupy the
> entire screen. Also, be patient because it is quite slow for now.
>
> Does anyone know if David is still active in this space?
>
> Erik, where can I learn more about the layers?
>
> Thanks,
> Chris
>
> On Thu, Apr 18, 2019 at 2:08 PM erik quanstrom <quanstro@quanstro.net>
> wrote:
>
>> this implementation is enough to run acme,but not a full p9 terminal.
>> you'll need layers for that.
>>
>

[-- Attachment #2: Type: text/html, Size: 2292 bytes --]

  reply	other threads:[~2019-04-18 19:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18 14:35 Chris McGee
2019-04-18 15:01 ` Lucio De Re
2019-04-18 15:25 ` Skip Tavakkolian
2019-04-18 15:30   ` Skip Tavakkolian
2019-04-18 15:33   ` Chris McGee
2019-04-18 17:27     ` Skip Tavakkolian
2019-04-18 17:52       ` erik quanstrom
2019-04-18 19:03         ` Chris McGee
2019-04-18 19:30           ` Joseph Stewart [this message]
2019-04-18 20:40             ` Skip Tavakkolian
2019-04-18 22:28               ` Joseph Stewart
2019-04-18 22:33                 ` hiro
2019-04-18 19:33           ` erik quanstrom
2019-04-18 20:37           ` David Hoskin
2019-04-19  0:22             ` Chris McGee
2019-04-19  1:26               ` David Hoskin
2019-04-18 18:12 ` hiro

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=CANGQBe5+T2essJ1p3-iqdwTe8udY_q-nH9na-0TyBMo3T9aJTw@mail.gmail.com \
    --to=joseph.stewart@gmail.com \
    --cc=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).