From: Francisco J Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] html5 canvas, go, devdraw
Date: Sat, 7 Sep 2013 18:24:44 +0200 [thread overview]
Message-ID: <A26CCB50-03BA-4852-9E2C-21D58ED5B6C8@lsub.org> (raw)
In-Reply-To: <20130907160522.GB4768@iota.offblast.org>
that's nice, thanks.
I was thinking on using a more abstract interface because, for example,
the canvas has everything needed to provide text frames for something like
acme, and you could write it in go and then make it something that could be
interfaced to programs running on 9.
But a raw 9p devdraw looks cool.
I will take a look.
thanks again.
On Sep 7, 2013, at 6:05 PM, Nick Owens <mischief@9.offblast.org> wrote:
> On Sat, Sep 07, 2013 at 05:48:18PM +0200, Francisco J Ballesteros wrote:
> there has been some work on this here. unfortunately not all devdraw
> messages are implemented, so graphics does not fully work.
>
> https://github.com/aiju/jsdrawterm
>
> i run a copy on http://9.offblast.org/
>
> nick
>
>> Hi,
>>
>> I'm playing a bit with the html5 canvas, js, and go servers, and I'm
>> thinking it would be quite easy to build a devdraw server (an omero like
>> server would be even easier) so that you only have to run your go program
>> and it would open a browser as your devdraw device.
>>
>> Just wondering, anyone playing with such a beast?
>>
>> cheers
>>
>>
next prev parent reply other threads:[~2013-09-07 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 15:48 Francisco J Ballesteros
2013-09-07 15:54 ` lucio
2013-09-07 15:57 ` Nemo
2013-09-07 16:48 ` lucio
2013-09-07 16:05 ` Nick Owens
2013-09-07 16:24 ` Francisco J Ballesteros [this message]
2013-09-07 16:19 ` erik quanstrom
2013-09-07 16:24 ` Anthony Sorace
2013-09-07 16:40 ` Francisco J Ballesteros
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=A26CCB50-03BA-4852-9E2C-21D58ED5B6C8@lsub.org \
--to=nemo@lsub.org \
--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).