>> Hi,
>> could we add as many as possible new interfaces from 2.0 to 1.8? For >> example the editXXX functions or the new field access methods for Ptr >> fields. It would be nice, if it is possible to compile an >> application with >> 1.8 and 2.0 with a view #ifdef OPENSG_20. >> >> We talked already about this, but I don't know, if the decission was >> already mad to do this. > > I would prefer doing it the other way (and that's the direction we'ce > been working in): add as many backwards-compatible things as > possible to > 2.x. There are some that won't work (interleaved multi-indexgeometry, > for example), but most old programs should work fine with 2. Well, some "old" programs are quite big and cannot ported easily to 2.0, especially since 2.0 is still a moving target. We cannot force the developer to use 2.0 right now. Some would like to use 2.0 as basis to try new things and some would like to stay with a stable version. I really would love to see some features in 1.8 (and 2.0) that helps us (and other OpenSG user) to keep the number of #ifdefs as low as possible. We really would like to keep a single branch that compiles on 1.8 and 2.0. Maybe we can introduce those extra functions after the 1.8 release. regards, johannes ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Opensg-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-core
