VizierDB/paper-HILDA-2016-Spreadsheets
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

trimming

Browse source
This commit is contained in:
Oliver Kennedy 2016-04-25 22:08:49 -04:00
parent dfacbba7ca
commit 2ff728b22c
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
sections/interface.tex
View file

@ -61,9 +61,9 @@ flexible data and schema manipulation features of spreadsheets as possible withi
\inlineitem{Copy/Paste cells} Users can copy and paste regions of cells. The formula of the copied cell(s) is replicated in the target region, preserving the formula's positional semantics. If the target region is larger than the source, cells in the source region are tiled to scale over the entire target.\\
\inlineitem{Add/Delete/Reorder columns or rows} Users may drag or columns rows to reposition them. A tab at the bottom and right edges of the displayed table allows users to widen or lengthen the table, adding new columns or rows respectively. Finally, several interface elements allow users to insert rows (resp., columns) before or after any existing row (column).\\
\inlineitem{Sort data} A dropdown menu allows users to sort data according to values in one or more columns.\\
\inlineitem{Filter data} A dropdown menu allows users to filter out rows according to a formula defined over the row.
\inlineitem{Filter data} A dropdown menu allows users to filter out rows according to a formula defined over the row.\\
%\end{compactitem}
Many of these operations (e.g., paste, typecast) require the user to define a target region. Although commonly specified as rectangular area of cells selected by clicking and dragging with the cursor, we propose to use declarative region specifiers, discussed in greater depth below.
Many of these operations (e.g., paste, typecast) require the user to define a target, normally specified as rectangular area selected by clicking and dragging with the cursor; We also propose to support declarative regions, as discussed below.
\subsection{Spreadsheet to Notebook and Back}
To create a seamless interface between the spreadsheet and notebook interfaces, we need to map operational semantics and effects between the two interaction models. We now sketch solutions to several of the resulting challenges.