Let's start with the new features first.
Feature Count for Thematic Rules
When dealing with thematic layers, sometimes one might want to know exactly how many features are covered by each thematic layer rule. There's now a Feature Count button to crunch those numbers for you.
Clicking it will crunch the feature counts of each individual style rule with a filter (default rule is omitted) and present the totals in a new dialog.
MgTileSeeder (the successor to MgCooker)
Not bundled with Maestro yet, but included as a standalone package available for download alongside this release is MgTileSeeder, a new command-line tile seeding application that is the successor to MgCooker and will eventually replace it in a future release.
I'll cover this tool in more detail in a future post.
New project site
Since MapGuide Maestro is now on GitHub, I've activated the GitHub Pages feature and spun up a new project web site for it.
On this site you will also find the user guide, developer's guide and the API reference for Maestro API and friends.
So speaking of Maestro API ...
Where's the SDK package?
The SDK story is going through a bit of churn at the moment. This milestone release is primarily focused around Maestro (the application) and not the API/SDK, so whatever things I had intended to finish regarding the Maestro API/SDK have taken a back seat so I can get Maestro (the application) out the door.
So as it stands, there is no SDK package with this release and there never will be with any future releases. This is due to major under-the-hood work to port the MapGuide Maestro API and supporting libraries over to target .net standard.
The end result of this is that the primary way to acquire the Maestro API is now via a NuGet package
And since the API reference is now online, this makes the SDK package somewhat redundant.
The various sample code and supporting tools in the SDK have been shipped off to a separate repository, that will be revealed in due course once they have all been updated to work in this new .net world we live in.
If you are an existing consumer of the Maestro API, it should be as simple as removing all your current assembly references to Maestro API and friends and installing the NuGet packages in the affected projects.
.net Framework 4.6.1 required
Due to porting the Maestro API to target .net standard 2.0, .net Framework 4.6.1 is the minimum version of the .net Framework required.
The Windows installer will automatically download and install this for you if you don't have it. It will also automatically install the Visual C++ redistributable so the local connection (mg-desktop) mode will also work out of the box.
Other changes/fixes
- Fix a long standing annoyance where setting WMS bounds on a published layer will set the coordinate system to EPSG:???? requiring you to manually enter in the EPSG code. This should now be automatic most of the time. It will also be automatically transformed to EPSG:4326 bounds if required.
- Now uses ICSharpCode.TextEditor for dialog to edit raw resource header XML
- New resources validation rules around WMS-published Layer Definitions
- Basic line styles no longer trashed on cancellation of the Edit Style dialog
- Can now read configuration documents where FDO-related attributes have incorrect casing
- No-op any map viewer rendering requests if any display parameter is <= 0
- Disable local map preview if connecting to a MapGuide Server older than 2.1
- Fusion editor no longer adds obsolete VirtualEarthScript element when adding Bing Maps layers
- Now gracefully handles invalid resources with open editors instead of crashing out to desktop.
Posts
No comments:
Post a Comment