Individual topicmaps/topics can be addressed via webclient URLs. To jump into a particular topicmap: http://localhost:8080/topicmap/2204 To jump into a particular topicmap and display a particular topic of that map: http://localhost:8080/topicmap/2204/topic/2512 Browser compatibility: the permalinks work in all browsers. However, to see the address bar's location change *while you navigate* (and for functional back and forward browser buttons) Firefox 4, Safari 5, or Chrome is required. Note: the "topicmap" URL query parameter is not supported anymore. Use the new URL format instead. Close ticket 106.
Note: draging'n'dropping files from arbitrary locations (in particular different Windows drives) collides with the concept of a single-rooted file repository (as realized by the proxy module). For the moment on Windows drag'n'drop operations are only supported from the C: drive (actually the drive DM is started from). See ticket 91.
The original problem was that DM's file related features didn't work if and only if DM was running behind an Apache reverse proxy. What we've learned: 1) Apache decodes URLs before passing the request to the backend application! As a consequence Jersey's default pattern for matching the request's path segments ([^/]+?) does *not* match if the URL contains encoded slashes (e.g. when a path is encoded *within* a path segment). This caused Jersey to respond with 404. The solution was to use a custom pattern (.+) for Jersey. 2) By default Apache doesn't allow encoded slashes in URLs at all! Such URLs are refused with a 404. The solution was to modify this behavoir by the means of Apache's AllowEncodedSlashes directive. Thanks to JuergenN and Silke for helping to track things down! Close ticket 107.
3rd try to fix a 404 issue in conjunction with a reverse proxy setup. Change regex for POST /files/folder requests. See ticket 107.
2nd try to fix a 404 issue in conjunction with a reverse proxy setup. Now we flush the response stream. See ticket 107.
To set a background image for a topicmap: 1) Reveal the Topicmap topic (e.g. via the "Associations" listing). 2) Create a File topic corresponding to the image file (either via file browser or via drag'n'drop). 3) Associate the topicmap with the file. 4) Retype the association to "Aggregation". Make the topicmap the "Whole" and the file the "Part". To choose another background image for a topicmap: 1) Proceed as described above. 2) Reactivate the previous background image (e.g. by retyping the association to "Association"). That's it basically. However, for the moment there are a lot of issues: - To actually see the map background you have to reload the client (http://localhost:8080/) - The background appears only after a forced map refreshing (e.g. by moving it a little) - IMPORTANT: there must be only *one* background image per map. Otherwise the map gets corrupted. So, the "Reactivate" step (2) above is crucial. See ticket 103.
The browser's back/forward buttons steps through the history of selected topics and topicmaps. Each topic/topicmap has a unique URL which appears in the browser's address bar. Firefox 4, Safari 5, or Chrome is required. Basically it works. A lot of issues remain, e.g. - when topics are deleted history gets corrupted - selected associations are not included in the history - when stepping back beyond the history begin an error occurs - the displayed URL does not actually work yet (permalink feature) For developers there are 3 new webclient hooks: - pre_push_history() - pre_pop_history() - post_reset_selection() See ticket 106.
Topic label rules can be configured interactively. A label rule is bound to a topic type. Subject to label rules are *complex types*. (Simple types need no rule: the topic's value IS its label.) To edit the label rule: 1) Reveal a complex topic type. 2) Press "Edit". You see the topic type's immediate child types displayed as boxes. 3) To choose which child types to include in the label select the respective "Include in Label" checkboxes. 4) Bring the child types in the desired order by vertically moving the boxes. 5) Press "Save". Hints: - Once a label rule is changed the existing topic instances are *not* adjusted. To apply the new rule select the topic, press "Edit" and then "Save". Applying a changed rule to *all* existing topic instances might be a future feature. - There is only *one* child type sequence: the order by which the child types are rendered in the content panel is the same order that is used to construct the label. Maintaining 2 individual sequences (content panel rendering vs. label construction) might be a future feature. - Label rules are cascading. The "Person" type e.g. is configured to use the "Person Name" type as the label. The Person Name type in turn is configured to use "First Name" AND "Last Name" as the label. So, consider all hierarchy levels when defining a label rule. - If there is no label rule defined (that is all "Include in Label" checkboxes are deselected) the former default rule applies: use the first simple type found by a depth-first traversal. See ticket 41.
Try the Contact's module Person topic type. Still missing: interactive label configuration. See ticket 41.
See ticket 90.