Changes between Version 4 and Version 5 of MapGuideRfc48
- Timestamp:
- Apr 30, 2008, 12:31:50 AM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MapGuideRfc48
v4 v5 9 9 ||RFC Template Version||(1.0)|| 10 10 ||Submission Date|| April 20, 2008 || 11 ||Last Modified|| Jason Birch - 2008-04-2 5 08:27 PDT ||11 ||Last Modified|| Jason Birch - 2008-04-29 09:30 CET || 12 12 ||Author||Jason Birch|| 13 ||Author||Kenneth Skovhede|| 13 14 ||RFC Status||draft || 14 15 ||Implementation Status||not started|| … … 33 34 == Proposed Solution == 34 35 36 * Re-brand MapStudio to "MapGuide Maestro" to avoid confusion with Autodesk !MapGuide Studio and !WebStudio 35 37 * Migrate SVN repository from Google Code to the OSGeo !MapGuide SVN 36 38 * Set up a new Component in !MapGuide Trac for !MapStudio Open Source … … 45 47 Into the following location: 46 48 47 http://svn.osgeo.org/mapguide/trunk/Tools/Ma pStudioOS/49 http://svn.osgeo.org/mapguide/trunk/Tools/Maestro/ 48 50 49 Alternately, if an alternate name for the API can be found, MapStudio and the API could be located directly under Tools.51 The API is currently named MapGuideAPI, which may cause confusion, since it is not an official API. The API will be renamed to MaestroAPI before import. 50 52 51 53 == Implications == 52 54 53 This will require that Kenneth sign a contributor agreement, and either certify that all of the work is owned by him (done on his own time) or obtain a contributor agreement from his employer.55 This will require that Kenneth sign a contributor agreement, and certify that all of the work is owned by him. 54 56 55 57 It would be desirable for someone to do a provenance review on the code. … … 59 61 We 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. 60 62 61 !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 "adopted" by !MapGuide. 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.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. 62 64 63 65 It 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.
