Manta Interactive Ray Tracer Development Mailing List

Text archives Help


Re: [MANTA] Trolltech Qt Open Source Edition


Chronological Thread 
  • From: Solomon Boulos <boulos@cs.utah.edu>
  • To: "Steven G. Parker" <sparker@cs.utah.edu>
  • Cc: James Bigler <bigler@cs.utah.edu>, manta@sci.utah.edu
  • Subject: Re: [MANTA] Trolltech Qt Open Source Edition
  • Date: Tue, 17 May 2005 14:19:10 -0400
I agree with keeping UI (not rendering) separate from the rendering code. I'd also agree that it's nice to have the renderer know as little as possible about the UI that might be hooked up to it -- although for my own UI, I chose to have the renderer at least send updates to the UI instead of using a peek system on the UI side to realize that the renderer has completed more work for the simple performance reasons.

Still, however, I don't see how code separation requires or suggests using a scripting language such as python. I agree that the UI and renderer communication should be minimal (but enough to get the job done) and that the UI code should only send commands to the renderer.

I guess I just don't understand what a "scriptable UI" really means. Is there a scripting console that you have when Manta starts and you can create yourself a new widget to help you interact with the renderer? Or am I still missing the underlying idea...

Solomon

On May 17, 2005, at 2:07 PM, Steven G. Parker wrote:

I wanted to keep the UI code out of the renderer (to the extent possible) so that it can be embedded in a library or used with different user interfaces (perhaps a custom interface).

Steve

On May 17, 2005, at 11:23 AM, Solomon Boulos wrote:


As long as Steve is defending a particular scripting language, I don't think I personally ever got a good feel for why the Manta UI would be scriptable. I understand sending commands to a renderer, and having those commands create helpful user interfaces (for example, when viewing an isosurface having a little widget to help you pick a particular isosurface value) is an obvious benefit, but nothing I've described so far requires a scripting language to actually generate user interfaces. Would anyone care to clear up my confusion?


On May 17, 2005, at 12:58 PM, James Bigler wrote:



without forcing the license upon the linked project. I would consider
Fox more if it had a maintained python binding.  The person who
maintained that bit of code is concentrating on Fox for Ruby. With



Have you guys decided on python rather than ruby for a scripting language?




Steve will have to defend himself on this one. It's mostly his decision.

James












Archive powered by MHonArc 2.6.16.

Top of page