Changes between Version 2 and Version 3 of ConceptLocks

Timestamp:

04/07/09 11:19:27 (16 years ago)

Author:

rostanin

Comment:

--

ConceptLocks

@@ -13 +13 @@
    1. One is allowed to add relations to a concept locked by another user
    1. One is allowed to edit an unlocked concept that is in a CM locked by another user
-   1. CMs should get a flag "dirty" if a concept in it was changed by another source (e.g. in a infoItems cockpit or VV)
+   1. If a concept in a CM was changed by another source (e.g. in a infoItems cockpit or VV)
       1. User has to get a signs that concepts were changed
          1. e.g. some symbol displayed as a concept icon
          1. If user opens such a concept it has to be refreshed from the server
          1. Flex-application should send "refresh"-requests periodically to get informed about changed concepts
+   1. All read-only CMs should get a flag "dirty" if the editing user saved/closed it
+         1. e.g. some symbol displayed
+         1. User can refresh the CM contents from the server
+         1. User can request a CM lock if the editing user closed the CM
+         1. Flex-application should send "refresh"-requests periodically to get informed about changed CMs
+   1. If a concept map is closed, CM locks must be removed
+      1. If the application is closed, all user's CM and concept locks must be removed
+         1. What to do if the the browser crashed?
+   1.