Changes between Version 14 and Version 15 of MapGuideRfc117

Timestamp:

Sep 7, 2011, 7:11:04 PM (13 years ago)

Author:

jng

Comment:

--

MapGuideRfc117

@@ -35 +35 @@
 > Although the current build is tightly bound to a server service, it would be useful to create a build profile (free of any server dependencies) that provided a desktop developer to quickly add spatial visualisation and interactivity to their application. 
 
-The web and server-centric nature of MapGuide means that it is currently not possible to have a '''truly disconnected''' desktop client mapping application. Under MapGuide 6.5, this was somewhat possible by using the technique of embedding the ActiveX viewer control and loading a MWF filled with static layer data. Under the current MapGuide, there is nothing that approaches this kind of setup in terms of installation and resource footprint. Currently, if you want to build a MapGuide "desktop" application, you '''have''' to have a MapGuide Server and Web Tier present on the desktop and incur the overhead of having both of these running at the same time. 
+The web and server-centric nature of MapGuide means that it is currently not possible to have a '''truly disconnected''' desktop client mapping application. Under MapGuide 6.5, this was somewhat possible by using the technique of embedding the ActiveX viewer control and loading a MWF filled with static layer data. If you wind the clock even further back, Autodesk had a specialized product for this purpose (Envision/OnSite Desktop) which has long since been discontinued.
+
+Under the current MapGuide, there is nothing that approaches this kind of setup in terms of installation and resource footprint. Currently, if you want to build a MapGuide "desktop" application, you '''have''' to have a MapGuide Server and Web Tier present on the desktop and incur the overhead of having both of these running at the same time. 
 
 Clayton Hotson's [http://au.autodesk.com/?nd=class&session_id=5241 AU 2009 Presentation] showed that it was indeed possible to utilize components of the MapGuide stack '''outside''' of the MapGuide Server to create applications that have no server or web tier dependencies (in the case of the AU presentation: A map renderer).
@@ -65 +67 @@
  * MgTileService
 
+Also included in mg-desktop, is a WinForms-based map viewer component library which has 80% of the functionality of the AJAX/Fusion viewer, which can be embedded in your own .net applications. The missing 20% is mainly support for tiled map layers and maps with dynamic/tiled layer combinations.
+
 In terms of implementation details:
 
@@ -145 +149 @@
 {{{
 
-class MgdFeatureService : public MgFeatureService
+class MG_DESKTOP_API MgdFeatureService : public MgFeatureService
 {
 ...
@@ -180 +184 @@
     // Deletes features from the specified feature class of the specified feature source with the specified filter using the specified transaction
     int DeleteFeatures(MgResourceIdentifier* resource, CREFSTRING className, CREFSTRING filter, MgTransaction* trans);
+};
+
+}}}
+
+=== MgdLayer ===
+
+Adds extra convenience methods for new APIs in MgdFeatureService
+
+{{{
+
+class MG_DESKTOP_API MgdLayer : public MgLayerBase
+{
+...
+
+PUBLISHED_API:
+    //Convenience form of MgFeatureService::BeginTransaction()
+    virtual MgTransaction* BeginTransaction();
+
+    //Convenience form of MgdFeatureService::SelectFeaturesExtended()
+    virtual MgdScrollableFeatureReader* SelectFeaturesExtended(MgFeatureQueryOptions* options);
+
+    //Convenience form of MgdFeatureService::InsertFeatures()
+    virtual MgFeatureReader* InsertFeatures(MgPropertyCollection* propertyValues);
+
+    //Convenience form of MgdFeatureService::UpdateFeatures()
+    virtual int UpdateFeatures(MgPropertyCollection* propertyValues, CREFSTRING filter);
+
+    //Convenience form of MgdFeatureService::DeleteFeatures()
+    virtual int DeleteFeatures(CREFSTRING filter);
+
+    //Convenience form of MgdFeatureService::InsertFeatures()
+    virtual MgFeatureReader* InsertFeatures(MgPropertyCollection* propertyValues, MgTransaction* trans);
+
+    //Convenience form of MgdFeatureService::UpdateFeatures()
+    virtual int UpdateFeatures(MgPropertyCollection* propertyValues, CREFSTRING filter, MgTransaction* trans);
+
+    //Convenience form of MgdFeatureService::DeleteFeatures()
+    virtual int DeleteFeatures(CREFSTRING filter, MgTransaction* trans);
 };
 
@@ -216 +258 @@
 
  * MgTransaction support
+ * Aliases
 
 In terms of compatibility, existing MapGuide application code is compatible at the source code level provided the code is targeting the subset of the MapGuide API that is supported and implemented by this desktop API. 
@@ -229 +272 @@
 It is planned, should this RFC be approved, to put the migrated source into a "Desktop" top-level directory under MgDev. This will have minimal impact on the rest of the source tree.
 
-Also if it hasn't been made clear already, this RFC only concerns the desktop API and not something like a desktop map viewer. The intention behind this RFC is to add the infrastructure to make it possible for such applications to be created. A desktop map viewer may exist in the future as a separate RFC.
-
 There are no plans to make this desktop API production ready for the 2.3 milestone. The scope of this RFC is to simply have the source of the desktop implementation integrated into the MapGuide source tree in a functional state by that stage. Unless there is interest from Autodesk, maintenance and enhancement of this codebase to keep up to date with future upstream platform and component changes will be a community responsibility