List item change to depend on TextRun

[basjan]

Following the issue #230 I have changed the inheritance of ListItem. It now inherits from TextRun, such that it behaves as a container. It is now possible to provide inline formatting of a ListItem.

@ivanlanin: I already appologize for not having my branch full in sync. I am still struggling with Eclipse, Egit and GitHub. I am able to start with a fully synced branch, but when changes are merged in the upstream branch, while I am coding, I am getting out of sync.
Still searching the web for a good tutorial :/

[ivanlanin]

Good proof of concept, @basjan. Our next release is 0.11 (#225), which is a minor version, that will have to maintain compatibility. This changes will break compatibility, i.e. current code using addListItem will produce error because the arguments are changed. So, I can't merge this pull now.

I suggest to create a new element with a different name, e.g. ListRun, and keep ListItem intact. We can merge this two element on 1.0 (#81).

[basjan]

Thanks. I will take a look at it. It does indeed sounds logical if you have Text and TextRun, to also have ListItem and ListItemRun.

[basjan]

Just for my thoughts: A Text element, when added to for example a section, creates in fact a TextRun element with a single Text element inside. This behaviour is in fact a short-cut for first creating a TextRun and adding a single Text element.

The current ListItem element behaviour could also be considered a short-cut for creating a TextRun of a 'special ListType' and adding a single Text element.

When you follow this line of thoughts, then the new element should be named ListItemRun as it will create only a TextRun of the 'special ListType'. Thus ListItemRun extends TextRun. (as was already done in the proof of concept).