From: Shane S. <sha...@sw...> - 2006-01-31 20:27:09
|
On Mon, 2006-01-30 at 11:32 +0100, Jan Schmidt wrote: > On Mon, 2006-01-30 at 19:01 +1100, Shane Stephens wrote: > > Rock! > > > > That's great work, Jan; and I think that your GStreamer approach is a > > very nice idea for GLUT and GTK as well. Do you think we could also > > swing the build system so that if GStreamer isn't present then that > > submodule simply doesn't build? Likewise for GLUT, GTK, etc.? > > Yes - if GStreamer isn't present, it won't build the module. My main > concern to get right before turning GLUT and GTK into modules is > ensuring that symbol resolution works properly for these modules - that > Togra.gstutil can correctly use symbols from the Togra._togra .so file. That's a good point. Do you know yet if this works OK? > > I have the following things on my list of todos: > > (1) Get Operations working without leaks, and get a reasonable test demo > > running > > (2) Document Operations properly (what they are, how to use them, etc) > > on the Wiki > > (3) Start up a skeleton Togra Hacker's Guide for me to fill out with > > information about Togra2, so that other people can start to hack on it > > too. > > Cool. I'll be interested to find out what Operations are ;) They take in vector (or scalar, colour, transform, etc.) streams, and modify them on the way through. Useful for dynamic rendering, could possibly also replace Interpolated transforms. Eventually I'll build a mini-compiler in that converts them on construction to relatively well optimised C. > Do you know how to retrieve details about the display from GL, such as > the pixel-aspect? We'll need this in the RenderControl to set up the > global transform matrix correctly. Hrmm, not sure. I know you can get width and height easily (there's methods in the RenderControl). I'll look into the pixel-aspect issue though. > Cheers, > J. > -- Shane Stephens <sha...@sw...> |