On Wed, 16 May 2001, Paul Rohr wrote:
>
> - C style (referenced by name)
> - P style (referenced by name)
> - explicit C properties
> - explicit P properties
> - hardwired defaults
>
> A few notes.
>
> 1. There can only be *one* relevant C style per character, and only one
> relevant P style per paragraph. Anything other than that would be chaos.
>
> 2. Note that for lookup of P properties, all of the C-level stuff can be
> ignored, so long as the UI doesn't allow you to set P-level properties for
> C-level styles. (I assume this happens already.)
>
Actually you can right now. This might make sense if a span for a
character level style extends over a paragraph break but I'm certainly
willing to be convinced para-props should not be allowed for styles.
> 3. As Martin mentions, styles can be basedon others of the same type, using
> the obvious cascading logic.
>
> 4. A style definition should, inherently, be incomplete. There's no point
> in specifying values for all properties, only the ones of interest.
>
> Finally, I should note that none of the above addresses what should happen
> in the UI when using the properties on an existing selection to define or
> update styles. I spec-ed some of the needed behavior as TODO #1 in the
> styles test document, but more work and thought is probably needed there.
>
I'll have another look at the document. The code on my harddisk gives the
current parapgraph and character properties at the cursor when one presses
"new".
Cheers
Martin
