Text archives Help
- From: Rocky Rhodes <rhodes@sgi.com>
- To: "'Abe Stephens'" <abe@sci.utah.edu>, "'manta@sci.utah.edu'" <manta@sci.utah.edu>
- Subject: RE: [MANTA] Need to decide what to do on user interface.
- Date: Fri, 27 May 2005 12:29:20 -0700
It will be worthwhile to insure that Manta is embeddable into an
application, even if the scriptable GUI is the route of choice for quick,
new interfaces.
Rocky
-----Original Message-----
From: owner-manta@sci.utah.edu [
mailto:owner-manta@sci.utah.edu] On Behalf
Of Abe Stephens
Sent: Friday, May 27, 2005 11:41 AM
To: 'manta@sci.utah.edu'
Subject: [MANTA] Need to decide what to do on user interface.
We need to reach a consensus on how we are going to do user interfaces
with Manta.
I think we are about to reach a point where we will be less productive
without a user interface. Kenny Hoff here at sgi is working on
integrating sophisticated mouse navigation system but we also need
configuration windows, drop down menus, sliders etc. We've talked about
some pretty cool demo ideas, but none of them are going to work without
a gui.
It seems to me that the scripting interface is a very powerful idea,
although it doesn't sound like it is the sort of thing that could be
assembled in the short span of time. I'm also unsure how a python demo
script would interact with other parts of a demo besides driving Manta.
For example how would you fit a C++ cad part database component into a
python driven demo? (Would you just write it in C++ for performance and
then swig it?) How would a 2D simian like transfer function widget work
in the python scripting environment?
If it is too complicated to quickly add a scripting gui interface to
Manta, should we focus on making Manta embeddable and then just place it
inside of a demo application?
Abe
Archive powered by MHonArc 2.6.16.