Support for different map types

[JuergeN]

user shall select different MapTypes? for data presentation, e.g. a geo map.

[Jörg Richter]

Topicmap renderer plugin mechanism (#52).

Begin of new feature: Plugins can provide custom topicmap renderers.

The new module "deepamehta-geomaps" will provide a OpenLayers?-based topicmap renderer.

The "New Topicmap" dialog shows a menu which lists all installed topicmap renderers.

New hook in Topicmaps module:

• topicmap_renderer

Dropped hook:

• get_canvas_renderer

See ticket 52.

• Changeset: 5d3e7a28befdf8c9e0f9a4be7a02176d3c56f226
• URL: ​https://github.com/jri/deepamehta/commit/5d3e7a28befdf8c9e0f9a4be7a02176d3c56f226

[Jörg Richter]

Geomaps module: display OpenStreetMaps? (#52).

See ticket 52.

• Changeset: 06ff4ecb11020cdfb2ce85f5231a17c80373368a
• URL: ​https://github.com/jri/deepamehta/commit/06ff4ecb11020cdfb2ce85f5231a17c80373368a

[Jörg Richter]

Elaborate map type extension mechanism (#52).

A topicmap renderer implementation can provide

• a custom topicmap model
• custom topicmap storage operations

The TopicmapRenderer? interface specifies a "load_topicmap" method.

Furthermore in core:
The "get-topics-by-type" service call has a "fetchComposite" parameter ("fetch_composite" query parameter in REST API).

See ticket 52.

• Changeset: 113f6426989231af68c3bac9fdead7c6e42c1e1b
• URL: ​https://github.com/jri/deepamehta/commit/113f6426989231af68c3bac9fdead7c6e42c1e1b

[Jörg Richter]

Elaborate map type extension mechanism pt.2 (#52).

Proper separation of generic canvas renderer and its topicmaps module specific extension.
The latter contains:

• load_topicmap() (moved from generic canvas renderer)
• prepare_topic_for_display()

See ticket 52.

• Changeset: 90f195e4f31921986d28cefa87e2202742074d41
• URL: ​https://github.com/jri/deepamehta/commit/90f195e4f31921986d28cefa87e2202742074d41

[Jörg Richter]

Elaborate map type extension mechanism (#52).

A topicmap renderer implementation can provide

• a custom topicmap model
• custom topicmap storage operations

The TopicmapRenderer? interface specifies a "load_topicmap" method.

Furthermore in core:
The "get-topics-by-type" service call has a "fetchComposite" parameter ("fetch_composite" query parameter in REST API).

See ticket 52.

• Changeset: 113f6426989231af68c3bac9fdead7c6e42c1e1b
• URL: ​https://github.com/jri/deepamehta/commit/113f6426989231af68c3bac9fdead7c6e42c1e1b

[Jörg Richter]

Elaborate map type extension mechanism pt.2 (#52).

Proper separation of generic canvas renderer and its topicmaps module specific extension.
The latter contains:

• load_topicmap() (moved from generic canvas renderer)
• prepare_topic_for_display()

See ticket 52.

• Changeset: 90f195e4f31921986d28cefa87e2202742074d41
• URL: ​https://github.com/jri/deepamehta/commit/90f195e4f31921986d28cefa87e2202742074d41

[jri]

Map type extension architecture is complete for the moment. Plugins can provide additional map types, e.g. a geo map or a time map. Each map type can have a distinguished data model, rendering facility, and interaction style.

For an usage example see the DM4 Geomaps plugin:
​https://github.com/jri/dm4-geomaps