9 | | One main aspect of this release is to revoke the **Performance** loss introduced in !DeepaMehta 4.0.12 in conjunction with Access Control. !DeepaMehta 4.0.13 uses a different approach to store the access control information and returns to the old performance. Further highlights include: **Geomaps** are a new topicmap type that display geo-related topics on a [[http://www.openstreetmap.org/|OpenStreetMap]]. An **Association Type Editor** let the user create custom association types. Furthermore, a whole bunch of GUI changes improves usability e.g. through **Cluster Moves** and more informed **Topic Revelation**. |
10 | | |
11 | | Of interest for administrators of a client-server !DeepaMehta installation might be the new [[http://karaf.apache.org/|Apache Karaf]]-based !DeepaMehta distribution. This makes it easy to run !DeepaMehta as a daemon process and to access via a remote shell. So, starting from version 4.0.13 !DeepaMehta comes in 2 flavors: the known "Standard Distribution" which focuses on small download size and easy setup for single users and the **Karaf Distribution** for client-server setups. |
12 | | |
13 | | !DeepaMehta 4.0.13 is ready for **server-side HTML generation** based on [[http://www.thymeleaf.org/|Thymeleaf]] templates. So, along with single-page AJAX applications, the !DeepaMehta plugin/application developer can choose between 2 architectural styles. To start with server-side HTML generation install the external [[https://github.com/jri/dm4-webactivator|DeepaMehta 4 Web Activator]] plugin. |
14 | | |
15 | | Several improvements in the !DeepaMehta framework simplify the life of plugin developers, in particular when listening to events and providing/consuming services. Last but not least several 3rd-party components are updated, most notably [[http://www.neo4j.org/|Neo4j]] 1.2 -> 1.8 |
16 | | |
17 | | Updating from previous !DeepaMehta versions is not supported.\\ |
| 9 | One main aspect of this release is to revoke the **Performance** loss introduced in !DeepaMehta 4.0.12 in conjunction with Access Control. !DeepaMehta 4.0.13 uses a different storage approach for access control information and thus returns to the old performance. Further highlights include: **Geomaps** are a new topicmap type for displaying geo-related topics on an [[http://www.openstreetmap.org/|OpenStreetMap]]. A graphical **Association Type Editor** let the user create custom association types. Furthermore, a whole bunch of GUI changes improves usability e.g. through **Cluster Moves** and more informed **Topic Revelation**. |
| 10 | |
| 11 | Of interest for administrators of a client-server installation is the new [[http://karaf.apache.org/|Apache Karaf]]-based !DeepaMehta distribution. This makes it easy to run !DeepaMehta as a daemon process and to access it via a remote shell. Starting from version 4.0.13 !DeepaMehta comes in 2 flavors: the known "Standard Distribution" which focuses on small download size and easy setup for single users and the **Karaf Distribution** for client-server setups. |
| 12 | |
| 13 | Furthermore, !DeepaMehta 4.0.13 is ready for **server-side HTML generation** based on [[http://www.thymeleaf.org/|Thymeleaf]] templates. So, along with single-page AJAX applications, the !DeepaMehta plugin/application developer can choose between 2 architectural styles. To start with server-side HTML generation install the external [[https://github.com/jri/dm4-webactivator|DeepaMehta 4 Web Activator]] plugin. Please note: while being functional, this plugin is in an very early state. |
| 14 | |
| 15 | Several improvements in the !DeepaMehta framework further simplify the life of plugin developers, in particular when listening to events and providing/consuming services. Last but not least several 3rd-party components have been updated, most notably [[http://www.neo4j.org/|Neo4j]] 1.2 -> 1.8. |
| 16 | |
| 17 | Updating from previous !DeepaMehta versions is not supported. |
| 18 | |
25 | | * Karaf Distribution (#349). |
26 | | * Association Type editor: let the user create custom association types. The color is configurable on a per-type basis. Simple and complex association types are supported (analogue to topic types) (#48). |
27 | | * Association instance editor: let the user enter data for an association instance according to the association's type definition (#335). |
28 | | * For developers: server-side HTML generation with Thymeleaf templates (#365). |
| 26 | * Apache Karaf-based Distribution for easy client-server setup and maintenance (#349). |
| 27 | * Association Type editor: Allows the user to create custom association types. The color is configurable on a per-type basis. Simple and complex association types are supported (analogous to topic types) (#48). |
| 28 | * Association instance editor: Let the user enter data for an association instance according to the association's type definition (analogous to topic types) (#335). |
| 29 | * For developers: Server-side HTML generation with Thymeleaf templates (#365). |
32 | | * 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). |
33 | | * 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). |
34 | | * Page panel: associations are grouped by type, using the association type names as group headers (#256). |
| 33 | * 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). |
| 34 | * 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). |
| 35 | * Page panel: Associations are grouped by type, using the association type names as group headers (#256). |
73 | | * Client-side load mechanism for auxiliary scripts: scripts located in `script/helper/` are loaded synchronously ''before'' the plugin is loaded. This allows e.g. several renderers to share common code (#372). |
74 | | * New client-side event `option_topics` allows filtering selection lists. Applies to both, comboboxes and checkbox lists (#345). |
75 | | * Webclient API: the Topic's and Association's `composite` property contains true `Topic` objects (formerly plain !JavaScript objects) and thus enables the use of the Topic API [3105fee2]. |
| 74 | * Client-side load mechanism for auxiliary scripts: Scripts located in `script/helper/` are loaded synchronously ''before'' the plugin is loaded. This allows e.g. renderers to share a common base class (#372). |
| 75 | * New client-side event `option_topics` allows filtering the selection lists. Applies to both, comboboxes and checkbox lists (#345). |
| 76 | * Webclient API: The Topic's and Association's `composite` property contains true `Topic` objects (instead of plain !JavaScript objects) and thus provides access to the client-side Topic API [3105fee2]. |