Heading 1
Heading 2
Heading 3
For example,
Of course, I'd much rather make something decent looking.
And for code, etc. we have:
How do you like them apples?
Customization
Most of the styles demonstrated in this document come from the current built-in set of styles. Until we hook up the Format/Styles menu, these are the only styles you'll be able to use. However, for testing purposes, this document redefines the
TODO
1. When the user sets a style "over" existing explicit formatting, do the Right Thing. If it's a different style, nuke the explicit formatting. If it's the same, pop up a dialog and ask whether to update the style to include those properties, or just revert to the existing definition.
2. Likewise, we may want logic to avoid setting explicit properties which duplicate the underlying style.
4. Honor the
5. Allow style definitions to be added and edited. This is more significant work because, not only does it require a few rich dialogs, but we also need to efficiently reformat the document to use the new style definitions.
6. Rework styles mechanism so they can be loaded from templates, instead of always being hardwired. The current trick of overwriting built-in styles may not work in this case, especially if we want to do something like the Style Gallery, which swaps templates underneath the existing document, thereby updating all its styles.
7. Also, decide what the hardwired set of style definitions should be. Something less ugly than this would be nice.