OK, good luck. The only concerned that occurred to me is that it could make import/export trickier. Will you always unwrap the paragraph from around the table or could there be situations in the future, like if you do allow inline tables, where you will have to guess whether to unwrap or not.
-Alex On 6/10/14 11:53 AM, "Harbs" <harbs.li...@gmail.com> wrote: >Coming from InDesign, it does not seem so hacky to me. That’s how >InDesign handles tables. > >Extending Paragraph has its own set of issues. A paragraph is expected to >have a TextBlock which represents the text as the children within the >paragraph. That does not work well with cells. If the table is a child f >the paragraph, that should not be a problem. > >There’s actually an advantage to have table be a child of a paragraph. It >could theoretically be composed inline to text on the same line as other >span text ― although I’m not planning on doing that at this point. > >Harbs > >On Jun 10, 2014, at 7:58 PM, Alex Harui <aha...@adobe.com> wrote: > >> >> >> On 6/10/14 1:20 AM, "Harbs" <harbs.li...@gmail.com> wrote: >> >>> This seems to be working well. >>> >>> Next problem: >>> >>> https://github.com/Harbs/TLF-Table-Work/issues/29 >>> >>> TLF assumes in quite a few places that all leaves belong to a >>>paragraph. >>> If tables can be siblings of paragraphs (as it stands now), this will >>>not >>> work. >>> >>> I¹m thinking of requiring tables to be children of paragraphs. I cannot >>> think of any obvious problems with this. Anything obvious that I¹m >>> missing? >> >> Bummer. Seems hacky, but no real objections. Did you consider making >> Table extend Paragraph? >> >> -Alex >> >
