[mapguide-internals] Documenting the HTTP API

Jason Birch jason at jasonbirch.com
Wed Feb 24 14:39:03 EST 2010


This looks good.

I think that there are some cases where parameters are mutually exclusive,
or groups of them need to all be specified for particular results, basically
like function signatures.

Can you think of a way of visually indicating this kind of inter-reliance
for the web API?  I've been scratching my head over it, but not making much
progress arguing with myself (I'm too stubborn).  I was thinking that
actually showing pseudo function signatures might be useful, but the number
of potential variations may make this unpractical.


On 24 February 2010 11:24, Trevor Wekel wrote:

> Hi everyone,
> I have started to document the GETDYNAMICMAPOVERLAYIMAGE HTTP op on the
> wiki.  The documentation for the op is not yet complete (it is complicated)
> but I think the general format is reasonable.  Please let me know if you
> like the format.  Is it understandable, does it need additional sections,
> etc.?
> http://trac.osgeo.org/mapguide/wiki/HttpApi
> http://trac.osgeo.org/mapguide/wiki/HttpApi/RenderingService/GetDynamicMapOverlayImage
> Regards,
> Trevor
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals

More information about the mapguide-internals mailing list