Maki I answer here your other
post,
On 22/02/2015 02:34 μμ, Maki wrote:
Anyway I played a couple of days with SVG
textures, some random facts and thoughts:
a) Salamander SVG is much more robust when it comes to
SVG specs support. After successfully testing in Atlas beta
I moved the theme to the phone and I had to redo some, even
simple ones, patterns because they didn't render. I attach
one sample. Couldn't Salamander be used in Android, too?
I tried first the opposite way, to use AndroidSVG in Java (but it
uses Android specific code).
The same result is with SVG Salamander, it relies on Java classes
that don't exist in Android.
I'm in favor too having only one SVG library and the most
compatible one too, but it seems to not be that easy.
b) I have caching issues in Atlas beta. If I modify the
SVG file, just reloading (F5) isn't enough, I have to quit
and reopen the app. Changes in the XML are handled fine,
however.
In Java (Atlas) we don't use SVG cache (probably not needed), so
the live rendering is performed each time.
For that I find a bit strange what you mention, but I'll check it.
c) reloading the map from the "tools" menu usually works
fine in Cruiser, but it happened once that I had to rename
the SVG file, because no matter what I did (reloading,
switching maps and/or theme) it didn't see the changes I
made.
In Android (Cruiser) I clear all the caches (also SVG) with each
map model change (open map / theme, reload etc).
Thanks for the feedback, we need to check those reports.