From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: In-Reply-To: From: Chris McGee Date: Thu, 18 Apr 2019 11:33:15 -0400 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="000000000000239be00586cfb9ed" Subject: Re: [9fans] Understanding /dev/draw Topicbox-Message-UUID: fafe2608-ead9-11e9-9d60-3106f5b1d025 --000000000000239be00586cfb9ed Content-Type: text/plain; charset="UTF-8" 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 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 >> > --000000000000239be00586cfb9ed Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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 <s= kip.tavakkolian@gmail.com> wrote:
This might be a good place to sta= rt:


On Thu, Apr 18, 2019 at 7:36 AM Chris McGee <newton688@gmail.com&g= t; wrote:
Hi All,

I'm looking at creatin= g 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, whic= h is great, but there are some points of confusion for me.

In particular, /dev/draw's interface and documentation keep re= ferring to the concept of a "window" indirectly. It seems that in= some cases the server providing /dev/draw needs to track windows and refre= sh them. But, what defines a window in this protocol? Is every image a wind= ow or only some of them?

Also, I'm trying to u= nderstand how off-screen images, such as fonts are loaded. It seems that ev= ery image must be associated with a screen and be given a position within t= he screen. So, how do you prevent the image from being visible to the user?=

Hopefully, if I can understand some of the hi= gh-level concepts here then the manual page will be all that I need. Does a= nyone 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.<= br>

Thanks,
Chris
--000000000000239be00586cfb9ed--