Rename old tq methods that no longer need a unique name

1 files changed, 13 insertions, 13 deletions

diff --git a/kspread/DESIGN.html b/kspread/DESIGN.html
index 31059876..11184218 100644
--- a/kspread/DESIGN.html
+++ b/kspread/DESIGN.html
@@ -22,7 +22,7 @@ and the source code itself.</p>
 
 <h2>Document/View Architecture</h2>
 
-<p>tqStatus: IN PROGRESS.</p>
+<p>Status: IN PROGRESS.</p>
 
 <p>MVC (Model/View/Controller) means that the application consists of three
 big parts, the <i>Model</i> which holds the data structure and objects,
@@ -49,7 +49,7 @@ to some extent he can take most part of the KSpread back-end and glue a new
 user interface around the code.</p>
 
 <h2>Dependency Handling</h2>
-<p>tqStatus: IN PROGRESS.</p>
+<p>Status: IN PROGRESS.</p>
 
 <p>When a cell holds a formula, then it is likely that it depends on other
 cell(s) for calculating the result. For example, if cell A11 has the formula
@@ -181,7 +181,7 @@ and the dependency manager will do the rest. In addition, this gives us
 recursive dependency calculation at almost no cost.</p>
 
 <h2>Manipulators</h2>
-<p>tqStatus: PLANNED.</p>
+<p>Status: PLANNED.</p>
 
 <p>Currently, every operation on a cell or on a range of cells is quite complex.
 You need to ensure correct repainting, recalculation, iterate on a range and so on.</p>
@@ -218,7 +218,7 @@ below.</p>
 accomplish this.</p>
 
 <h2>Selection handling</h2>
-<p>tqStatus: PLANNED</p>
+<p>Status: PLANNED</p>
 
 <p>The selection shall be an instance of some RangeList class,
 or however we want to call it - this will contain a list of
@@ -227,7 +227,7 @@ more entries. This will allow easy implementation of CTRL-selections and so,
 because thanks to manipulators, each operation will automatically support these.</p>
 
 <h2>Repaint Triggering</h2>
-<p>tqStatus: PLANNED</p>
+<p>Status: PLANNED</p>
 
 <p>As mentioned above, the interface between the core and the GUI needs to be kept
 at minimum. Also, the number of repaints needs to be as low as possible, and repaints
@@ -255,7 +255,7 @@ the manipulators that derive from it, so that it knows whether it changed
 cell's content or formatting.</p>
 
 <h2>Formula Engine</h2>
-<p>tqStatus: FINISHED.</p>
+<p>Status: FINISHED.</p>
 
 <p>This formula engine is just an expression evaluator. To offer better
 performance, the expression is first compiled into byte codes which will
@@ -472,7 +472,7 @@ token right before the percent. If yes, then the following code is generated:
 
 <h2>Value</h2>
 
-<p>tqStatus: FINISHED.<br>
+<p>Status: FINISHED.<br>
 </p>
 
 <p>to be written.</p>
@@ -480,7 +480,7 @@ token right before the percent. If yes, then the following code is generated:
 <h2>Commands Based on KCommand<br>
 </h2>
 
-<p>tqStatus: IN PROGRESS.</p>
+<p>Status: IN PROGRESS.</p>
 
 <p>Until lately, to implement undo and redo, KSpread creates corresponding
 KSpreadUndo classes for each action and runs them when the user undoes
@@ -492,12 +492,12 @@ hence we should be able to undo/redo every operation (provided that the
 corresponding manipulator provides methods to store/recall the undo information).</p>
 
 <h2>Cell Storage</h2>
-<p>tqStatus: PLANNED.</p>
+<p>Status: PLANNED.</p>
 
 <p>Cells are grouped together, and then hashed.</p>
 
 <h2>Format Storage</h2>
-<p>tqStatus: PLANNED.</p>
+<p>Status: PLANNED.</p>
 
 <p>Formatting specifies how a cell should look like. It involves font
 attributes like bold or italics, vertical and horizontal tqalignment,
@@ -589,7 +589,7 @@ be in more than one leaf in the quad-tree. <i>Details on the possible use of
 quad-tree or other methods should be explored further more</i>.</p>
 
 <h2>Default Toolbars</h2>
-<p>tqStatus: IN PROGRESS.</p>
+<p>Status: IN PROGRESS.</p>
 
 <p>Relevant mailing-list threads:</p>
 
@@ -652,7 +652,7 @@ Borders, Background, Foreground</li>
 </ul>
 
 <h2>Test Framework</h2>
-<p>tqStatus: IN PROGRESS.</p>
+<p>Status: IN PROGRESS.</p>
 
 <p>Relevant mailing-list threads:</p>
 
@@ -704,7 +704,7 @@ test cases.</p>
 </p>
 
 <h2>Coding Style</h2>
-<p>tqStatus: IN PROGRESS.</p>
+<p>Status: IN PROGRESS.</p>
 
 <p>(to be written in details).</p>