Subject: Re: Topic: Tables and 1.0
From: Leonard Rosenthol (leonardr@lazerware.com)
Date: Sun May 06 2001 - 17:26:57 CDT
At 12:55 AM 5/7/2001 +1000, Martin Sevior wrote:
>I am not currently thinking about a mini-document. I think a table could
>be represented in our piecetable as:
OK...
>1. Overall sub-class of a section strux - TableStrux. It has a list of
>properties describing the overall table including: Number of rows, number
>of columns. Which cells span multi-rows and multi-columns. Maybe other
>properties to describe if the table floats in the text or has fixed
>position on a page.
OK, but...
>2. After the Table strux entry comes the cell struxes. These have
>properties like location in the table (xn - xm, yn - y-m), horizontal or
>vertical size. It carries the ID associated with the table.
I'm confused. Why are number of rows/columns tracked in the
table, but their size is in the cell? And is this size the CURRENT size or
the defined size (ie. if the user said that he wanted a cell width==20%,
what gets stored - the 20% or the actual resolution of that value)? And if
that info is in each cell, that potentially means a LOT of iterating of
cell data to compute cursor, etc. locatons.
Also, what about cell attributes & formatting info (text
alignment, background color, borders, etc.)? And are tab stops relative to
a cell or relative to the page?
Something else to consider. If allow cross-cell selection (ie.
some text in one cell and some text in another), what happens when you then
hit "Backspace"?
>We will extend these manipulations to allow cell strux changes
>(populate/change/insert/delete) these map to CallSectionLayout.cpp
>
>and table strux changes (populate/change/insert/delete) these map to
>TableSectionLayout.cpp.
What about attribute information (see above)?
LDR
This archive was generated by hypermail 2b25 : Sat May 26 2001 - 03:51:03 CDT