Hi,
The editor was simply written as a test of some features for Thermite. As features have been added to Thermite I've changed what Thermite actually does so as to demonstrate those features. First I added the physics support and then made Thermite load the castle/rigid bodies to demonstrate that, and then I took out the ridid bodies demo and turned it into a terrain editor instead. Now things have evolved, and it loads and executes JavaScript files on startup to define application specific behaviour.
In other words, the terrain editor doesn't exist as a stand alone program, it's simply the state Thermite was in about a year ago.
Of course, all the code is still there behind the scenes, it's just that I've taken out the user interface. So you can look at the Thermite code to find the information you are looking for. Have a look for two functions called 'buildRenderOperationFrom' which take PolyVox meshes and put the data into Ogre hardware buffers. The simpler version is for the cubic terrain (like Minecraft) where as the more complex version is for the Marching Cubes terrain (which you want).
Note that the main reason the Marching Cubes terrain version is more complex is that it performs some rather fiddely duplication of triangles as it copies the data across. This is so that triangles with multiple materials get rendered several times, once for each material. This is a more advanced trick and you don't need to bother with it initially.
You may find an easier approach is to use the Ogre ManualObject class (at least initially). Be sure to check out the PolyVox BasicExample as this demonstrates extracting data and rendering with OpenGL. Porting to Ogre::ManualObject should be quite straight forward. Also read the tutorial here:
http://www.thermite3d.org/joomla/index.php?option=com_wrapper&view=wrapper&Itemid=32
Code is very slightly out of date but you should be able to work it out if you look at the BasicExample at the same time.
Just ask if you have more questions
