Changes between Version 6 and Version 7 of TEXT_PERFORMANCE_R0

Timestamp:

05/14/10 15:20:36 (15 years ago)

Author:

kyli

Comment:

--

TEXT_PERFORMANCE_R0

@@ -34 +34 @@
 
 = Design =
- What should the test measure:
+What should the test measure:
+
  * Insert a large text in s frame (like a paste will do);
  * Simulate pressing left / right arrows (navigation);
@@ -44 +45 @@
  * write some more chars in the text.
 
- The test will extend SystemTestBase, since it is the only testbase that starts the whole app. Thus we will be able to take in mind other factors like halo menus. It will perform these things and print the result in milliseconds. Unnecessary modules will not be started (alternative skin, for example). All the measurements will be placed in one test case, since starting the app for every case will be very slow.
+The test will extend SystemTestBase, since it is the only testbase that starts the whole app. Thus we will be able to take in mind other factors like halo menus. It will perform these things and print the result in milliseconds. Unnecessary modules will not be started (alternative skin, for example). All the measurements will be placed in one test case, since starting the app for every case will be very slow.
+
+Create class SelectionInfo, which will hold the mark and caret positions. It will be immutable, 2 private final int fields - mark and caret. A default constructor will be provided, as well as getters for the mark and caret indices. Also, generated hashcode() and equals() and public static SelectionInfo DEFAULT = new SelectionInfo(-1, -1) (values are same to the current default values for the mark and caret);
+
+In BaseTextModel, delete mark() and caret(), instead create private RwProp<SelectionInfo> selectionInfo(), with a default value of SelectionInfo.DEFAULT.
+
+Replace getMark() and getCaret() with getSelectionInfo(). Replace setMark() and setCaret() with setSelectionInfo(). I think the purpose of these methods is clear, as is their usage. 
+
+
+
+