Changes between Version 125 and Version 126 of ReleaseNotes


Ignore:
Timestamp:
30.05.2015 18:25:34 (10 years ago)
Author:
jri
Comment:

4.6 release notes, revision 2

Legend:

Unmodified
Added
Removed
Modified

  • ReleaseNotes

    v125 v126  
    55---- 
    66 
    7 == //upcoming//: DeepaMehta 4.6 == 
     7== 2015-05-30: DeepaMehta 4.6 == 
     8 
     9!DeepaMehta 4.6 is a maintenance release that comes with an extended DM meta-model, a lot of small improvements, and (partly overdue) bug fixes. As a first application of the extended meta-model the DM Contacts model is revised. For an explanation of the new meta-model and Contacts model see this posting:\\ 
     10http://lists.deepamehta.de/pipermail/users-lists.deepamehta.de/2015-May/000488.html 
     11 
     12You can upgrade any !DeepaMehta 4 installation which is not older than !DeepaMehta 4.1. For installation and update instructions see the [[https://github.com/jri/deepamehta#readme|README]]. 
     13 
     143rd-party plugins compatible with !DeepaMehta 4.5 might be required to be adapted by the respective developers in order to work with !DeepaMehta 4.6. 
    815 
    916New features: 
    10 * **Extended meta-model**: type definitions with custom association types (#341). 
     17* **Extended meta-model**: association definitions can have custom association types (#341). 
    1118* **Error reporting**: errors occurring at server-side are reported to the Webclient user (#790). 
    1219 
    1320Improvements: 
    14 * **Refined //Contacts// model**: the intermediate `Address Entry` and `Phone Entry` topic types/instances are gone. A person/institution is connected //directly// to its `Address` and `Phone` topics via a custom association. The `Address Label`/`Phone Label` are attached to the custom association (#779). 
     21* **Refined //Contacts// model**: the intermediate `Address Entry` and `Phone Entry` topic types/instances are gone. A person/institution is connected //directly// to its `Address` and `Phone` topics via a custom association. This renders the topic network more intuitive (#779). 
    1522* Webclient usability: 
    1623    * The detail panel remembers a topic/association's vertical scrollbar position. When the user revisits the topic/association the remembered scrollbar position is restored (#783). 
    … …  
    1825    * When clicking a topic in the detail panel which has more than one association to the selected topic only one association is revealed (instead of all), nameley the one that corresponds to the clicked list entry. This reduces the chance for selecting the wrong association on the canvas afterwards (#460). 
    1926    * The sensitive area of the detail panel's resize-handle is increased from 2 pixel width to 7 pixel width (#676). 
    20     * In the //New Workspace// dialog the radio buttons to select the Workspace Sharing Mode features a tooltip which explains the respective option (#784). 
     27    * In the //New Workspace// dialog the radio buttons to select the Workspace Sharing Mode feature a tooltip which explains the respective option (#784). 
    2128* In the detail panel's "related topics" list besides the association type the association value is displayed (#793). 
    2229* DM never creates empty simple child topics. In particular a combobox menu is not extended by an empty item when the user lefts the field (e.g. "Phone Label", "City") empty (#171). 
    … …  
    3441 
    3542Changes: 
    36 * Webclient: the standard view properties `x`, `y`, and `visibility` are stored as node properties (instead as child topics) (#761). 
     43* Webclient: the standard topicmap view properties (`x`, `y`, and `visibility`) are stored as node properties (instead as child topics) (#761). 
    3744 
    3845Plugin Development Framework: 
    … …  
    4451    * REST API and declarative migrations: simplified format for create/update requests. The child topic's `type_uri` must no longer be specified (#636). 
    4552    * Core API: an Association Definition can be added in the middle of the sequence (#770). 
    46     * Orthogonality: 
    47         * //Topic references// are supported for //Composition// as well. Topic references are supported for all the 4 cases, that is composition/aggregration, one/many (#786). 
    48         * An update operation supports //topic deletion references// for composition-one and aggregation-one childs as well. Topic deletion references are supported for all the 4 cases, that is composition/aggregration, one/many (#171). 
     53    * Core API orthogonality: in a create/update operation Topic References and Topic Deletion References are supported for all the 4 cases, that is !Composition/Aggregation, !One/Many. 
     54        * Topic References are supported for //Composition// as well (#786). 
     55        * Topic Deletion References are supported for //Composition-One// and //Aggregation-One// childs as well (#171). 
    4956    * Bug fixes: 
    50         * Objects don't loose their label when updating their child topics (#766). 
     57        * Objects don't loose their label when updating their child topics (#766, #791). 
    5158        * `ChildTopics` manipulator methods work for child topics defined with cardinality //many// (#788). 
    5259        * When a type is deleted and the (then deleted) type is requested subsequently (via API) a proper "Type not found in DB" exception is raised (#765).