From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] nix at lsub
Date: Thu, 19 Apr 2012 03:03:02 -0700 [thread overview]
Message-ID: <B2B010DD-7FE2-432A-8259-9BFC1C28E3BB@bitblocks.com> (raw)
In-Reply-To: <CAOw7k5gX=L4kywDTjgkDbOpLXBAQK6ywxBfzfmdPftj9TX2D4w@mail.gmail.com>
On Apr 19, 2012, at 1:46 AM, Charles Forsyth <charles.forsyth@gmail.com> wrote:
> "But wait!", I hear you cry. State, callbacks, no data structures to
> speak of, ... why don't we look
> at how they handle this stuff in ... Haskell! (Monads, and a learning
> curve, though you can then build
> up something that's not entirely graphics machine code.)
It is a big state machine because you have to give it a lot of state & the 3D h/w does do a lot of complicated things! SGI had open inventor, a scene graph level C++ API but it didn't really go anywhere it seems.
But I think openGL 3.0+ and openGL ES 2.0 with their programmable pipeline can map well to a fileserver, where you write your data to the openGL server and the GPU does all the heavy lifting. This can also work reasonably well where the 3D h/w is a few tens of microseconds away from your cpu. I have a partial paper design but long way to go. A prototype is needed to see how well this will perform. An openInventor/coin3D/ivy (in scheme) kind of GUI library can be build on top of that.
next prev parent reply other threads:[~2012-04-19 10:03 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 18:05 arnold
2012-04-19 1:37 ` hiro
2012-04-19 4:15 ` Jeff Sickel
2012-04-19 8:10 ` Charles Forsyth
2012-04-19 8:16 ` Joseph Stewart
2012-04-19 8:46 ` Charles Forsyth
2012-04-19 10:03 ` Bakul Shah [this message]
2012-04-19 10:32 ` Charles Forsyth
2012-04-19 16:36 ` Bakul Shah
2012-04-19 15:50 ` ComeauAt9Fans@gmail.com
2012-04-19 16:11 ` Lucio De Re
2012-04-19 17:09 ` ComeauAt9Fans@gmail.com
2012-04-19 17:56 ` Lucio De Re
2012-04-19 18:05 ` Comeau At9Fans
2012-04-19 18:23 ` Lucio De Re
2012-04-19 18:27 ` Lucio De Re
-- strict thread matches above, loose matches on Subject: below --
2012-04-18 16:09 arnold
2012-04-18 16:18 ` Nemo
2012-04-18 16:28 ` Charles Forsyth
2012-04-18 16:35 ` Francisco J Ballesteros
2012-04-18 17:43 ` Lucio De Re
2012-04-18 15:45 arnold
2012-04-18 15:49 ` Francisco J Ballesteros
2012-04-14 21:02 Nemo
2012-04-15 13:45 ` David Leimbach
2012-04-16 10:47 ` Francisco J Ballesteros
2012-04-16 11:02 ` Noah Evans
2012-04-16 17:23 ` Aram Hăvărneanu
2012-04-16 17:32 ` Noah Evans
2012-04-16 17:42 ` Noah Evans
2012-04-16 17:44 ` ron minnich
2012-04-16 20:53 ` Andrés Domínguez
[not found] ` <CAEAzY380ECzLQJCbNaK=QiYE6vzQpqTW3ZoakzW7EJ-WajptHg@mail.gmail.c>
2012-04-16 17:54 ` sl
2012-04-16 13:22 ` Christoph Lohmann
2012-04-16 18:04 ` Lucio De Re
2012-04-17 2:16 ` kokamoto
2012-04-17 5:53 ` andy zerger
2012-04-17 5:54 ` andy zerger
2012-04-17 7:17 ` Nemo
2012-04-17 8:41 ` kokamoto
2012-04-17 8:51 ` Francisco J Ballesteros
2012-04-17 12:22 ` Tristan
2012-04-17 18:56 ` Charles Forsyth
2012-04-17 19:13 ` Nemo
[not found] ` <charles.forsyth@gmail.com>
2012-04-18 0:26 ` kokamoto
2012-04-18 4:07 ` John Floren
2012-04-18 4:12 ` John Floren
2012-04-18 7:54 ` Francisco J Ballesteros
2012-04-18 12:27 ` Charles Forsyth
2012-04-18 12:35 ` 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=B2B010DD-7FE2-432A-8259-9BFC1C28E3BB@bitblocks.com \
--to=bakul@bitblocks.com \
--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).