Changes between Version 6 and Version 7 of MapGuideRfc9


Ignore:
Timestamp:
Feb 12, 2007, 12:15:50 PM (17 years ago)
Author:
robertbray
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc9

    v6 v7  
    160160== Implications ==
    161161
    162 Because these are additions to the API no compatibility issues exist. However in order to take advantage of the new methods users will need to call the new !MgMap constructor. If they do not the new methods will throw an exception.
     162Because these are additions to the API no compatibility issues exist. However in order to take advantage of the new methods users will need to call the new !MgMap constructor. If they do not the new methods will throw an exception. To further direct developers to these new methods the following !MgMap methods will be depreciated:
     163
     164{{{
     165MgMap();
     166
     167virtual void Create(MgResourceService* resourceService, MgResourceIdentifier* mapDefinition, CREFSTRING mapName);
     168
     169virtual void Open(MgResourceService* resourceService, CREFSTRING mapName);
     170}}}
     171
     172Note that depreciation means that these methods will still exist and function as before, but the documentation will be updated to declare them as depreciated and point to the new/appropriate methods to use.
    163173
    164174== Test Plan ==
    165175
    166 API Unit Tests will be added to test the new !MgLayerBase methods.
     176API Unit Tests will be added to test the new !MgMap and !MgLayerBase methods.
    167177
    168178== Funding/Resources ==