| Title: | Online Bookbuilding |
| Notice: | This conference is write-locked: see note 1.3. |
| Moderator: | VAXUUM::UTT |
| Created: | Fri Aug 12 1988 |
| Last Modified: | Mon Jul 15 1991 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 440 |
| Total number of notes: | 2134 |
Hi -
One thing that's been bugging me is that popup tables longer than a
windowful break according to (I'm guessing) hardcopy page-size, not
according to window-size. So a new table title line appears in the
middle of the screen, and the table continues.
I thought I had found a way out of this by including
<TABLE_ATTRIBUTES>(keep), which does, in fact, work in many cases.
But I have come across one longish, formal table that produced an
"exceeded memory capacity" error with the <TABLE_ATTRIBUTES>(keep) tag.
When I deleted the <TABLE_ATTRIBUTES>(keep), my document compiled fine.
But then, of course, the table paging (or should I say windowing?)
online looked awful.
Is there another fix I should be using besides
<TABLE_ATTRIBUTES>(keep)?
[By the way, I generally conditionalize the <TABLE_ATTRIBUTES>(keep)
for online so that it doesn't apply to the hardcopy version.]
Thanks,
Kate
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 275.1 | TPDOC::FARINA | Wed Feb 07 1990 13:53 | 5 | ||
Kate, this is something that's been bothering me, too. It really looks
awful. Does anybody have anything for us?
Susan
| |||||
| 275.2 | why paginate tables | RAGMOP::UTT | Thu Feb 08 1990 13:20 | 22 | |
Kate,
Yes, you're right. Formal tables *are* paginated much like hardcopy
tables. They *do* have to be paginated or we'd get tex-out-of-memory
errors all over the place. I could have suppressed the repeating
headers, but after much discussion among the development team and
local writers, we decided to leave them in. In a very long table,
the column heads will scroll off the window, which could make the
table very hard to read. If the heads repeat, you never have to scroll
back very far, if at all, to get a reminder about what data is in
which column. I think the ideal solution would be to have a stationary
column heading window at the top of the popup and for the table data
to scroll beneath it. This, however, would require Bookreader
functionality and other things are higher on the list at the moment.
(Note that the functionality could get somewhat complex to accommodate
table units and so on in very complicated tables.) So, a better
solution for tables is on the list but it's not very high on the list
at the moment.
Thanks,
Mary
| |||||
| 275.3 | DECWET::OSHEA | Kate O'Shea | Thu Feb 08 1990 13:36 | 10 | |
Thanks for the explanation, Mary. I agree with you completely that
having the table heads repeated is helpful. I just wish they'd appear
at the top of each successive window instead of somewhere randomly in
the middle. [I like your idea about a stationary heads bar at the top
and the table scrolling by underneath.]
I'll wait and hope for better table functionality as time goes on.
:-)
Kate
| |||||
| 275.4 | <ONLINE_CHUNK> might help??? | ATSE::KNIGHT | Fred Knight | Mon Feb 12 1990 17:25 | 9 |
I have found an interesting fact with informal tables. The <ONLINE_CHUNK> tag causes the table headers to be repeated. It was said that this tag had no visible effect, but I can see that it in fact does have a visible effect. I don't know however what the impact is in formal tables. You might give it a try, and see if it provides you with control over where the headers show up. Fred Knight | |||||
| 275.5 | No, don't try it | CLOSET::UTT | Mon Feb 12 1990 18:03 | 5 | |
The tag does not work in formal tables, and I believe the documentation
says not to use <online_chunk> in formal elements. (If it doesn't, it
should! :-)
Mary
| |||||