Ticket #48 (closed Enhancement: fixed)

Opened 9 years ago

Last modified 8 years ago

Association Type Editor

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

Description

Users shall be able to create new association types

Change History

comment:1 Changed 9 years ago by jri

  • Status changed from new to accepted
  • Module set to deepamehta-typeeditor
  • Summary changed from add AssociationType-Editor to Association Type Editor
  • Complexity changed from 3 to 5
  • Version set to 4.0.3
  • Milestone set to Release 4.1
  • Owner set to jri

comment:2 Changed 9 years ago by JuergeN

After last discussions with Jörg, there shall be a simple Version of an Association Type Editor (without colour chooser, but hex color code) in 4.0.5.

It will allow to create ones own labeled Association Types and use them to link between Topic-Instances. These associations will appear as links in the content panel, sorted by Association Type including a headline (name of the Association Type).

comment:3 Changed 9 years ago by jri

Thanks, Jürgen, for reporting! Yes, the association type editor will come the way you described. But release plan has changed: on Oct 20 DeepaMehta 4.0.5 will be released but without the association type editor.

For the moment I'm very busy with the Kiezatlas usecase (that is the Facets and Geomaps modules). I have to demo that soon. And the association type editor will take more than 3 days, as estimated recently. Once the Kiezatlas demo is done, I do the association type editor.

In the meantime I could extend the REST API docu to let yet create association types from the command line.

comment:4 Changed 9 years ago by jri

The REST API docu (and the Data Format page) is updated now.

Some hints:

  • Once an association type is created via command line do a webclient reload and you're ready to use the new type: select an association and press "Edit", then choose an association type and press "Save".
  • When you want colorful association types: It's best to include a view topic definition in the assoc type definition (see example 2). Then you can change the color interactively in the webclient later on: reveal the assoc type's view config topic and edit its "Color" field. Unfortunately a server restart is required to see the changes.

You need latest code from master.

Let me know if creating association types works for you.

comment:5 Changed 9 years ago by JuergeN

I have updated my DeepaMehta installation with the latest version and tryed to create a new assoc type from the console:

curl localhost:8080/core/assoctype -i -X POST -H Content-Type:application/json -d '{uri: "spaceorg.planetarium.discoverer", value: "Discoverer", data_type_uri: "dm4.core.text"}' 

but the result is:

HTTP/1.1 405 Method Not Allowed
Allow: GET,OPTIONS,HEAD
Content-Type: text/html; charset=iso-8859-1
Cache-Control: must-revalidate,no-cache,no-store
Content-Length: 1397
Server: Jetty(6.1.x)

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
<title>Error 405 Method Not Allowed</title>
</head>
<body><h2>HTTP ERROR 405</h2>
<p>Problem accessing /core/assoctype. Reason:
<pre>    Method Not Allowed</pre></p><hr /><i><small>Powered by Jetty://</small></i><br/>                                                
...
</body>
</html>

Am I missing something?

comment:6 Changed 9 years ago by jri

That happens if you don't have the latest code running at server-side.
Are you sure you're on the master branch? (perhaps you're still on geomaps branch)

git status

must return:

# On branch master
nothing to commit (working directory clean)

If you're not on master:

git checkout master
mvn clean install -P all

comment:7 Changed 9 years ago by JuergeN

Yes, I was on master, but for some reason it did not work. Finally I deleted my local deepamehta directory and reinstalled completely from source. Now I can create associations via curl.


comment:8 Changed 9 years ago by JuergeN

OK, I have created a new assoc. It appears in the content panel, amongst all other association.

Jörg, how would you estimate your effort to list the assoc types in the content panel with headlines as discribed above? Cause without this feature or a label, the association as such still does not mean too much. This is just a question. If you feel like you cannot do this now, then let's just leave it for the moment.

comment:9 Changed 9 years ago by jri

