[mapguide-users] Re: Upgrading MaestroAPI

[Jackie Ng]

Reason is simplicity and better encapsulation (ok, maybe also because I
couldn't get the 2.x code to work under the 3.0+ API design)

There is a whole set of properties that are dependent on the layer
definition you initialize the RuntimeMapLayer with. For example, what if you
change the feature source without updating the class definition, geometry,
and IdentityProperties properties to match? One broken runtime layer. 

Such unnecessary and error-prone mutability will cause problems for new
users of the Maestro API.

I have updated the SDK web samples with an example of modifying a layer
filter (one such read-only property) using this layer replacement approach.

- Jackie

--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Upgrading-MaestroAPI-tp7019938p7050680.html
Sent from the MapGuide Users mailing list archive at Nabble.com.