AnotherFoxGuy/polyvox
1
0
Fork 0
Code Issues Pull Requests Activity

Normalized line endings

Browse Source
This commit is contained in:
David Williams
2014-09-25 22:38:01 +02:00
parent c560e84be5
commit 86357d66b7
106 changed files with 50344 additions and 50344 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
documentation/principles.rst
View File

@ -1,14 +1,14 @@
**********************
Principles of PolyVox
**********************
.. warning ::
This section is being written and is just a skeleton for now
PolyVox provides a library for managing 3D arrays (volumes) of data (voxels). It gives you the tools to iterate through, randomly access, read and write volumes. It supports any type you'd like to represent each voxel whether it's just an ``int`` or a class which encapsulates both density and colour.
Once you have a volume, PolyVox provides a number of tools for turning it into something that you can pass to your rendering engine. These are called `surface extractors`.
Each surface extractor needs to be told how to interperet your voxel type and that is done using...
Link to a page describing how to write your own voxel type and link it to a surface extractor...
**********************
Principles of PolyVox
**********************
.. warning ::
This section is being written and is just a skeleton for now
PolyVox provides a library for managing 3D arrays (volumes) of data (voxels). It gives you the tools to iterate through, randomly access, read and write volumes. It supports any type you'd like to represent each voxel whether it's just an ``int`` or a class which encapsulates both density and colour.
Once you have a volume, PolyVox provides a number of tools for turning it into something that you can pass to your rendering engine. These are called `surface extractors`.
Each surface extractor needs to be told how to interperet your voxel type and that is done using...
Link to a page describing how to write your own voxel type and link it to a surface extractor...