Changes between Version 5 and Version 6 of MapGuideRfc48


Ignore:
Timestamp:
Apr 30, 2008, 12:32:10 AM (16 years ago)
Author:
ksgeograf
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc48

    v5 v6  
    6161We may require some assistance from the OSGeo SAC in bringing in the Google Code SVN, but if this is not available then the code can just be committed without history.
    6262
    63 !MapStudio relies on a custom .Net 1.1 API for !MapGuide that is included in the !MapStudio source tree.  This API will also need to be present in the Maestro source. It does not require endorsement by !MapGuide, but may prove usefull for .Net developers.  The API contains a native wrapper section that has a static patched (for .Net 1.1) copy of the Swig-generated !MapGuide managed API.  It may be desirable to have this code automatically created/patched from the current !MapGuide source at build time rather than storing the generated files in the repository, but this does not need to be done immediately. Alternatively the entire application may be upgraded to .Net 2.0, and then be able to use the managed API that is shipped with MapGuide.
     63!MapStudio relies on a custom .Net 1.1 API for !MapGuide that is included in the !MapStudio source tree.  This API will also need to be present in the Maestro source. It does not require endorsement by !MapGuide, but may prove usefull for .Net developers.  The API contains a native wrapper section that has a static patched (for .Net 1.1) copy of the Swig-generated !MapGuide managed API.  It may be desirable to have this code automatically created/patched from the current !MapGuide source at build time rather than storing the generated files in the repository, but this does not need to be done immediately. Alternatively the entire application may be upgraded to .Net 2.0, and then be able to use the managed API that is shipped with !MapGuide.
    6464
    6565It is intended that !MapStudio remain as a separate application from !MapGuide, with its own download packages and release cycle.  Existing tags in the repository already have a MAPGUIDE prefix, but we may need to either modify the existing branch names, or just ensure that !MapStudio uses a prefix for its branches.