9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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:40:03 +0200	[thread overview]
Message-ID: <525C5686-15FC-4121-BF34-84CFB9C6D654@lsub.org> (raw)
In-Reply-To: <574BAE0B-71B2-4C65-B0D9-9D7C89BA5664@9srv.net>

I will, thanks to all of you for your replies.

Yes, I think that provided what canvas can do, doing something like
an omero viewer should be both fast to write and efficient when running.

Now that I see that drawterms are around the corner, perhaps here already,
I will play with more omero like interfaces.

On Sep 7, 2013, at 6:24 PM, Anthony Sorace <a@9srv.net> wrote:

> You may be interested in what David Hoskin is doing for one of our
> GSoC projects:
>    https://bitbucket.org/dhoskin/9webdraw
> He's been producing weekly status updates, which you can follow
> along with over on the plan9-gsoc google group:
>     http://groups.google.com/group/plan9-gsoc
> It's not done, but he's gotten promising results and is still working on
> it. Check it out.
>
> It'd be interesting to see how simply something for Omero could be
> done, bypassing draw entirely. I really like the model you came up
> with there, and wish there was more diversity in implementations.
>
> Anthony
>



      reply	other threads:[~2013-09-07 16:40 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
2013-09-07 16:19 ` erik quanstrom
2013-09-07 16:24 ` Anthony Sorace
2013-09-07 16:40   ` Francisco J Ballesteros [this message]

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=525C5686-15FC-4121-BF34-84CFB9C6D654@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).