Ticket #269 (closed Feature Request: fixed)

Opened 8 years ago

Last modified 8 years ago

Interactive read-only maps

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

Description

Anonymous users should be able to search/navigate in topicmaps in a read-only fashion (nothing can be created/edited/deleted). These operations should be permitted:

  • open topimap (by URL)
  • view topic and association details
  • navigate alongside associations
  • hide topics and associations
  • move topics
  • move the canvas
  • search the corporate memory

Changed view-data according to these operations should be stored in the client-side view-model only, nothing is stored in the DB. An exception are Search topics: they can be created and are stored in the DB.

Change History

comment:1 Changed 8 years ago by jri

  • Status changed from new to accepted

comment:2 Changed 8 years ago by Jörg Richter

Topicmaps: anonymous canvas moves (#269).

Anonymous canvas moves are not persistent.

See ticket 269.

comment:3 Changed 8 years ago by Jörg Richter

More on interactive read-only maps (#269).

Not yet complete.

See ticket 269.

comment:4 Changed 8 years ago by Jörg Richter

Topicmaps: update and extend API (#269).

Overall the refId is stripped from the Topicmaps API.
In preparation to "Interactive read-only maps" (#269).

New methods:

  • void moveTopic(long topicmapId, long topicId, int x, int y)
  • void setTopicVisibility(long topicmapId, long topicId, boolean visibility)

Changed methods:

  • addTopicToTopicmap() returns void and is invoked via POST
  • addAssociationToTopicmap() returns void and is invoked via POST
  • removeAssociationFromTopicmap() has no refId parameter

The 2 provider classes are dropped:

Furthermore a core fix: DMObject's setCompositeValue() opens a transaction.

CAUTION: the "accesscontrol" branch is currently not fully functional.

See ticket 269

comment:5 Changed 8 years ago by Jörg Richter

New core service method getAssociation... (#269).

New method:

  • getAssociationBetweenTopicAndAssociation()

Furthermore a core fix: Topic's and Association's delete() method opens a transaction.

"Interactive read-only maps" (#269) are functional.

Note: the "accesscontrol" branch is functional.

See ticket 269

comment:6 Changed 8 years ago by Jörg Richter

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

Topicmaps: read-only maps are complete (#269).

Once logged in the Webclient reloads the topicmaps.

2 client-side events are renamed:

"user_logged_in" -> "logged_in"
"user_logged_out" -> "logged_out"

IMPORTANT: if your plugin makes use of these events it must be adapted.

Close ticket 269

comment:7 Changed 8 years ago by Jörg Richter

Topicmaps: anonymous canvas moves (#269).

Anonymous canvas moves are not persistent.

See ticket 269.

comment:8 Changed 8 years ago by Jörg Richter

More on interactive read-only maps (#269).

Not yet complete.

See ticket 269.

comment:9 Changed 8 years ago by Jörg Richter

Topicmaps: update and extend API (#269).

Overall the refId is stripped from the Topicmaps API.
In preparation to "Interactive read-only maps" (#269).

New methods:

  • void moveTopic(long topicmapId, long topicId, int x, int y)
  • void setTopicVisibility(long topicmapId, long topicId, boolean visibility)

Changed methods:

  • addTopicToTopicmap() returns void and is invoked via POST
  • addAssociationToTopicmap() returns void and is invoked via POST
  • removeAssociationFromTopicmap() has no refId parameter

The 2 provider classes are dropped:

Furthermore a core fix: DMObject's setCompositeValue() opens a transaction.

CAUTION: the "accesscontrol" branch is currently not fully functional.

See ticket 269

comment:10 Changed 8 years ago by Jörg Richter

New core service method getAssociation... (#269).

New method:

  • getAssociationBetweenTopicAndAssociation()

Furthermore a core fix: Topic's and Association's delete() method opens a transaction.

"Interactive read-only maps" (#269) are functional.

Note: the "accesscontrol" branch is functional.

See ticket 269

comment:11 Changed 8 years ago by Jörg Richter

Topicmaps: read-only maps are complete (#269).

Once logged in the Webclient reloads the topicmaps.

2 client-side events are renamed:

"user_logged_in" -> "logged_in"
"user_logged_out" -> "logged_out"

IMPORTANT: if your plugin makes use of these events it must be adapted.

Close ticket 269

Note: See TracTickets for help on using tickets.