Hello Michael,
On 10/12/2011 08:09 AM, Michael Raab wrote:
> 1.) Using OSGCOMPAT_ENABLE to accelerate porting from 1.8 to 2.0:
> Are there any drawbacks when using this flag or can it be used in general?
I can't think of any cases where it would cause problems, it mostly
enables some old function names that in general forward to the renamed
implementation.
> 2.) OSB file format compatibility:
> At the moment we have lots of scenes saved using the binary osb format. Will
> I be able to load these files directly into OpenSG2.0? If not, are there any
> convertion tools?
They should load without conversion.
> 3.) FieldContainer implementations:
> We have implementated several OpenSG classes on our own. What is the best way
> to move them from 1.8 to 2.0. Has the fcd file format been changed?
The .fcd file format has been extended, but not in an incompatible way,
so older .fcd files should still work. The *Base.{cpp,h,inl} files just
need to be regenerated, the other files that make up a FC need to be
ported by hand though.
Cheers,
Carsten
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
