9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Vector graphics device
Date: Sun, 21 Feb 2010 19:15:17 +0000	[thread overview]
Message-ID: <62CE37A9-6C0A-4114-9E23-60D97630B644@fastmail.fm> (raw)
In-Reply-To: <48ff49f6665b00f0d9ef428a3017f681@coraid.com>


On 19 Feb 2010, at 21:58, erik quanstrom wrote:

>> In this model the client doesnt actually draw an image, but just
>> operates on an (changeable) vector graphic. Things like scaling,
>> resizing (even funny effects like deformed windows while moving)
>> all are done by the display server - the client just sees object
>> vectors in an continous 2D space.
>
> that model expired in the 60s.
>
> if you want to support scaling, you'll likely need to support
> something
> more complicated than vectors.  (vectors scale trivially.)
>
> once you branch beyond vectors, life gets a bit complicated.
> and generally one jumps immediately to 3d.

I have some ideas for a 3D draw device where the client may build and
work with a tree of 2D and 3D objects. The plan was to make
"deepterm", a drop-in replacement for drawterm with additional
capability implemented with aid of the host's OpenGL. Beyond that my
ideas are fairly vague. I was hoping to work them out as I developed a
proof-of-concept server, but the project has been on ice for a couple
of months and I barely remember what I was doing.



  reply	other threads:[~2010-02-21 19:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 16:35 Enrico Weigelt
2010-02-18 21:16 ` James Tomaschke
2010-02-19 21:36   ` Enrico Weigelt
2010-02-19 21:58     ` erik quanstrom
2010-02-21 19:15       ` Ethan Grammatikidis [this message]
2010-02-20  4:01     ` Patrick Kelly

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=62CE37A9-6C0A-4114-9E23-60D97630B644@fastmail.fm \
    --to=eekee57@fastmail.fm \
    --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).