Abstract:
A method for hiding and showing spreadsheet cells of a worksheet being displayed on a computer system display means. The hiding and showing is based upon hierarchical relationships among the spreadsheet cells. This technique is implemented by first determining hierarchical relationships among cells based on cell indentation, content, and formulas. A group of contiguous cells having a common hierarchical relationship is then selected and hidden. Totals for the group of cells may then be shown in place of hidden cells. The hidden group of cells may be stored in a memory location other than main memory such as a magnetic or optical disk. The group of cells may then be retrieved from memory and shown on the display means.

Description:
This application is a continuation of U.S. application Ser. No. 07/359,678 filed on May 31, 1989, now abandoned. 
    
    
     BACKGROUND OF THE INVENTION 
     Copyright Notice 
     A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. 
     FIELD OF THE INVENTION 
     This invention relates to a method of determining hierarchical relationships among cells in a spreadsheet and more particularly a method of hiding and showing cells in a spreadsheet based on hierarchical relationships among the cells. 
     DESCRIPTION OF THE PRIOR ART 
     The most common software application used on personal computers in business is the spreadsheet. Spreadsheets are commonly used for a wide variety of applications. These include financial applications such as budgets, forecasts, income statements and balance sheets; database applications such as customer lists, sales records, personnel files, and equipment inventories. Other applications include graphics and even word processing. 
     What makes spreadsheet software so useful and widespread is its simplicity and versatility. It offers a raw two (or more) dimensional grid of cells which the user can utilize as desired. Numbers and/or words can be entered into any of the cells as desired. A wide variety of operations are then available for use with this data, such as totaling, sorting, graphing, copying, moving, word justification, and more. This combination of free-form data entry and then extensive commands for operating on the data is a powerful combination which allows spreadsheet software to be used effectively in a wide range of applications. 
     However, this flexibility also has drawbacks. By being flexible enough for use in a wide range of applications, spreadsheet software is more limited than necessary for any one application. 
     Three important limitations of spreadsheet software exist in financial applications including (1) spreadsheet data is limited to RAM which limits the size of the worksheets that users may operate; (2) large worksheets become unwieldy such that it is hard to create summary views of the worksheet for viewing, printing, or graphing; and (3) the operations offered by the spreadsheet software are ignorant of the structure inherent in financial worksheets (i.e. categories and time periods). These three limitations are discussed in more detail below. 
     A key limitation in all of the popular spreadsheet software today is that the spreadsheet data must be held in free RAM (i.e. the RAM that is left over after the operating system, the spreadsheet software, and any co-resident applications are loaded) while the worksheet is being used. In contrast to other applications such as databases and some word processors, spreadsheet software does not take advantage of disk storage to hold data that is being operated on. This is a severe limitation for users wanting to work with large spreadsheets. Currently, the only solution for users desiring more spreadsheet data space is to purchase more RAM, and then using special-purpose hardware or software called expanded memory to expand beyond DOS&#39;s 650K-byte memory limit. 
     It is the flexibility inherent in spreadsheets which requires spreadsheet data to be stored in RAM during the operation of the spreadsheet software. Because any cell can be viewed at any time and any cell can refer to any other cell in a formula, the spreadsheet software must keep all the cell contents in RAM, where the contents of each cell can be quickly accessed. Storing cell contents on disk would slow display and recalculation down to a level which users would find unacceptable. 
     The uniformity of spreadsheets (i.e. a homogenous grid of rows and columns), which contributes greatly to the flexibility and ease-of-use of the spreadsheet, becomes a negative feature as the users&#39; worksheets become large. With many rows and columns, it becomes difficult and time-consuming to find items of interest, to move around the worksheet, to rearrange it, to comprehend the data, to display or print summary data, and so forth. Also, recalculation time shows down as the spreadsheet gets larger. 
     The generality of spreadsheet software leads to the third limitation in working with financial worksheets, which is the difficulty in manipulating the worksheet. There is a certain structure to financial worksheet, which relates to the information contained within it and common operations performed on the information. Popular spreadsheet software is ignorant of this structure. This results in simple operations taking much more time than would be necessary if this financial worksheet structure or other application structures were utilized in spreadsheet functions. 
     SUMMARY OF THE INVENTION 
     The present invention provides a method for hiding and showing spreadsheet cells of a worksheet being displayed on a computer system display means. The hiding and showing is based upon hierarchical relationships among the spreadsheet cells. This technique is implemented by first determining hierarchical relationships among cells based on cell indentation, content, and formulas. A group of contiguous cells having a common hierarchical relationship is then selected and hidden. Totals for the group of cells may then be shown in place of hidden cells. The hidden group of cells may be stored in a memory location other than main memory such as a magnetic or optical disk. The group of cells may then be retrieved from memory and shown on the display means. 
     As a result of this technique, the user can increase the size of the worksheet without being constrained by the size of the computer main memory. In addition, the user can easily create a summary worksheet without duplication or loss of data while also preserving the structure of the worksheet. In a smaller or summary worksheet, it is easier to find items of interest and it is easier to understand and absorb the contents of the worksheet. Furthermore, this technique allows the user to more easily create reports and graphs with varying levels of summary or detail. 
     A further understanding of the nature and advantages of the present invention can be realized by reference to the remaining portions of the specification and the attached drawings. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS 
     FIGS. 1a-1e are screen displays of a budget worksheet; 
     FIGS. 2a and 2b are block diagrams of a computer system utilizing first and second embodiments of the invention; 
     FIGS. 3a-9d are flowcharts showing the operation of the first embodiment; and 
     FIGS. 10a-13b are structure charts showing the structure of the first embodiment. 
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 
     User View 
     A first preferred embodiment of the present invention is a technique for showing and hiding sections of the worksheet corresponding to different hierarchies within the worksheet. This process referred to is hereinafter referred to as spreadsheet outlining. By showing or hiding different levels of detail and totals within the worksheet, the user can easily create different summary views of the worksheet, all within the same single worksheet. The user may hide rows to create a summary view by row category and/or hide columns to create a summary view by time period. This is much simpler, easier, faster, and reliable than creating multiple versions with formulas and links between versions. Similarly, in a three dimensional spreadsheet, the user may hide across the third dimension (and so forth for an n-dimensional spreadsheet). 
     FIG. 1a shows a screen displaying a portion of a budget worksheet. The user may hide a portion of the budget such as the detail rows under Payroll as shown in FIG. 1b. The user may hide the entire Monthly Expenses category rows as Shown in FIG. 1c or several portions of the Monthly Expenses category rows as shown in FIG. 1d. In addition, the user may hide or compress the monthly totals columns as shown in FIG. 1e. 
     By hiding sections of a worksheet, then showing sections of interest at a time, the user works with a smaller worksheet. As a result, it is easier to find items of interest, the worksheet is easier to understand and absorb, summary reports can be printed directly from the displayed worksheet, and the worksheet may recalculate faster. 
     In the first embodiment, hidden data may be moved off the worksheet. It can be moved to a variety of places, including to a disk drive, to an unused portion of the spreadsheet, or to other storage devices. Alternative embodiments may also move the data to RAM or simply suppress the display of the data without moving it. 
     When a category is hidden, the totals for that category remain on the worksheet. Typically, a financial worksheet will have a row with a category label, followed by detail lines, followed by a total line for that category, (e.g., see Payroll in FIG. 1a). 
     When hiding Payroll in FIG. 1a, the first embodiment moves the detail rows (Holly, Jim, Stan, Audrey) and the overscore out of the worksheet. If the data is being moved out of the spreadsheet entirely (e.g. to disk) and the total line contains formulas to calculate the totals, the first embodiment records the total formulas and replaces the total formulas with just the total numbers themselves. The total numbers are then moved up to the category label row (next to Payroll). The total label (&#34;Total Payroll&#34;) is the moved off the worksheet. The result is shown in FIG. 1b. When the hidden data is later reshown, the process is reversed and the total formulas are reinserted. When hiding columns to show only the totals of higher-level time periods (e.g. hiding months to show only quarter and year totlas), if the totals were not already present in the worksheet, the first embodiment calculates them and then treats them as if they were. Alternative embodiments may also calculate totals for rows. 
     Moving the hidden data to a disk drive or other storage device provides the benefit of freeing the RAM that was used for that data, releasing it for use by other data. This allows the worksheet to grow beyond the size of RAM. That is, hidden portions of the worksheet reside on disk, while the un-hidden portions remain in RAM. To view the portion on disk, the user requests that the hidden portion be &#34;shown&#34;. This has the effect of moving the hidden portion from disk to RAM for reinsertion in the spreadsheet. If there is not enough RAM to hold the data to be shown, the user is prompted to select another category of data to be hidden on disk. 
     It is Spreadsheet Outlining which allows portions of the worksheet to be moved to disk. The reason it is not done generally with spreadsheets is that they do not have enough structure to make intelligent decisions about which data can be moved to disk without being needed for display or formula recalculation. However, implicit in Spreadsheet Outlining is knowledge about which data is to be viewed and which is to be hidden at any given time. This removes the need to keep the data in the spreadsheet for display purposes. And when data is hidden, Spreadsheet Outlining replaces the total formulas referring to the hidden data with just the total numbers. This can be done because with the data hidden it cannot be changed and therefore the totals will not change until the data is re-shown. This removes the need to keep the data in the spreadsheet for formula recalculation. 
     Spreadsheet Outlining has additional capabilities for manipulating financial worksheets. A re-organization facility allows the user to point to a category title, point to where it should be put in the worksheet structure, and then have it automatically moved to the indicated place. All subsidiary rows are moved with the category title and no further spreadsheet operations such as inserting or deleting blank rows are necessary. 
     Operational View 
     The first embodiment exists within the context of an Electronic Spreadsheet (initially Lotus Development Corporation&#39;s 1-2-3). Such a spreadsheet is characterized by the ability to store data (numbers, text-labels, formulas) in cells organized in a two dimensional matrix in memory (a spreadsheet). In the existing implementation, the host spreadsheet program maintains and displays the data, and the first embodiment is responsible for extending the host&#39;s command set and functionality to implement outlining and storage of hidden data on disk. Alternatively, the outlining and storage of hidden data on disk could be integrated with the spreadsheet program to create a second preferred embodiment offering all these functions. 
     FIG. 2a is a block diagram showing the first embodiment within a computer system 100. The first embodiment (hereinafter referred to as Bud) 102 resides with a host spreadsheet program 104 in a computer 106. Both the first embodiment (Bud) and the host handle communications from a keyboard 108 and a disk 110. However, only the host handles communications to a display screen 112. 
     FIG. 2b is a block diagram showing the second embodiment within computer system 100. The second embodiment is an Integrated Spreadsheet Outliner 114 having all the functions of the first embodiment and the host spreadsheet program described above. However, there are efficiencies of implementation by combining the two programs. 
     General Functionality 
     The functionality involved is the ability to analyze data on the spreadsheet in order to discover hierarchical organizations of data which can then be manipulated so as to give the appearance of hiding and showing groupings and sub-groupings of data. Data manipulation consists of combinations of: moving data to/from remote regions of the spreadsheet, moving data to/from secondary storage media (typically magnetic disk drives), setting hidden column attributes, and introducing new data representing summary information calculated from the original data. 
     BUD is implemented as an add-in product for Lotus 123. In this environment the first embodiment receives control at several points. The user may invoke Bud by pressing a certain key sequence. This causes a routing to display a menu allowing the user to select an action such as hiding rows, showing rows, or setting the column detail display level. These commands will then be dispatched to the appropriate routines. 
     FIGS. 3a and 3b show the process when a previously saved worksheet file is loaded by the host spreadsheet. Bud will first open a previously saved companion file (step 200). The companion file has the same name as the worksheet file, but with a different extension (.bud). If there is no companion file (step 202), Bud will examine the sheet for Bud specific information (Step 204). If tag formulas indicating hidden rows stored to disk are detected (step 206), Bud will initialize a swap file (step 208) and display a &#34;lost hidden data&#34; message (step 210). If the file is found (step 202), and there is on-disk storage (step 212), Bud will copy the companion file to a swap file (step 214), read the linkage information (step 216), and free list information (step 218), and truncate the swap file to hidden data (step 220), before closing the companion file (step 222). 
     FIG. 4 shows the process when a worksheet file is saved by the host spreadsheet. Bud will be notified so that it may save a companion file. If on sheet storage is used (step 230), Bud only writes some basic header information with house keeping into the companion file (step 232). If on-disk storage is used (step 230), the swap file is copied to the companion (steps 234 and 236), linkage information and free-list information is written (steps 238 and 240) before closing the companion file (step 242). 
     Determining Row Hierarchy 
     Hierarchical groupings are determined in two distinct ways, one for each axis of the spreadsheet matrix. 
     A row group consists of a &#34;parent&#34; row, subsidiary &#34;children&#34; rows below it, and possibly a total row below the children. A row group is determined primarily from the relative indentation of data within a row. A row&#39;s indentation is determined by scanning from left to right until a non-blank cell is encountered. If this cell is textual, then the number of leading spaces in the text is considered low-order indentation information. That is, a whole column of indentation is always more significant than any number of leading spaces. Rows of greater indentation are considered to be &#34;owned&#34; or grouped under preceding rows of lesser indentation. If no indentation is used or it is ambiguous, labels and formulas are also examined. If line has a label beginning with the literals &#34;Tot&#34; or &#34;sub&#34; and ends with the literal that comprises the parent row&#39;s row header (the label in the leftmost cell in the row), then that row is a total line which concludes the group. Similarly, if a row is encountered which contains a formula totaling from the parent row to that row, it is considered to be a total line for that group and therefore concludes the group. 
     The indentation of a row is determined by the GetLevel routine whose flowchart is given in FIGS. 5a-5b. In a first step 250, column and indentation variables are initialized. The cell at (row, col) is examined (step 252). If cell is blank, col is incremented (step 254) and tested against the maximum column scanning limit (step 256) to control looping. The column scanning limit is the right most column used by the user unless the user specifies a different column. If the cell is non-blank (step 252) and contains text (step 258), the text is retrieved. A loop is used to count the number of leading spaces in the text (steps 258, 260, 262, and 264). The level information is encoded as 256 times the column indentation plus the count of leading spaces (step 266). 
     The discovery of row ownership is done through the ScopeForward routine whose flowchart is given FIGS. 6a-6e. The variable row begins with the value of the row to be scoped. If the initial row already has hidden rows (step 270), there is no further scope (step 272). If the initial row does not already have hidden rows, then the level information and label of the parent row are recorded for later comparison (step 274). Any initial blank rows are skipped (step 276). The IndentRow and TotalRow variables are initialized (step 278). These variables represent the furthest scoped rows due to indentation detection and to summary total formula detection respectively. The row indentation level is then calculated (step 280). If the row is a blank row (step 282), the blank count is incremented (step 284) and if past a threshold value (step 286), the main scoping loop is terminated. If the row is outdented from the parent row (step 288), the scoping loop is terminated. If the row is the first row (step 290), then the indScope flag is set based the indentation of this first row (step 292). If indent scoping is active (step 294), the current row level is compared against the parent row level (step 296). If the current row indented, IndentRow is advanced to current row (step 298), otherwise indentation scoping is de-activated (step 300). If indentation scoping is deactivated (step 294), an indented row will flag subsequent termination of the scoping loop (steps 302 and 304) If the row contains a total label that matches the value text of the parent&#39;s label (step 306), the scope is determined to reach the current row (step 308). If the label does not match (step 306) and there is a summary formula present (step 310), the formula is examined. If the formula refers to cells prior to the parent row (step 312), the scoping loop is terminated. Otherwise, TotRow is advanced to the current row (step 314). The current row variable is then incremented (step 316) and tested for row scanning limits before continuing the main scoping loop (step 320). Upon completion of the main scoping loop (off page connector A), the greater of the IndentRow and TotalRow values is used to determine the scope of the parent row (steps 322, 324, 326 and 328). 
     Determining Column Hierarchy 
     Column-wise hierarchies are determined by the relationship of column header cells to the time based groupings: month, quarter, and year. There are no &#34;owner&#34; columns, but there will be total columns which represent summary data for columns to the left of the respective total columns, based on the time periods included in the total. For example, there may be a column for &#34;Year 1988&#34; which is the total for the 12 previous columns representing data for &#34;January 88&#34; through &#34;December 88&#34;. 
     The SetColLevel routine handles column wise hierarchy scanning and detail level control as given in FIG. 3f. The level of detail display is supplied by the user. Columns are first fully expanded by looping over all columns (steps 330-340). Each column is shown by turning off the &#34;hidden&#34; attribute (step 334). If the column is a temporary total (step 336), it is removed and scanning continues with the next column which will now be at the temporary&#39;s index. Otherwise, the column index is incremented (step 340) to continue showing columns. After the columns are fully expanded, the column scanning information is then reinitialized (steps 342, 344). The columns are again examined from left to right with a loop (344-360). Each pass through the loop will use a routine to find the next set of columns which are contained in the same period as the current column. If the last column spanned is a total (step 350), it is refreshed (step 352). Otherwise, a temporary total column is inserted (step 354 and the next column variable is incremented (step 356). All the spanned columns (but not the last one) are then hidden (step 358), and the current column is advance to the next column (step 360) after the span. 
     Hiding Rows 
     Groups are hidden in response to commands issued by the program operator. The flow chart for the hide rows operation is given in FIG. 3g. 
     First, rows are examined sequentially starting from the current row to determine which rows belong to the group to be hidden (step 370). This involves examining indentation levels, labels, and formulas, as described above in &#34;Discovering Groups&#34;. If no rows are discovered to be owned by the current row (step 372), no action is taken (step 374). 
     Once the rows in the group are discovered, then the formulas of all rows must be examined to determine if they reference data that is about t be hidden (removed) from the spreadsheet (step 376). References to the total line, if present, are allowed, as this data will remain available. If invalid references are discovered (step 378), the hide operation is disallowed (step 380). 
     The physical manipulation of data now occurs. There are two storage options available in this implementation: on-sheet remote storage, and off-sheet disk-storage (step 382). 
     If on-sheet, memory availability is first calculated (step 384) and examined (step 386). If memory is available, the hidden row data is moved to a special reserved area of the spreadsheet matrix. First, exchange parent&#39;s and total line&#39;s label, if present (steps 388 and 390). This is because the total line will remain on the worksheet, but without the detail showing, the relevant label is that of the parent. Then move interior detail lines (and parent line if total present) to reserved area (step 392). Move subsequent lines (and total line) up to cover area vacated by interior lines (step 394). Finally, install a linkage formula in column A (step 396) to connect the visible line (parent or total, as appropriate) to the hidden rows. This linkage formula causes a plus-sign to appear in the reserved spreadsheet column. 
     If off-sheet (step 382), a group linkage record is allocated (step 398), parent and total line&#39;s labels are exchanged (steps 388 and 390). Interior detail lines are transferred by writing the contents of each cell sequentially to the disk file area allocated. As each line is successfully written (steps 400-402), a row locator record is allocated and linked to the list of row locators from the group linkage record (steps 404, 406, 408). If a total line is present (step 410), save the total line to the disk file and replace its formulas with constants representing their current values (steps 412-414) before covering hidden areas (step 394). The linkage formula in Column A (step 396) contains the ID number of a group-record which is linked to the list of row-records made in steps 400-410. If an error is encountered when writing hidden lines to disk (step 402 or 414), the hide operation is undone by releasing allocated file space (step 416), freeing group and row locator records (step 418) and re-exchanging the parent and total labels (steps 420, 422). 
     Showing Rows 
     Hidden groups may be shown in response to commands given by the program operator. This is the inverse operation to hiding rows and when successful will restore the spreadsheet to the appearance it had before the hide operation. Referring to FIG. 3b, the row is examined for presence of linkage formula in the first column (step 426). If there is no linkage, there is no hidden data (step 428). Calculate number of hidden rows and memory requirements (steps 430 and 432). If there is insufficient memory (step 434), allow user to hide other rows or terminate the show operation (see Swapping below) (steps 436, 438, 440, 442, 444 and 446). Open blank area on sheet by moving subsequent rows down (step 448). If on-sheet move hidden row data into newly opened area (steps 450, 452). If on disk, follow row-record links sequentially from group record and sequentially read cell contents from disk swap file (steps 456, 458, and 460). If total line present, exchange parent&#39;s and total&#39;s label (steps 462 and 464). If off-sheet storage, read total line&#39;s formulas from final hidden row record (steps 466 and 468). Release all disk storage allocated to the lines displayed (step 472) and free the group and row-locator records (step 474). Remove linkage formula from column A (step 476). 
     Swapping 
     The hierarchical organization of rows gives the program operator a convenient grouping for swapping spreadsheet data in and out of limited memory. With off-sheet storage, memory is reclaimed when groups are hidden. This enables the creation of spreadsheets larger than the central memory capacity of the computer. 
     For a spreadsheet larger than memory, the entire sheet may not be displayed at one time. It is possible that there will not be enough memory available to execute a show command. When this occurs, the program will allow the operator to point at an alternative group to hide. The program will hide the alternative group and then re-attempt the original show command (carefully keeping track of the shifting of row data due to hide operations). This loop will continue until the show operation succeeds or the operator terminates the command. 
     Hiding and Showing Columns 
     Columns are hidden or shown based on a request to homogeneously display data at a given time-based interval: months, quarters, years, or all-data. When hiding columns, data is not physically transferred, rather the hidden-column attribute of the host spreadsheet program is manipulated to prevent display of the desired columns. Temporary columns may be introduced to display summary (total) data for groups of columns. 
     1) Scan column headers left to right noticing when a break from one unit at the appropriate interval to the next occurs. 
     2) If the last column for a group is not a total for the interval, move subsequent columns right one column and install labels and formulas calculating the totals. 
     3) Install a special formula in the top row for the total column which records whether it was temporarily installed and displays as a plus-sign. 
     4) If a temporary total column whose interval level doesn&#39;t match the display level of the current command is found, remove it by moving columns to the right of this column left one column. That is, if quarter totals are being shown and a temporary month total is encountered, remove it. 
     5) Set the hide/show attribute of each column based on the interval levels. That is, if showing by quarters, hide specific day and month columns, show quarters and years. 
     Reading and Writing Spreadsheets 
     When hidden rows are stored off-sheet, there is a swap file maintained to hold the hidden data. When a normal spreadsheet Save or Retrieve command is executed, this swap-file must be transferred to/from a companion file with a common name component with the spreadsheet file. In addition the group-records, row-records, and free-space allocation list must be written to/from this companion file. 
     FIGS. 10a-13b are a structure chart of Bud. Each block represents a module or routine that is executed to perform a function. A block has a blackened upper right corner if the module is repeated elsewhere in the structure chart. A block has a shadow if it is shown in more detail in another drawing. It will be understood that in FIGS. 10a-13b, a calling module includes a function call to another called module if the calling module (e.g. PutRow 538) is shown above and pointing to the called module(s) (e.g. OpenStream 542, PlaceCell 544, and PlaceTag 536). Each of the modules is briefly described below in Appendix A. 
     A program listing of the first embodiment is given in Appendix B. The program code is written in the C language for Borland&#39;s Turbo C compiler for the IBM Personal Computer. 
     The invention has now been described with reference to specific embodiments. Other embodiments will be apparent to those of ordinary skill in the art. If is therefore not intended that this invention be limited, except as defined in the appended claims. ##SPC1##