[mapguide-internals] RFC60 ??? - at least a sandbox please
Walt Welton-Lair
walt.welton-lair at autodesk.com
Fri Sep 18 18:58:59 EDT 2009
And as usual the attached file (24Kb) didn't make it. Definitely a PITA.
-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Walt Welton-Lair
Sent: Friday, September 18, 2009 6:57 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] RFC60 ??? - at least a sandbox please
I think you should create your own test map - it's not hard. Use one of your existing tiled maps, and modify a couple of your layer definitions to use the new stylization.
Start by looking in the UnitTest\TestData\Symbology folder. It contains sample symbols / layers used by the unit test.
- the .sd files are sample symbol definitions (point / line /area)
* symbol.sd / symbol.sd are point symbols
* linesymbol.sd is a line symbol
* areasymbol.sd is an area symbol
- the .ldf files are sample layer definitions that reference these symbols - pay attention to the SymbolInstance element
* UT_SymbologyPoints.ldf - an example of a layer referencing a point symbol
* UT_SymbologyLines.ldf - an example of a layer referencing a line symbol
* UT_SymbologyParcels.ldf - an example of a layer referencing an area symbol
To convert a layer to use the new stylization, replace any PointTypeStyle / LineTypeStyle / AreaTypeStyle element with a CompositeTypeStyle element, like in the unit test layer files. You'll then want to do two tests with the layer (you'll want your RFC60 code to handle both):
1) Test using referenced symbol definitions. This is what the .ldf files currently have. The SymbolInstance contains a ResourceId element indicating which SymbolDefinition resource to use. Obviously you'll need to add the symbol definitions to the repository. I know MapGuide Studio lets you easily create them, or you can add them by hand using the Web forms. One nice thing about using referenced symbols is that in a *debug* build you can make the ReferenceId point to a file on your machine, e.g.:
<SymbolInstance>
<ResourceId>C:\Temp\Symbols\SymbologyLines.sd</ResourceId>
...
</SymbolInstance>
You can then easily edit the symbol to test different behaviors, without having to upload it all the time.
2) Test using inlined symbol definitions. Instead of using a ResourceId tag just embed the SymbolDefinition directly, e.g.:
<SymbolInstance>
<SimpleSymbolDefinition>
...
</SimpleSymbolDefinition>
</SymbolInstance>
Of course you'll want to test using different symbol definitions. Refer to the schema and RFC 14 for this. Again, once you get a layer set up which uses a referenced symbol on your hard drive then it's very easy to test. I also attached a zip with symbols + layers I've used in my testing. You'll have to sort through it though.
Walt
-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of UV
Sent: Friday, September 18, 2009 6:17 PM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] RFC60 ??? - at least a sandbox please
> Yes, I refuse to use a beta or release candidate on a production box as a matter of policy/liability.
>
> Thanks
we cant even use a release candidate any longer but have to patch with
RFC60 ourselves.... for production of course!
I still hope that somebody will come up with a big map using new
stylization for me before I am too busy to look into it anymore
so we can tackle the remaining issue at the root.
My second merge with the 2.1 branch already caused a few days extra
work... (or lets call it waste of time ;)
having a new stylization map I also could verify that the patch does not
cause problems with new stylization even without any changes...
_______________________________________________
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