From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Colors and other fun
Date: Wed, 27 Jun 2007 13:35:08 -0700 [thread overview]
Message-ID: <20070627203508.3DA905B3B@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Wed, 27 Jun 2007 21:39:55 +0200." <82c890d00706271239k10113e4er89c1572d042781ac@mail.gmail.com>
> i see the point of 3d when doing tools for visualizing representation
> of things that should be moved live like a car model, or a building
> plant or quake. May be he is speaking about this? something like
> opengl or directx :-?
Consider for example google earth or a CAD program -- if you
ever played with revit you'd realize just how clunky Autocad
is. Consider 3d video games. Consider something like a
flight simulator -- all the one I played with were very
clunky to interact with. Can we do something to make it easy
to visualize complex information in a virtual 3d space and
navigate around it or modify it? Can there be an interface
for a sculptor to model something he wishes to build? Why
must such things be separate "applications"? Why can't we
just treat each "window" as a piece of paper and shuffle it
around, bend a corner, crumple it up, stretch it out, do some
origami with?
Take my question in whichever direction you want.
Some times misunderstanding leads to invention!
> > What's more usable about 3d than 2d for a GUI desktop?
Turn your question around. If you had a 3d UI what useful
(or playful) things can you do that you can't do today? If
you come up with something you'd want to do, what else can be
added/changed/removed to make the UI simpler and more useful?
> > I use Acme on Mac OS X as my main editor for most things these days
> > actually. The only things I really miss are when I'm editing scheme or lis
> p
> > and need to match up all those damned parenthesis. In those cases I use
> > Emacs... it's just better at it (and no stopping to click to highlight
> > open/close parens doesn't do it for me as much as automatic code indentatio
> n
> > based on syntax gets me)
Do you write any haskell/python in acme?
If the editor showed each s-expr at a different height &
color and if you could look at your program from a 45 angle,
you'd see what's what :-)
next prev parent reply other threads:[~2007-06-27 20:35 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 [this message]
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
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=20070627203508.3DA905B3B@mail.bitblocks.com \
--to=bakul+plan9@bitblocks.com \
--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).