[mapguide-internals] Refactoring Web .NET API into Common DLLs is ready for review.

Jackie Ng jumpinjackie at gmail.com
Thu Jun 25 12:29:24 EDT 2009


I might find the Coordinate Transformation stuff useful, but that doesn't
really do much without the 300-400MB of CS dictionaries correct?

I can't really see how the rest of these libraries can/could be used from a
desktop perspective

- Jackie


Jason Birch wrote:
> 
> I understand the theoretical benefits I guess, but I'm not convinced that
> there is concrete demand that justifies disrupting all of the existing
> .Net applications.
> 
> I personally haven't seen people clamouring to re-use the MapGuide APIs
> outside of MapGuide web apps.  This change causes additional work for
> existing implementations, has the potential to cause confusion for
> existing and new users, creates a divergence between the .Net/PHP/Java
> APIs, and doesn't appear to have a strong foundation in community demand.
> 
> I'd be interested in whether our resident .Net desktop developers see ways
> this could benefit their applications (such as Maestro and FDO Toolbox).
> 
> Jason
> 
> -----Original Message-----
> From: Leaf Li
> Sent: Thursday, June 25, 2009 7:04 AM
> Subject: [mapguide-internals] RE: Refactoring Web .NET API into Common
> DLLs is ready for review.
> 
> The key motivation of this RFC is to let other application be able to
> resue MapGuide's code.
> 1. It is ture .NET developer need update their project to add new
> reference after this RFC is implemented. However, they may still need
> rebuild their project without this RFC after using a new version of
> MapGuide because of some changes to .NET API. So adding some new
> references to their project is really a minor changes.
> 2. Currently MapGuide .NET Web API depends on MapGuide environment. It is
> nearly for other application to reuse MapGuide .NET API. After refactoring
> MapGuide .NET Web API into some common dlls, APIs in Foundation, Geometry
> and PlatformBase components can be completely used by other applicaiton
> such as coordinate system API. In that time, MapGuide is not only a Web
> GIS platform. but also a GIS platform which can be used by both desktop
> applicaiton and web applicaiton.
> 
> Thanks,
> Leaf Li
> 
> ________________________________________
> From: Leaf Li
> Sent: Thursday, June 25, 2009 6:47 PM
> To: mapguide-internals at lists.osgeo.org
> Subject: RE: Refactoring Web .NET API into Common DLLs is ready for
> review.
> 
> I think Jason just gave us a very good sample of one of the benefits to
> this RFC. Users can develop other application based on MapGuide API.
> Actually those application can be both desktop and web application. I am
> not sure whether we can have a MapGuide .NET Desktop SDK currenlty. It
> isn't difficult for users to copy several files manually before we have it
> as long as we document it.
> 
> Thanks,
> Leaf Li_______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
> 

-- 
View this message in context: http://n2.nabble.com/RE%3A-Refactoring-Web-.NET-API-into-Common-DLLs-is-ready-for-review.-tp3154316p3156128.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.



More information about the mapguide-internals mailing list