Thanks Robert
I thought there wasn't a list but worth asking anyway before I jump in.
Alan
Robert Osfield wrote:
Hi Alan,
On 12/12/06, Alan Harris <[EMAIL PROTECTED]> wrote:
I have not been able to find one, but is there a list of critical
changes in osg as it moved from 1.0 to 1.1 to 1.2.?
By critical changes I mean ones that will break an application unless
application modifications are made.
I'm afraid I haven't tracked API breaking changes. It would be nice
to have this going forward, but the way the OSG is developed in small
incremental steps its difficult to catch every little change that
might break things. I do try to highlight major changes in the NEWS
files, and do notify the list of changes as they happen, but this
won't be sufficient to catch all changes.
I wonder if an automated analysis osgIntrospection generated wrappers
might be a way of tracking API changes. One could take a snapshot of
the classes, methods and member varaibles for one release and then
compare it against another. This would have to be done through some
serialization out of the class definiations and require a 3rd part
tool then to do the diff analysis so its not a trivial job, it would
be very cool though :-)
Right now the best I can recommend is try it out and see how you get
on. In general the vast majority of the OSG API stays the same
between releases, with only certain classes changing, if you don't use
these classes then things will just compile, if you do use them then
will need to amend. Functionality typically just morphs so it should
be just a case of tweaking the affected parts rather than required
major rewrites.
By updating to the new releases with small increments you can minimize
the number of breaking changes, by using the CVS version you reduce
the number of breaking changes you are exposed to at any one time even
further. Tracking changes closely also keeps things relevant to
discussions that are happening on the osg-users mailing list - so
others will be discussing these changes too. If you wait a six months
or a year to upgrade then you'll miss these discussions as well as
have more changes to account for.
I'd recommend just trying new releases out, and pinging the list if
you come across problems, most should be resolvable pretty quickly.
Robert.
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
