Closed dmcassel closed 8 years ago
The search-map directive could cover most of the UI part of this. The back-end already supports it out of the box, though there are improved versions of the geo-constraint..
Submitted PR with initial integration Google Maps updates. Tested on ML 7. Should work fine in ML 8 if data is stored as XML but will not work if stored as native JSON. Will open new ticket for handling native JSON.
Good chance it 'just works' with native JSON as well..
I started new component https://github.com/grtjn/ml-google-maps-ng that is supposed to merge all maps related things, including work from Dave G, Matt P, and me..
How much geospatial support should be in the vanilla generated app? Does the ESRI option still make sense, especially since it only shows a map on the details page?
I assume don't include maps unless specifically asked for. So should something be changed from the current situation?
Moving this to milestone 0.2.1. There is ESRI support for the detail page, and the ml-google-maps-ng can fill the need for geo searching for the moment.
Still a good question though. It makes sense to include frequently used components into the slush generator, to make it easier to get started. Maybe we need to discuss the shape of things, and options/questions you want to offer the end user..
I am considering closing this ticket. Since newer slush template we moved away from having such components inside the slush generator itself. We have cookbook recipes (#167) for adding separate components like ml-google-maps-ng and such, and Dave G is working on one for similar functionality using ESRI.
Votes?
I vote we close it as a no longer relevant ticket.
@daveegrant Did you publish your work on the new ESRI component yet?
There is a separate ticket for the ESRI component: #233, closing this one..
To make it easy to set up geospatial search, include components in the generator for doing so.