On Jun 25, 12:02 pm, Miguel Angel Vilela <[email protected]> wrote:
> On Fri, Jun 25, 2010 at 12:33, JavaJive <[email protected]> wrote:
>
> Looks doable with Static Maps API, just add a "print" link or button that
> will open a new window/tab with the printable version. It's not a solution I
> like recommending (opening a new window) but will work across all browsers.
Thanks, but I already know how to create a seperate Print Window. If
anyone reading this wants some ideas on how to do this, see Print Node
here ...
http://www.macfh.co.uk/JavaJive/ProgScriptWeb/General.html
It's the MAPS that are the problem. Is there any documentation
anywhere as to how to create a printable version of an existing Google
Map, complete with markers, geometries, etc? Preferably something
simple.
Nevertheless, the fact remains that noone should have to be doing
this ...
> On Jun 25, 10:43 am, Miguel Angel Vilela <[email protected]> wrote:
>
> > > Printing is not officially supported in the JavaScript APIs because each
> > > browsers deals with printer in their own way. If you need a map that will
> > > print well, you'll be better off with the Static Maps API.
1) The v2 Maps print almost acceptably well, albeit only in
Compatibility View in the world's most popular browser, so obviously
Google's problems with printing maps are not insurmountable.
2) Because Google don't seem particularly concerned about backward
compatibility, just as the all the custom controls I innocently
created for v2 ...
http://www.macfh.co.uk/JavaJive/ProgScriptWeb/GoogleGoogle.html
... are now broken in v3 (as far as I have been able to establish
either completely or at least until I put in more time than I really
should spare right now) so any solution I or others create to print a
Google Map will probably break next time Google change the API again.
3) Both the pages I linked have other types of maps on them. It's
extremely unlikely that any solution that I create that works with a
Google Map will work with those.
4) As Google being a multi-national corporation has much more clout
than each individual private developer using its APIs, and as printing
is such a fundamental requirement, Google should supply a standard
solution, preferably through consultation with browser developers, an
interim de facto standard if all else fails.
Whatever happened to WYSIWYG? Are today's developers so dazzled by
all the modern gagdetry that they've forgotten such basic principles
of of computing?
Really, this is Google's problem, and they should set to and solve it.
--
You received this message because you are subscribed to the Google Groups
"Google Maps JavaScript API v3" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-maps-js-api-v3?hl=en.
