Dependency with location
| Project: | Geobrowser |
| Version: | 5.x-1.0 |
| Component: | Documentation |
| Category: | feature request |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | active |
Hello phayes,
first I like to say 'Thank you!' for working on geobrowser.
I had to find the hard way that geobrowser 5.x1.0 only works with location up to and including version 5.x-2.7. When I tried to run it with the latest one, 5.x-3.x, I get a lot of errors and could not hack it to work. Perhaps this is my fault. In my humble opinion, it would be nice to state somewhere (on the project side) that geobrowser 5.x-1.0 works hassle free with location up and including location version 5.x-2.7 and to avoid location version 5.x-3.0 and later.
What's the status of the dev tree? Does it work with the latest location and is the category sorting solved?
Loading only certain categories: geobrowser?categories=2,3,4,5
Is it correct that the parameters (i.e. 2,3,4,5) represent the _term-id_ and not the _category-id_?
Any chance to offer 2 or more different geobrowser settings, like different sets of categories or to start on a different location, with a diffrent initial zoom factor?
Last point. I got some trouble because two people have icons located in the same house. Their icons location don't differ and to seperate them would put them in the neighbors house. So in the end there's only one "seen" one is covered. Any chance that overlapping icons are splitted by a mouse_over event?
