Manta Interactive Ray Tracer Development Mailing List

Text archives Help


Re: [MANTA] where to put OctreeVolume.h?


Chronological Thread 
  • From: "Steven G. Parker" <sparker@cs.utah.edu>
  • To: Aaron Knoll <knolla@cs.utah.edu>
  • Cc: Abe Stephens <abe@sci.utah.edu>, manta@sci.utah.edu
  • Subject: Re: [MANTA] where to put OctreeVolume.h?
  • Date: Fri, 12 May 2006 11:19:36 -0600
Basic data structures probably belong in Core somewhere. However, it might make sense to just put it in scene (or make a subdir of scene) and move it to someplace once the picture is more clear and the boundaries are more defined. For example, things in Core shouldn't refer to the intersection or volume rendering code - they should just be basic data structures.

Thanks for trying to be careful about it :)

Steve


On May 12, 2006, at 11:14 AM, Aaron Knoll wrote:

Done.

I'm just trying to figure out the software convention in general. Ultimately, some form of volume rendering will probably come compiled standard in Manta, and I don't want my weird octree- isosurface implementation to deviate too much :)

Thanks,

-Aaron

On May 12, 2006, at 2:26 AM, Abe Stephens wrote:

The location that you place the code isn't as important as being sure that its compilation can be turned on and off in cmake.

I've placed most of my application specific code in fox/ <name>_demo. (take a look at fox/disco_demo for example) Usually there is a fox gui interface created for these scenes, but it isn't necessary. Actually if you create a directory under fox/ with the name formatted as <name>_demo the CMakeLists file will automatically include it. This allows you to stay current with the trunk without necessarily committing every project in a sub directory before updating that part of the tree.

Abe

Aaron Knoll wrote:

So I have this class for the octree volume data itself. It contains only the structure for the volume data; no routines for traversal or knowledge of the scene.

Where should I put that? I was thinking of Model/Primitives but that's not quite right...

The closest analogy to anything in the existing system is Array3.

Thanks -

Aaron

P.S. none of this will be committed until it's all working - feel free to code-review me too.








Archive powered by MHonArc 2.6.16.

Top of page