ISSUE-98: Eliminate separate clear timing from dynamicFlow

Clear timing.

Eliminate separate clear timing from dynamicFlow

State:

CLOSED

Product:

TTML 1.0

Raised by:

Sean Hayes

Opened on:

2009-05-15

Description:

I can see no justification for having separate clear timing in any of the examples from John Birch’s original documents (the only hard evidence I can find in the history trail of a design discussion). The notion of a separate clear timer seems to have been added between the March 14 draft and March 21 draft without discussion on the public list. What is more, the presence of a separate clear interval seems at somewhat at odds with the behavioral requirement.

If I have a two line caption region , and I wish to flow the text through it, with text entering at a word rate and leaving at a line rate. Then I don’t want a clear to occur until after two lines have been added, but then I want to clear the lines after each additional line is completed; which implies clear timing can’t start until the region starts to overflow, so the first clear interval needs to be extended, and after that we want the clear interval to be synchronized with the fill interval which is based on irregular length words, so a single value seems inappropriate.

In the example flow below: The first clear/reflow occurs at t14, the next at t20, then at t27 and at t33 (clear intervals of 14, 6, 7 6), then we presumably want to clear the remaining two lines to be cleared in some manner.

T01 Alice

t02 Alice was

….

t06 Alice was beginning to get very

t07 Alice was beginning to get very
tired

….

t13 Alice was beginning to get very
tired of sitting by her sister on

t14 tired of sitting by her sister on
the
…
T19 tired of sitting by her sister on
the bank and of having nothing

T20 the bank and of having nothing
to
….

T26 the bank and of having nothing
to do: once or twice she had

T27 to do: once or twice she had
peeped

T33 peeped into the book her sister
was

T34 peeped into the book her sister
was reading

Related Actions Items:

No related actions

Related emails:

1. Agenda for meeting 22-05-09 (from Sean.Hayes@microsoft.com on 2009-05-22)
2. RE: ISSUE-98 (Clear timing.): Eliminate separate clear timing from dynamicFlow [DFXP 1.0] (from Sean.Hayes@microsoft.com on 2009-05-19)
3. Re: ISSUE-98 (Clear timing.): Eliminate separate clear timing from dynamicFlow [DFXP 1.0] (from gadams@xfsi.com on 2009-05-19)
4. RE: ISSUE-98 (Clear timing.): Eliminate separate clear timing from dynamicFlow [DFXP 1.0] (from Sean.Hayes@microsoft.com on 2009-05-18)
5. Re: ISSUE-98 (Clear timing.): Eliminate separate clear timing from dynamicFlow [DFXP 1.0] (from gadams@xfsi.com on 2009-05-16)
6. RE: ISSUE-98 (Clear timing.): Eliminate separate clear timing from dynamicFlow [DFXP 1.0] (from geoff_freed@wgbh.org on 2009-05-15)
7. RE: ISSUE-98 (Clear timing.): Eliminate separate clear timing from dynamicFlow [DFXP 1.0] (from Sean.Hayes@microsoft.com on 2009-05-15)
8. RE: ISSUE-98 (Clear timing.): Eliminate separate clear timing from dynamicFlow [DFXP 1.0] (from geoff_freed@wgbh.org on 2009-05-15)
9. ISSUE-98 (Clear timing.): Eliminate separate clear timing from dynamicFlow [DFXP 1.0] (from sysbot+tracker@w3.org on 2009-05-15)

Related notes:

Display change log