Robert,
Thanks for the update. No matter how it's implemented internally, there is
still a need for my clients to not have to hack a command line or a text/xml
file. They are not programmers (they don't even use Windows's
CommandPrompt). When VPB is up and running, I'll just update the back-end to
reflect that.
XML is great way to save parameters in a cross-platform fashion.
- Nick -
From: "Robert Osfield" <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: [osg-users] osgDem Windows Front-End
Date: Sat, 18 Aug 2007 16:54:23 +0100
FYI, I am currently changing the way that VTPB defines its source and
destination graphs. The source data is based on the
osgTerrain::Terrain/Layer classes and serialization. The destination
graph is not yet set but right now looks most likely to reuse PagedLOD
directly. The serialization will be supported by both .osg and .ive.
With the new work there will be several apps that can be run to
process chunks for the serialized destination graph. These will be
able to run multi-threaded as well as distributed across the network.
These apps will be nature be command line driven.
Defining the source data could be defined in an xml format, although
it won't really get you much over the .osg based source graph
serialization Follows is a current example:
osgTerrain::Terrain
{
name "puget sound"
ElevationLayer
{
CartesianLocator 0 0 1000000 1000000
Image ps_height_512.tif
}
ColorLayer
{
CartesianLocator 0 0 1000000 1000000
Images
{
ps_height_512.tif
ps_texture_1k.tif
}
}
}
I haven't modified osgdem to use the above as an input file format,
but this should be possible - one just loads the source data and then
traverse the loaded scene graph for its Terrain nodes, this could then
help build the old style source graph.
osgdem itself will stay largely untouched while I rewrite VPB, all the
new features will grow alongside it, and when they are ready and well
tested it should be possible to just drop osgdem.
In my planed work I don't have a GUI front end planned, exactly what a
GUI might need to encompass will depend upon how the final low level
code/apps work. Note that my VPB work will deliver have a system that
can do incremental and distributed builds, something osgdem can't do -
it just has to everything in a one pass.
The VPB work does mean that I can't recommend investing much effort
into osgdem. If you can spend a day mocking up a front end then fine,
but do expect it to be replaced within the next six months by
something that is quite different in the way it works.
Robert.
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
_________________________________________________________________
Former Police Officer Paul Gillespies TAKE BACK THE INTERNET tips and
tricks, watch the video now http://safety.sympatico.msn.ca/
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
