Ticket #77 (closed Defect: fixed)
Editing "Composed Topic Types" in the Content Panel not functional
Reported by: | jri | Owned by: | jri |
---|---|---|---|
Priority: | Major | Milestone: | |
Component: | DeepaMehta Standard Distribution | Version: | 4.0.3 |
Keywords: | Cc: | JuergeN, dgf, irau, Malte | |
Complexity: | 5 | Area: | |
Module: | deepamehta-typeeditor |
Description
Changes are not processed and not saved.
These functions are missing:
- Change Association Type
- Change Cardinality
- Change Child Type Order (by drag'n'drop the boxes)
Not yet implemented.
Change History
comment:1 Changed 13 years ago by jri
- Status changed from new to accepted
- Version changed from 4.0.2 to 4.0.3
comment:2 Changed 13 years ago by Jörg Richter
Core/Type? Editor: change child type order (#77).
On the edit page for a composite type:
drag'n'drop the child type boxes in the desired order and press "Save".
The other 2 functions are still missing.
See ticket 77.
comment:3 Changed 13 years ago by Jörg Richter
Core/Type? Editor: change child type order (#77).
On the edit page for a composite type:
drag'n'drop the child type boxes in the desired order and press "Save".
The other 2 functions are still missing.
See ticket 77.
comment:4 Changed 13 years ago by jri
Changing the association type in the type editor panel works.
Still pending:
- Change cardinality
- Visually update possible association definitions on the canvas (e.g. color)
Changeset 2b77e4758a77ea40e4f29afc4f7fcd8937316f09 (April 22)
comment:5 Changed 13 years ago by jri
Changing the cardinality in the type editor panel works.
Click a topic type -> press Edit -> change Cardinality -> press Save.
Still pending:
- Visually update possible association definitions on the canvas (e.g. color)
Changeset 9653a24a09b9ca77378bf14c39e7ae8965b1e0ce (April 22)
comment:6 Changed 13 years ago by jri
- Status changed from accepted to closed
- Resolution set to fixed
Webclient fix: update canvas on type update (#77).
Core: the following applies when an association is updated as a consequence of another operation, e.g. when a topic type is updated (in particular its association definitions):
- the POST_RETYPE_ASSOCIATION hook is possibly triggered
- an UPDATE_ASSOCIATION directive is send to the client
Changeset: 59be928390a2b66319095eebacca60c8c2c8b23f (May 11)
comment:7 Changed 13 years ago by Jörg Richter
Type Editor panel: change association type (#77).
Changing the association type in the type editor panel works.
Still pending:
- Change cardinality
- Visually update possible association definitions on the canvas (e.g. color)
Furthermore in Core:
1) Introduce service implementation class ObjectFactory?. Its responsibility is to load domain objects from DB.
This makes for a more clean design and reduces complications (no model-less domain objects are constructed).
The domain object's own fetch() methods are about to be dropped.
For the moment only one domain object -- AssociationDefinition? -- is transformed.
2) Change AssociationDefinition? interface: Add method
void update(AssociationDefinitionModel? model, ClientState? clientState, Directives directives)
3) Change Association interface: New method
getRole(RoleModel? model)
replaces
getRole(long objectId)
4) Change Role interface: Add method
RoleModel? getModel()
See ticket 77
comment:8 Changed 13 years ago by Jörg Richter
Type Editor panel: change cardinality works (#77).
Changing the cardinality in the type editor panel works.
Click a topic type -> press Edit -> change Cardinality -> press Save.
Still pending:
- Visually update possible association definitions on the canvas (e.g. color)
See ticket 77
comment:9 Changed 13 years ago by Jörg Richter
Core API: change updateTopicType() service call.
Core service API:
- updateTopicType(): returns Directives (instead a TopicType?)
Webclient hooks:
- "post_update_topic": drop "old_topic" parameter
- "post_update_association": drop "old_assoc" parameter
Webclient service methods:
- dm4c.do_update_topic(): drop "old_topic" parameter
- dm4c.do_update_association(): drop "old_assoc" parameter
- dm4c.do_update_topic_type(): drop "old_topic_type" parameter
In preparation to a bug fix.
See ticket 77.
comment:10 Changed 13 years ago by Jörg Richter
Webclient fix: update canvas on type update (#77).
Core: the following applies when an association is updated as a consequence of another operation, e.g. when a topic type is updated (in particular its association definitions):
- the POST_RETYPE_ASSOCIATION hook is possibly triggered
- an UPDATE_ASSOCIATION directive is send to the client
See ticket 77.