Changes between Version 1 and Version 2 of Future/SupportMicrosoftAjax


Ignore:
Timestamp:
Mar 18, 2008, 10:01:01 PM (16 years ago)
Author:
jbirch
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Future/SupportMicrosoftAjax

    v1 v2  
    1 Currently, MapGuide can be used with Microsoft .Net web applications through the use of the .Net APIs and manual HTML, JS, and other features via Fusion.  This development model is less-than-intuitive for many .Net developers, and is really hindering the uptake of MapGuide by .Net shops.
     1Currently, !MapGuide can be used with Microsoft .Net web applications through the use of the .Net APIs and manual HTML, JS, and other features via Fusion.  This development model is less-than-intuitive for many .Net developers, and is really hindering the uptake of !MapGuide by .Net shops.
    22
    3 Ideally, MapGuide would provide a series of custom Microsoft AJAX controls (see http://codeplex.com/AtlasControlToolkit for examples) that would allow the visual design of a Fusion application, including HTML and JavaScript and a back-end component that auto-generates an ApplicationDefinition.XML file.
     3Ideally, !MapGuide would provide a series of custom Microsoft AJAX controls (see http://codeplex.com/AtlasControlToolkit for examples) that would allow the visual design of a Fusion application, including HTML and !JavaScript and a back-end component that auto-generates an !ApplicationDefinition.XML file.
    44
    5 Less ideally, MapGuide would provide a library parallel to Fusion that performs the same kind of function.
     5Less ideally, !MapGuide would provide a library parallel to Fusion that performs the same kind of function.