From: Skip Tavakkolian <skip.tavakkolian@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 10:27:40 -0700 [thread overview]
Message-ID: <CAJSxfmK0Kgb0FZo+kQAh6x-=dNeahQG0ido+oQ=XpsbQ83G=WQ@mail.gmail.com> (raw)
In-Reply-To: <CAOk9ws1n+8z5swbHOQco7QRJ-eu3pOk8Us6UOHcOieY+yJAQrg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1888 bytes --]
Improving or reimplementing it better are just as important as originality.
On Thu, Apr 18, 2019 at 9:51 AM Chris McGee <newton688@gmail.com> wrote:
> Thanks, this looks to be exactly what I was hoping to do. The idea wasn't
> as original as I thought.
>
> On Thu, Apr 18, 2019 at 11:27 AM Skip Tavakkolian <
> skip.tavakkolian@gmail.com> wrote:
>
>> This might be a good place to start:
>>
>> https://bitbucket.org/dhoskin/9webdraw/src/default/
>>
>> On Thu, Apr 18, 2019 at 7:36 AM Chris McGee <newton688@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> I'm looking at creating an alternate filesystem for /dev/draw,
>>> /dev/mouse and /dev/kbd that hooks up to a web server providing HTML
>>> interfaces (e.g. canvas) for Plan 9 UI. I've been reading over the manual
>>> pages, which are quite detailed, which is great, but there are some points
>>> of confusion for me.
>>>
>>> In particular, /dev/draw's interface and documentation keep referring to
>>> the concept of a "window" indirectly. It seems that in some cases the
>>> server providing /dev/draw needs to track windows and refresh them. But,
>>> what defines a window in this protocol? Is every image a window or only
>>> some of them?
>>>
>>> Also, I'm trying to understand how off-screen images, such as fonts are
>>> loaded. It seems that every image must be associated with a screen and be
>>> given a position within the screen. So, how do you prevent the image from
>>> being visible to the user?
>>>
>>> Hopefully, if I can understand some of the high-level concepts here then
>>> the manual page will be all that I need. Does anyone have experience with
>>> this area or could point me to information that might help clarify it?
>>>
>>> My next step will probably be to figure out how libmemdraw does all of
>>> this on top of a frame buffer.
>>>
>>> Thanks,
>>> Chris
>>>
>>
[-- Attachment #2: Type: text/html, Size: 2922 bytes --]
next prev parent reply other threads:[~2019-04-18 17:27 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 [this message]
2019-04-18 17:52 ` erik quanstrom
2019-04-18 19:03 ` Chris McGee
2019-04-18 19:30 ` Joseph Stewart
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='CAJSxfmK0Kgb0FZo+kQAh6x-=dNeahQG0ido+oQ=XpsbQ83G=WQ@mail.gmail.com' \
--to=skip.tavakkolian@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).