Pass an IRenderer to the constructor of the RasterizingLayer

[pauldendulk]

So the user can override the default rasterizer.

[pauldendulk]

Done in commit: pauldendulk@1362ee2

[pauldendulk]

It is now also possible to use different renderers for different layers. For instance ShapefileSample.CreateLayer could be like this:

       var gdi = new GdiMapRenderer();
       layers.Add(new RasterizingLayer(CreateCountryLayer(countrySource), rasterizer: gdi));
       layers.Add(new RasterizingLayer(CreateCityLayer(citySource)));
       layers.Add(new RasterizingLayer(CreateCountryLabelLayer(countrySource)));
       layers.Add(new RasterizingLayer(CreateCityLabelLayer(citySource), rasterizer: gdi));

[smremde]

When this commit is published to nuget, individual renders should be published as individual packages.

[pauldendulk]

Why? For practical reasons it would not make a difference since you can specify which assemblies are suited for a specific platform.

I would like to keep the functionality the same for all platforms and with Gdi included there will at least be a difference in the number of renderers. That would be an argument to split them. But having many nuget packages also makes it harder to maintain. Not sure if I would be willing to do that in this stage.

[smremde]

Ok - having never maintained a nuget package I wasn't sure of the complexity.

Like you say the advantage is being able to choose the dependency(s). I think you said openTK won't work with WPF at the moment, but if it did, would you include that in the default WPF package?