Changes between Version 84 and Version 85 of ReleaseNotes
- Timestamp:
- 21.12.2013 18:06:33 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ReleaseNotes
v84 v85 7 7 == 2013-12-10: DeepaMehta 4.1.3 == 8 8 9 ''### to be completed'' 10 11 CHANGELOG 9 !DeepaMehta 4.1.3 brings a lot of crucial GUI improvements and a View Customization Framework (for developers). 10 11 You can update any !DeepaMehta 4.1.x installation (including 4.1) or perform a clean installation. For installation and update instructions see the [[https://github.com/jri/deepamehta#readme|README]]. 12 12 13 13 New features: 14 * ### Box Renderer (#577). 15 * ### View Customization Framework (#505). 16 * Support for complex data models, namely "Aggregated Composites". Topic/association instances can be edited via Detail Panel (#337, #30). 17 * The Apache Felix Gogo Shell is included. That enables you to e.g. start and stop DeepaMehta plugins, and even install new plugins without restarting DeepaMehta. 14 * The Topicmap Panel has a new look & feel (provided by the **Box Renderer** plugin) (#577, #505): 15 * Topics are rendered as solid boxes with a reduced-size type icon in the corner. This way the topic content takes center stage (instead of the icon). 16 * The content of Note topics is displayable right on the topicmap. Note topics have an expand/collapse handle. The goal is to increase the topicmap's information density. Don't show a proxy, but the real thing. 17 * Each topic box can have an individual color (independent of topic type). The color is set via context menu. The goal is to provide the user increased means of expression as known from graphics applications. 18 * Associations can be drawn by pulling the topic's type icon. No context menu and no Shift key is involved (although these gestures still work.) 19 * **View Customization Framework**: enables a plugin developer to customize the topicmap look & feel without the need of implementing an entire Topicmap Renderer. Instead she selectively hooks in drawing and event handling behavior and model extensions (#505): 20 * Two topic rendering flavors: a) draw on Canvas, b) render as DOM (stylable via CSS). 21 * Intercept event handling and provide custom interactions/gestures. 22 * Extend the topicmap view model with per-topic custom properties (e.g. color, shape). 23 * While loading a topicmap from DB: partially load topic ''content'' to be rendered in the topicmap. 24 * The Webclient supports complex data models, namely "Aggregated Composites". Such complex topic/association instances can be edited via Detail Panel (#337, #30). 25 * The Apache Felix Gogo Shell is included. That enables you to e.g. start and stop !DeepaMehta plugins, and even install new plugins without restarting !DeepaMehta. 18 26 19 27 GUI improvements: 20 28 * Topicmap Panel: 21 * New look & feel (provided by the Box Renderer plugin):22 * Topics are rendered as solid boxes with a reduced-size type icon in the corner. This way the topic content takes center stage (instead of the icon).23 * The content of Note topics is displayable right on the topicmap. Note topics have an expand/collapse handle. The goal is to increase the topicmap's information density. Don't show a proxy, but the real thing.24 * Each topic box can have an individual color (independent of topic type). The color is set via context menu. The goal is to provide the user increased means of expression as known from graphics applications.25 * Associations can be drawn by pulling the topic's type icon. No context menu and no Shift key is involved (although these gestures still work.)26 29 * Create topics directly on the topicmap: right-click and choose a type from the list. The topic is created on-the-spot (#529). 27 30 * Associations are displayed along with their values (as entered in the detail panel) (#34). … … 51 54 * The `CompositeValue`'s manipulator methods (`set()`, `setRef()`, `remove()`) extend the passed `Directives` (by a UPDATE_TOPIC resp. UPDATE_ASSOCIATION directive) (#576). 52 55 * Core API `Type` interface: `setDataTypeUri()` and `setLabelConfig()` take a `directives` parameter (#576). 53 * The DeepaMehta Core thoroughly uses `Lists` instead of `Sets`. One advantage is better performance (#559).56 * The !DeepaMehta Core thoroughly uses `Lists` instead of `Sets`. One advantage is better performance (#559). 54 57 * Core API: there is a new model class: `de.deepamehta.core.model.TopicReferenceModel`: A reference to a topic, either by ID, or by URI (#574). 55 58 * Core API: `DeepaMehtaObject` has a method to fetch child topics selectively: `loadChildTopics()` (#522). This is particularly useful in conjunction with a Viewmodel Customizer (#505). … … 57 60 * Client-side: 58 61 * Plugins can add icons and disabled items to the topic/association/canvas context menus (#529). 59 * DeepaMehta GUI Toolkit:62 * !DeepaMehta GUI Toolkit: 60 63 * Support for context menus (#532). 61 64 * Disabled items can be added to menus (#529). … … 93 96 * The RESTClient no longer depends on the Webclient (#557). 94 97 * The GUIToolkit menus and context menus rely on the jQuery UI Menu widget (#532). 95 * Updates(#507):98 * 3rd party components are updated (#507): 96 99 * jQuery 1.7.2 -> 2.0.3 97 100 * jQuery UI 1.8.21 -> 1.10.3