Changes between Version 46 and Version 47 of ReleaseNotes
- Timestamp:
- 21.12.2012 01:05:16 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ReleaseNotes
v46 v47 12 12 * Server-side HTML generation with Thymeleaf templates (#365). 13 13 * 3rd-party components are updated, most notably Neo4j 1.2 -> 1.8 (#350). 14 * A different storage aproach for the Access Control information brings back the performance known from pre-4.0.12 (#344). 14 15 15 16 New Features: … … 17 18 18 19 GUI Improvements: 20 * Cluster move: Moving an association moves the visually connected subnetwork (#327). 19 21 * More informative page panel: topics which are already visible on the canvas are displayed with an disabled icon. This provides a useful hint when revealing topics (#308). 20 22 * Differentiated gestures for revealing topics via the page panel: a) clicking the topic's icon reveals it, b) clicking the topic's label reveals ''and'' focuses it (#387). 21 * When the user changes an association's type the form is updated immediately. New fields are displayed on the spot. The user must no longer leave and re-enter the form (#347). 23 * Page panel: associations are grouped by type, using the association type names as group headers (#256). 24 * When the user changes an association's type the form is updated immediately. The user must no longer leave and re-enter the form (#347). 25 * Once association is created Edit mode is entered automatically (#314). 22 26 23 27 Improvements: 28 * A different storage aproach for the Access Control information brings back the performance known from DM 4.0.11 and before (#344). 24 29 * Better support for virtual host environments: the new config property `dm4.host.url` allows the admin to specify the installation's public URL. This is relevant for plugin's which make use of `DeepaMehtaUtils.isDeepaMehtaURL()` or the Files API's `getRepositoryPath()` [a9ffcf77]. 30 * Data model: Meta Types are applicable as child types in association definitions (#363). 25 31 26 32 Bug Fixes: 33 * Handle transitive plugin service dependencies (#351). 34 * Redeploy the Core while active HTTP sessions exist (#299). 27 35 * Edit meta type view configuration via REST API (#378). 28 36 29 37 Plugin Development Framework: 30 * A plugin consumes services by annotation. The ''consumedServiceInterfaces'' setting in `plugin.properties`is no longer required (#367).31 * A plugin's provided service is automatically picked up by the Core. The ''providedServiceInterface'' setting in `plugin.properties`is no longer required (#368).38 * A plugin consumes services by annotation. The ''consumedServiceInterfaces'' config property is no longer required (#367). 39 * A plugin's provided service is automatically picked up by the Core. The ''providedServiceInterface'' config property is no longer required (#368). 32 40 * Flexible REST resources registration: a plugin which provides no Root Resource can still provide JAX-RS provider classes [2b464811]. 41 * Client-side load mechanism for auxiliary scripts: scripts located in `script/helper/` are loaded synchronously ''before'' the plugin is loaded (#372). 42 * The "association" part of a RelatedTopic is serialized (#266). 43 * Refactored internal object fetch/store code (#340). 33 44 * 3 new core events: `PreUpdateAssociation`, `PostUpdateAssociation`, `IntroduceAssociationType` [654d9c7b][3645932c]. 34 * Data model: Meta Types are applicable as child types in association definitions (#363). 35 * Client-side load mechanism for auxiliary scripts: scripts located in `script/helper/` are loaded synchronously ''before'' the plugin is loaded (#372). 45 * New client-side event `option_topics` allows filtering selection lists (comboboxes and checkbox lists) (#345). 36 46 37 47 ----