[OSM-dev] Osmarender: Produce SVG maps for mobile phones (SVG TINY/BASIC)
80n80n at gmail.com
Wed May 9 18:00:31 BST 2007
We have to make a decisions on a case-by-case, feature-by-feature basis.
If we *know* that SVG Tiny does not support, for example, baseline-offset,
then we can use a different method if possible, or if not possible then make
an alternative strategy for SVG Tiny devices.
Unless we *know* what does and does not work, we will blindly use any SVG
feature that gets the job done with no consideration for what is and is not
possible in SVG tiny. A little thought at the right time can save us from
taking a bad path that is then hard to come back from.
On 5/9/07, Frederik Ramm <frederik at remote.org> wrote:
> > I don't think it is such a good idea to steer Osmarender away from SVG
> > features that are not supported by SVG mobile. This could
> > signigificantly reduce the features offered by the full SVG
> > created by
> > Osmarenderer since SVG tiny lacks a lot of SVG Full features.
> But on 29th January, on this list, you wrote:
> > Using Illustrator, I converted one of the OSM maps from SVG to SVG
> > Tiny .
> > The resulting map was identical as far as I can figure. The only
> > thing which
> > differs from the full blown SVG map is that the navigation keys on
> > the left
> > are not working. This happens because according to the
> > specification the SVG
> > Tiny platform does not support events (which is not such a major
> > restriction, since this map will be used on mobile phones anyway).
> > So, I belive that SVG Tiny is powerful enough to visualise OSM maps
> > without
> > any problems.
> At that time it sounded as if we could use SVG tiny without loss of
> Frederik Ramm ## eMail frederik at remote.org ## N49°00.09' E008°23.33'
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dev