Re: [9fans] Understanding /dev/draw

Hi Chris, I hope it's a useful starting point for you. I'm definitely interested in seeing any changes you make, but it might make more sense for you to fork it. Good luck, -- David From: Chris McGee Subject: Re: [9fans] Understanding /dev/draw Date: Thu, 18 Apr 2019

Re: [9fans] Understanding /dev/draw

Thanks David, you have saved me a bunch of work. If I were to fix/extend the project would you be interested in the changes or should I just fork it? On Thu, Apr 18, 2019 at 4:37 PM David Hoskin wrote: > > Does anyone know if David is still active in this space? > > Hi Chris, > > I'm still

Re: [9fans] Understanding /dev/draw

hmm? what would you like, please tell us more On 4/19/19, Joseph Stewart wrote: > Skip/all: there's a lot I think about especially surrounding plan9 and > Inferno. Sadly little action results. > > On Thu, Apr 18, 2019 at 2:52 PM Skip Tavakkolian > > wrote: > >> Joseph, others, have you thought

Re: [9fans] Understanding /dev/draw

Skip/all: there's a lot I think about especially surrounding plan9 and Inferno. Sadly little action results. On Thu, Apr 18, 2019 at 2:52 PM Skip Tavakkolian wrote: > Joseph, others, have you thought about Dis-to-wasm JIT? I recall > Charles/Vita Nuova doing a browser plugin a few years ago,

Re: [9fans] Understanding /dev/draw

Joseph, others, have you thought about Dis-to-wasm JIT? I recall Charles/Vita Nuova doing a browser plugin a few years ago, but things could be a lot simpler now. HTML5 also has storage api's; a lot of local resources can be available via 9p/sytx (devdraw, fs, cons) On Thu, Apr 18, 2019 at

Re: [9fans] Understanding /dev/draw

> Does anyone know if David is still active in this space? Hi Chris, I'm still lurking the list, but I haven't touched this code in years. The basic drawing ops are alright but layers are maybe quarter baked. All of it is hacky student code written in a sort of lowest common denominator of

Re: [9fans] Understanding /dev/draw

I think the missing stuff is in libmemdraw.On Apr 18, 2019 12:03, Chris McGee 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

Re: [9fans] Understanding /dev/draw

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 wrote: > Hi All, > > I managed to get it running after all of these years. In case anyone tries > it

Re: [9fans] Understanding /dev/draw

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

Re: [9fans] Understanding /dev/draw

> 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 >

Re: [9fans] Understanding /dev/draw

this implementation is enough to run acme,but not a full p9 terminal.  you'll need layers for that.- erikOn Apr 18, 2019 10:27, Skip Tavakkolian wrote:Improving or reimplementing it better are just as important as originality.On Thu, Apr 18, 2019 at 9:51 AM Chris McGee

Re: [9fans] Understanding /dev/draw

Improving or reimplementing it better are just as important as originality. On Thu, Apr 18, 2019 at 9:51 AM Chris McGee 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 < >

Re: [9fans] Understanding /dev/draw

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.tavakkol...@gmail.com> wrote: > This might be a good place to start: > > https://bitbucket.org/dhoskin/9webdraw/src/default/ > > On Thu,

Re: [9fans] Understanding /dev/draw

I've been hoping someone would resurrect this project, especially given that Typescript and Go (wasm) are both much better options for implementing it. On Thu, Apr 18, 2019 at 8:25 AM Skip Tavakkolian wrote: > This might be a good place to start: > >

Re: [9fans] Understanding /dev/draw

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

Re: [9fans] Understanding /dev/draw

Whatever you do, do not start with Linux-type assumptions, or MIT-X assumptions. They will cripple your understanding. Everything is in the man pages, except the actual device driver, /dev/draw. VGA, if I understand your interest, you will be spared. I never quite understood everything involved

[9fans] Understanding /dev/draw

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