Me: >6. We will stay in sync with the latest fltk1.3.x svn code as long as our >patches are being integrated. We simply >don't have the bandwidth to engage >in a cycle of re-applying/updating patches to stay in sync.
If we were to consider the initial integration to the fltk-1.3.x code base as being purely for development purposes, there would be no need to stay in sync. The actual final integration could occur as a separate task after the FLA wrapper API has been stabilized. This would eliminate all of the code flux prior to that point. It would also allow us to work somewhat independently until we had a final API spec. to present to the FLTK team. If the wrapper API is done right, it shouldn't matter what changes have occurred in the fltk-1.3.x code base between now and then. If a problem were to come up during the integration process, it would almost certainly be the result of an FLA design flaw. This is a much better approach. It keeps the noise level to a minimum until we actually have something more concrete to review/discuss. It also delays the FLTK code changes until they can be made against a working FLA library. Thanks, Gerry _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
