Changes between Version 58 and Version 59 of ReleaseNotes

Timestamp:

09.03.2013 23:34:13 (12 years ago)

Author:

jri

Comment:

4.1 release notes, pt. 2

ReleaseNotes

@@ -16 +16 @@
 * Encoded passwords are not visible in the webclient (#375).
 * More complex searches for composite topics: you can e.g. search a person by its entire name. And you can search Persons or Institutions by combined Address terms (#420).
+* More familiar wording of Core concepts: "Parent/Child" replaces "Whole/Part". This benefits both, API and GUI (#67).
+* For developers: the Neo4j Shell can be launched while DeepaMehta is running [3601ae4a].
 
 Bug fixes:
+* The admin user can change hers password (#369).
+* A User Account is editable only by a) the respective user, and b) by the creator of the User Account (#375).
+* View Configuration default values are reflected in the GUI. In particular the "Viewable", "Editable", and "Rows" settings are no longer changed by accident (#208).
+* View Configurations of the standard types, e.g. Person, can be edited via GUI (#377).
 * Association types get Workspace assignments (analogous to topic types) (#376).
 * Search topics and Webpage topics show no "Edit" button (#259, #248).
@@ -24 +30 @@
 
 Plugin Development Framework:
-* The core classes CompositeValue and CompositeValueModel provide convenience accessors which take a "defaultValue" argument (#418).
+* The core class `CompositeValue` is attached to the DB. So, for complex update operations of composite topics/associations the developer must not care about model updates vs. DB-updates. The underlying model and the DB are always in-sync automatically. `CompositeValue` is now on-par with all the other Core objects (#339).
+* The core classes `CompositeValue` and `CompositeValueModel` provide convenience accessors which take a "defaultValue" argument (#418).
 
 ----