style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<sakkaku> wrote in message.Net
is also supported "out of the box". The APIs are automatically generated from
the same C++ API and wrapped into the target language via SWIG (I may be wrong
about this though). So theoretically you might be able to get wrappers for
perl, ruby and python or any of the other languages swig supports if you felt
like pulling your hair out and castrating yourself trying to get it to work.
We started off on Mapguide 4 or 5 all the way to 6.5 before migrating to 2008.
IMO the new API has much more functionality at the cost of more time in
development. At the same time some things are simplified (for instance passing
coordinates/zoom instead of an id for zoomto, so you don't need a zoomto for
every feature). Some of the design decisions make me want to pull my hair out
at times though (like passing base64 encoded numbers of different bytelengths
in selection XML without specifying the type, when XML should be human
readable to begin with). Unwrapping the API and squinting in vain to see where
the logic is can be fun at times.
Access a broad range of knowledge to help get the most out of your products and services.