Why not use the same macro syntax of GoogleStaticMap

[jrovegno]

Hi martin_s: I'm probing GoogleMapMacro plugin and some features are missing. I'm gonna create an issue about that.

But the current issue is like a wish list:

1. Change the GoogleMapMacro syntax to the same macro syntax of GoogleStaticMapMacro, It would be nice only have to change GoogleMap for GoogleStaticMap and vice versa, and have the best of the both worlds :P
2. Enable the same wiki processor syntax of GoogleStaticMapMacro on GoogleMapMacro, I love this feature, is clear and simple.

I'm planning to make in the future on TracGoogleMapTicket can be enable use syntax like this:

{{{
#!GoogleStaticMap
center=#1.coodinates
path="#1.coodinates|#12.coodinates|#3.coodinates|#4.coodinates"
markers="label:M|Munich"
markers="label:B|#1.components.coodinates"
markers="label:K|Cologne"
markers="label:H|color:orange|Hamburg|Hannover"
markers="size:small|color:green|Mannheim|Straubing|Münster"
size=250x300
}}} 

to create dynamics maps on the wiki, reports and descriptions. What do you think about this?

Regards Javier

[Martin Scharrer]

The reason why this two macros have a different syntax is because they both depend on the underlying syntax of the Google APIs. GoogleStaticMapMacro only builds a image URL out of the given values. The wiki processor syntax is also very new, so I didn't had time to implement it in the other macro.

To 1.
But you are right, both macros should accept the same syntax for be more user friendly. Also the GoogleMapMacro could have a static switch to only create a static map. This would render GoogleStaticMapMacro unnecessary or call for an integration of both.

To 2.
The wiki processor syntax is easy enough and I will go and implement it in GoogleMapMacro soon.

[Martin Scharrer]

2. is now implemented: [8649].

[jrovegno]

Replying to martin_s:

2. is now implemented: [8649].

I have tested:

{{{
#!GoogleMap
address="Providencia Santiago Chile"
markers=center;A;ticket:1|"Av. Manuel Montt";B
zoom=14
types=hybrid
size=300x300
}}}

And It works OK. Thanks