[Tilesathome] less inkscape calls in _unstable

[Matthias Julius]

Dirk-Lüder Kreie <osm-list at deelkar.net> writes:

> Following the or/p projection support by Frederik I now make use of
> all the goodness in the current unstable client, by not only rendering
> tilestripes and cutting them (resulting in up to 65 inkscape or batik
> calls for the "tile" layer alone) but rendering one super-tile for
> every detail level and then cutting that into up to 32x32 tiles,
> reducing the amount of inkscape/batik calls to 6 for tile, 5 for
> maplint and -- unchanged -- 1 for captionless.
>
> Initial testing shows it does indeed work as expected, at least with
> or/p and inkscape.

Is there someone running _unstable with Batik?

I had been working on a mostly re-write of the rendering in the client
over the weekend.  It is running, but it is not quite final, yet.

My version is simplifying the code quite a bit.  I got rid of the
recursive calls to RenderTile.  It is always rendering full tilesets
and all blank tiles since I want these to be there for the assembly of
tileset files.  The rendering is forked only on one spot and each fork
is rendering one or more zoom levels each straight from OSM to SVG to
PNG to tiles.

I got rid of the striped rendering completely.  For that reason I
would like to wait a while and see if anyone is reporting Inkscape or
Batik problems with the one-PNG-per-zoom-level setup that aren't there
with the striped rendering.  I'll commit my changes to SVN in a few
days if nobody is complaining.

Matthias