This issue is not high priority but could improve the user experience and its implementation may shed light on the bigger map manager design. The implementation of a map manager to improve performance is discussed in issue #136. That issue is concerned more with memory management and performance hit of reinitializing maps.
An incremental step to that design might be to at least implement a map manager that is aware of the maps that are in the application and have been viewed. The state of the map could be remembered so that when reviewed the user does not need to renavigate the map. For example, remember the zoom coordinate and zoom level so that the map can be reopened to the same location. These state variables can optionally be saved as cookies so that if the user revisits the website later in another session, the maps will be shown as they left them. More complex state could be remembered such as which layers are enabled/visible. Actually, because the interface is by design intended to be simple, there are not that many state variables to remember.
Maybe the manager can use a version of the map configuration file data model, with some additional data for real-time application state?
This issue is not high priority but could improve the user experience and its implementation may shed light on the bigger map manager design. The implementation of a map manager to improve performance is discussed in issue #136. That issue is concerned more with memory management and performance hit of reinitializing maps.
An incremental step to that design might be to at least implement a map manager that is aware of the maps that are in the application and have been viewed. The state of the map could be remembered so that when reviewed the user does not need to renavigate the map. For example, remember the zoom coordinate and zoom level so that the map can be reopened to the same location. These state variables can optionally be saved as cookies so that if the user revisits the website later in another session, the maps will be shown as they left them. More complex state could be remembered such as which layers are enabled/visible. Actually, because the interface is by design intended to be simple, there are not that many state variables to remember.
Maybe the manager can use a version of the map configuration file data model, with some additional data for real-time application state?