Infoclick: Be able to use x,y and zoom as params.

[jesade-vbg]

We need the possibility to access and use {x}, {y} and {zoom} in infoclick templates to create links etc containing these.

Similar to: #1076 (comment)

Maybe group these as {click:param}

{click:x}
{click:y}
{click:zoom}

Edit:
I've also added the possibility to convert the coordinates to another projection.
Example:
{click:x|toProjection('x', 'click:x', 'click:y','EPSG:4326', 4)}
this converts x to EPSG:4326 (used by google etc)
{click:y|toProjection('y', 'click:x', 'click:y','EPSG:4326', 4)}
this converts y to EPSG:4326 (used by google etc)
So now you should be able to create links to a wide variety of map services.

[jacobwod]

@jesade-vbg Can you tag and mark as done please?

[jesade-vbg]

Is this done? Have I missed something?

[jacobwod]

I thought it was completed in 3b565d8, but perhaps I mixed it up with something else? 😄

Edit: ahh.. it looks like two separate issues. Sorry!

[jesade-vbg]

I have a suggestion, to make AppModel a singleton. The AppModel is passed around in alot of places in the code. As there is only one AppModel instance that coders want to access, why not make it a singleton?

Whats your opinion? @Hallbergs @jacobwod

Check this commit:
e35b69d

[jacobwod]

Interesting! Perhaps we can talk about this some day this week?

[jesade-vbg]

AppModel and coordinate transforms seems trustworthy after refactoring. Transforms tested against GMaps and GStreetView.