Ticket #52 (closed Enhancement: fixed)

Opened 9 years ago

Last modified 9 years ago

Support for different map types

Reported by: JuergeN Owned by: jri
Priority: Major Milestone: Release 4.1
Component: DeepaMehta Standard Distribution Version:
Keywords: Cc:
Complexity: 5 Area:
Module:

Description

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

Change History

comment:1 Changed 9 years ago by 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.

comment:3 Changed 9 years ago by jri

  • Complexity changed from 3 to 5
  • Milestone set to Release 4.1
  • Summary changed from create configuration facility for different MapTypes to Topicmap renderer plugin mechanism

comment:4 Changed 9 years ago by jri

  • Summary changed from Topicmap renderer plugin mechanism to Support for different map types

comment:5 Changed 9 years ago by jri

  • Owner set to jri
  • Status changed from new to accepted

comment:6 Changed 9 years ago by 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.

comment:7 Changed 9 years ago by 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.

comment:8 Changed 9 years ago by 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.

comment:9 Changed 9 years ago by 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.

comment:10 Changed 9 years ago by jri

  • Status changed from accepted to closed
  • Resolution set to fixed

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

Note: See TracTickets for help on using tickets.