History behavior - Revision history

Ted: /* Tool history management */

2007-03-27T05:17:07Z

‎Tool history management

Ted: /* Tool history management */

2007-03-27T05:14:41Z

‎Tool history management

Ted: /* Compliant Solution/Behavior */

2007-03-27T04:20:27Z

‎Compliant Solution/Behavior

Peter gummer: /* Recording */

2007-02-08T04:42:52Z

‎Recording

Peter gummer: /* Recording */

2007-02-08T04:42:16Z

‎Recording

Peter gummer: /* Recording */

2007-02-08T04:41:39Z

‎Recording

Peter gummer: /* Recording */

2007-02-08T04:31:29Z

‎Recording

Ted: /* Recording */

2007-02-08T02:41:17Z

‎Recording

Ted at 06:36, 2 February 2007

2007-02-02T06:36:40Z

Ted at 05:14, 2 February 2007

2007-02-02T05:14:50Z

@@ Line 23: / Line 23: @@
 == Tool history management ==
-Four tools provide history management. They are Class, Feature Relation, Diagram and Dependency. Internally there is a stand alone history manager working for each tool.
+Four basic tools and customized tools provide history management. The basic tools are Class, Feature Relation, Diagram and Dependency. Internally there is a stand alone history manager working for each tool.
 === Recording ===
 The history manager records a stone (an object representing a cluster, class, feature, etc.) after any of the following actions, unless the stone being processed is the same as the active one:

@@ Line 33: / Line 33: @@
 === Back and Forth ===
-* Choosing an class entry from the list of address bar that belongs to a class based tool or choosing a feature entry from the list of address bar that belongs to a feature based tool will navigate to the stone in current tool. No entry is added in current tool, but possible entry is recorded in other tools if "propagate stone".
+* Choosing an class entry from the list of address bar that belongs to a class based tool or choosing a feature entry from the list of address bar that belongs to a feature based tool will navigate to the stone in current tool. No entry is added in current tool, but possible entry is recorded in other tools if "link tools".
-* Choosing a class entry from the list of address tool that belongs to a feature based tool does no effect to current tool, but the class is delivered to class based tools if "propagate stone" and possible entry is recorded in those tools.
+* Choosing a class entry from the list of address tool that belongs to a feature based tool does no effect to current tool, but the class is delivered to class based tools if "link tools" and possible entry is recorded in those tools.
 * Clicking "Back" or "Forth" is relatively simply because of the unity of stones in history managers. These behaviors only function on current tool.
 === Removal ===

@@ Line 40: / Line 40: @@
 * When the active stone is not the last one in the history, a recording behavior, before a real extending, removes all elements after the active stone.
 === Compliant Solution/Behavior ===
-* In order to keep similar behavior to EiffelStudio5.7, a new preference, "tools.context_tool.propagate_stone" is added. Upon a True value when a tool receives a stone, it propagate the stone to the rest of history managed tools who will extend their own history if needed. Otherwise, the tool simply decide which tool the stone should go and deliver it.
+* In order to keep similar behavior to EiffelStudio5.7, a new preference, "interface.development_window.link_tools" is added. Upon a True value when a tool receives a stone, it propagate the stone to the rest of history managed tools who will extend their own history if needed. Otherwise, the tool simply decide which tool the stone should go and deliver it.
 = Conclusion =
 * Advantages: Independent history management on each tool that make life clearer; More Class/Feature relation tools are possible in the future; Try to be smart per user demand and does not break much behaviors against EiffelStudio5.7.
 * Disadvantages: Would confuse the user, especially when all tools are pulled off, they looks independent but actually sometimes are connected.

@@ Line 8: / Line 8: @@
 == Main editor history management ==
 === Recording ===
-The history manager records a stone (an object representing a cluster, class, feature, etc.) after any of the following actions, unless the processing stone is the same as the active one:
+The history manager records a stone (an object representing a cluster, class, feature, etc.) after any of the following actions, unless the stone being processed is the same as the active one:
 * After clicking on a node of the feature tool or cluster tool.
 * After picking a cluster, class or feature from anywhere in EiffelStudio and dropping it onto a main editor, a main editor tab or some place where a new tab editor is created to load the stone.

