9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Colors and other fun
Date: Mon,  2 Jul 2007 08:55:17 +0000	[thread overview]
Message-ID: <lsudnXWrcvneMRjbnZ2dnUVZ_o2vnZ2d@comcast.com> (raw)
In-Reply-To: <20070627190951.73A8B5B3B@mail.bitblocks.com>

"Bakul Shah" <bakul+plan9@bitblocks.com> wrote in message 
news:20070627190951.73A8B5B3B@mail.bitblocks.com...
> I am not sure what I mean :-)  Guess some sort of 3D UI.  A
> way to deal with 3d objects.  ...

You need to distinguish between a genuine 3D display, which is extremely 
rare,
a stereoscopic display, which is not as rare (I have played Tomb Raider on a 
PC in stereo),
and a 3D *model* rendered in 2D, which is pretty common these days.

3D rendering is computationally intensive, and in modern times it is usually
done by sending the model to a so-called 3D graphics card along with
lighting and viewing parameters; updating just the viewing parameters
is sufficient to view a static model from all aspects.  For 3D games a
lot of compromises are made in order to be able to supply new model
information at a good frame rate as the modeled objects move in real time.

You might look into free 3D rendering software such as the POV ray-tracer
or the BRL-CAD package (on SourceForge I believe), which I contributed
to in its early days.  These provide modeling and viewing tools, and in the
case of BRL-CAD there are programming library facilities for interrogating
the model geometry, for applications like ballistic vulnerability studies.
*Maybe* these could be ported to Plan 9; I suspect APE would be helpful.
If there is an X-Windows server for Plan 9 it might not be too hard.


  parent reply	other threads:[~2007-07-02  8:55 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27  9:37 pavlovetsky
2007-06-27 10:08 ` Lucio De Re
2007-06-27 15:07   ` Rob Pike
2007-06-27 18:26     ` Bakul Shah
2007-06-27 18:35       ` Kris Maglione
2007-06-27 19:09         ` Bakul Shah
2007-06-27 19:24           ` David Leimbach
2007-06-27 19:39             ` Gabriel Diaz
2007-06-27 20:35               ` Bakul Shah
2007-06-27 21:20                 ` Jack Johnson
2007-06-29  2:16                   ` Bakul Shah
2007-06-27 19:51             ` Francisco J Ballesteros
2007-06-27 21:49               ` Jack Johnson
2007-07-02  8:55           ` Douglas A. Gwyn [this message]
2007-06-28  4:42     ` Anant Narayanan
2007-06-28  4:50       ` andrey mirtchovski
2007-06-28 17:30     ` Dave Eckhardt
2007-06-27 15:59 ` andrey mirtchovski
2007-06-27 16:23   ` Lorenzo Fernando Bivens de la Fuente
2007-06-27 17:55     ` Steve Simon
2007-06-27 18:03       ` erik quanstrom
2007-06-27 18:22         ` Rob Pike
2007-06-28 15:26         ` Steve Simon
2007-06-27 18:03       ` Kris Maglione
2007-06-27 18:59 Russ Cox
2007-06-27 19:13 ` Tim Wiess
2007-06-27 21:25 ` Charles Forsyth
2007-06-27 15:41   ` john
2007-06-27 21:56     ` erik quanstrom
2007-06-27 16:18       ` john
2007-06-27 22:06       ` Kris Maglione
2007-06-27 21:48 ` Markus Sonderegger

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=lsudnXWrcvneMRjbnZ2dnUVZ_o2vnZ2d@comcast.com \
    --to=dagwyn@null.net \
    --cc=9fans@cse.psu.edu \
    /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).