The grouped display is not fully trivial. For the moment the webclient doesn't have the necessary information. Effort is about 1 day. I plan to do it once there is a reasonable Kiezatlas-brakethrough. That will be in about 10 days.
Reporting your feature priorities is appreciated :)

comment:10 Changed 8 years ago by jri

The grouping feature is realized meanwhile.
The graphical association type editor is planned for DM 4.0.13 (Dec 4, 2012)

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

Assoc type editor: create assoc types (#48).

Just the beginning: create assoc types via menu.
The actual assoc type editor is about to come (just the generic topic editor for the moment).

See ticket 48.

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

Type editor: refactor renderer code (#48).

TopicTypeRenderer? and AssociationTypeRenderer? have common base class: TypeRenderer?.

Not yet functional.

See ticket 48.

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

Webclient: refactor client-side model code (#48).

TopicType? and AssociationType? have common base class: Type.

Association type editor not yet functional.

See ticket 48.

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

Core: refactor type update code (#48).

The type update code is moved to base class (AttachedType?).
It is shared by topic types and association types.

Core service API:

  • updateAssociationType() is new method
  • DELETE_ASSOCIATION_TYPE is new directive

Webclient API:

  • dm4c.do_update_association_type() is new method

Association type editor is functional for simple types.
Complex association types are pending.

See ticket 48.

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

Association type editor works (#48).

Simple assoc types and complex assoc types.
Just like topic types.

See ticket 48.

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

Type Editor: adpat to core changes (#48).

The TypeRenderer? base class is loaded through new synchronous load mechanism (script/helper/).

See ticket 48.

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

Assoc type editor: create assoc types (#48).

Just the beginning: create assoc types via menu.
The actual assoc type editor is about to come (just the generic topic editor for the moment).

See ticket 48.

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

Type editor: refactor renderer code (#48).

TopicTypeRenderer? and AssociationTypeRenderer? have common base class: TypeRenderer?.

Not yet functional.

See ticket 48.

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

Webclient: refactor client-side model code (#48).

TopicType? and AssociationType? have common base class: Type.

Association type editor not yet functional.

See ticket 48.

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

Core: refactor type update code (#48).

The type update code is moved to base class (AttachedType?).
It is shared by topic types and association types.

Core service API:

  • updateAssociationType() is new method
  • DELETE_ASSOCIATION_TYPE is new directive

Webclient API:

  • dm4c.do_update_association_type() is new method

Association type editor is functional for simple types.
Complex association types are pending.

See ticket 48.

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

Association type editor works (#48).

Simple assoc types and complex assoc types.
Just like topic types.

See ticket 48.

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

Type Editor: adpat to core changes (#48).

The TypeRenderer? base class is loaded through new synchronous load mechanism (script/helper/).

See ticket 48.

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

Assoc type editor: create assoc types (#48).

Just the beginning: create assoc types via menu.
The actual assoc type editor is about to come (just the generic topic editor for the moment).

See ticket 48.

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

Type editor: refactor renderer code (#48).

TopicTypeRenderer? and AssociationTypeRenderer? have common base class: TypeRenderer?.

Not yet functional.

See ticket 48.

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

Webclient: refactor client-side model code (#48).

TopicType? and AssociationType? have common base class: Type.

Association type editor not yet functional.

See ticket 48.

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

Core: refactor type update code (#48).

The type update code is moved to base class (AttachedType?).
It is shared by topic types and association types.

Core service API:

  • updateAssociationType() is new method
  • DELETE_ASSOCIATION_TYPE is new directive

Webclient API:

  • dm4c.do_update_association_type() is new method

Association type editor is functional for simple types.
Complex association types are pending.

See ticket 48.

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

Association type editor works (#48).

Simple assoc types and complex assoc types.
Just like topic types.

See ticket 48.

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

Type Editor: adpat to core changes (#48).

The TypeRenderer? base class is loaded through new synchronous load mechanism (script/helper/).

See ticket 48.

comment:29 Changed 8 years ago by jri

  • Status changed from accepted to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.