@@ Line 25: / Line 25: @@
 Four tools provide history management. They are Class, Feature Relation, Diagram and Dependency. Internally there is a stand alone history manager working for each tool.
 === Recording ===
-The history manager records a stone (an object representing a cluster, class, feature, etc.) after any of the following actions, unless that the stone being processed is the same as the active one:
+The history manager records a stone (an object representing a cluster, class, feature, etc.) after any of the following actions, unless the stone being processed is the same as the active one:
 * After picking a cluster, class or feature from anywhere in EiffelStudio and dropping it onto the Class, Feature Relationship, Output, C Output, External Output, Error, Warning, Diagram or Dependency tools.
 * After entering a class or feature in the address bar available on the Class, Feature Relation, Diagram and Dependency tools.

@@ Line 25: / Line 25: @@
 Four tools provide history management. They are Class, Feature Relation, Diagram and Dependency. Internally there is a stand alone history manager working for each tool.
 === Recording ===
-* The history manager records a stone (an object representing a cluster, class or feature etc.) after the following behavior except that the processing stone is the same as the active one.
+The history manager records a stone (an object representing a cluster, class, feature, etc.) after any of the following actions, unless that the stone being processed is the same as the active one:
-* Pick a cluster/class/feature from anywhere in EiffelStudio and drop onto tools including Class, Feature Relationship, Output, C Output, External Output, Error, Warning, Diagram and Dependency.
+* After picking a cluster, class or feature from anywhere in EiffelStudio and dropping it onto the Class, Feature Relationship, Output, C Output, External Output, Error, Warning, Diagram or Dependency tools.
-* Enter a class/feature in the address bar available on tools of Class, Feature Relation, Diagram and Dependency.
+* After entering a class or feature in the address bar available on the Class, Feature Relation, Diagram and Dependency tools.
 * The recording takes place in a functioning tool which is chosen and activated by the PND or address entering behavior (or all tools needed, See Compliant Solution/Behavior). The activation behavior follow this default rule: a class stone activates a Class tool, a feature stone activates Feature Relation tool.
-* There are basically two kinds of history managed tools, one is class based tool, Class, Diagram and Dependency, and the other is feature based tool, Feature Relation. A class based tool only records class stones (not feature stones any more). And a feature based tool only records feature stones.
+* There are basically two kinds of history managed tools: the class based tools (Class, Diagram and Dependency), and the feature based tool (Feature Relation). A class based tool only records class stones (not feature stones any more); and a feature based tool only records feature stones.
 * In feature relation tool drops or enters in address bar a class that contains a feature A with the same name as current feature B, this class stone will be treated as a feature stone A.

@@ Line 2: / Line 2: @@
 = Overview =
-This article presents history managements of the main editors and various tools in EiffelStudio 6.0 with docking. The goal is to discuss and clarify the history behaviors.
+This article focuses on history managements of the main editors and various tools in EiffelStudio 6.0 with docking. The goal is to clarify the history behaviors, and the implementation should follow this requirement. Here we do not discuss history management tool specific, i.e. history of diagram operations and history of metric calculations.
 = Behaviors =
 == Main editor history management ==
-=== Record ===
+=== Recording ===
-=== Back and forth ===
+* The history manager records a stone (an object representing a cluster, class or feature etc.) after the following behavior except that the processing stone is the same as the active one.
-=== Remove ===
+* Click on a node of the feature tool and cluster tool.
 == Tool history management ==
-=== Record ===
+Four tools provide history management. They are Class, Feature Relation, Diagram and Dependency. Internally there is a stand alone history manager working for each tool.
-=== Back and forth ===
+=== Recording ===
-=== Remove ===
+* The history manager records a stone (an object representing a cluster, class or feature etc.) after the following behavior except that the processing stone is the same as the active one.
-=== Relationship among various tools ===
+* Pick a cluster/class/feature from anywhere in EiffelStudio and drop onto tools including Class, Feature Relationship, Output, C Output, External Output, Error, Warning, Diagram and Dependency.