One more thing: I’m pretty sure there were changes done to TLF in develop after I forked the code, so this changes will need to be merged in.
On Oct 5, 2014, at 10:53 PM, Harbs <harbs.li...@gmail.com> wrote: > I just committed my work on tables to the repository. I committed it to a new > branch called tables. There’s still work to be done before it can be merged > with develop. Here’s a summary of the status: > > 1) There are NO unit tests. I have not run any existing test nor have I > created any new tests. I have zero experience with tests. I’ll be happy to do > some work on this, but I will need direction. > 2) Markup will probably not work. All my testing with the code has been > creating elements directly. > 3) There are no Operations that currently work correctly with tables, so Undo > with tables is a no-no. > 4) I have made changes to SelectionManager, and there’s now a concept of > nested TextFlows and nested SelectionManagers/EditManagers. Text in table > cells are nested TextFlows rather than children of the main TextFlow. > 5) ParagraphElements can now contain more than a single TextBlock. > Substantial work has been done to support this. > > A quick summery of what features are supported: > > 1) While it’s possible to specify header and footer cells, they are > ineffectual. > 2) Cells spanning columns work, but ones spanning rows do not. > 3) Multiple cells can be selected, but the must be contiguous ranges. > 4) It’s possible to get the selection of cells from the parent EditManager. > 5) All basic cell formatting is supported (strokes, fills, inset, etc.) > 6) No stroke/fil patterns are supported. If you need alternating fills for > example, they must be specified directly. > 7) Fixed height and expanding height cells are supported. All cells must have > a fixed width. > > That’s more or less what comes to mind right now. I will be committing any > fixes to the tables branch from now on. I’ll try to document as much as I can > somewhere… ;-) > > Harbs
