OK, but that means that when a paragraph has multiple styles, we end up
with the following structure:
Paragraph
Span
Textsome styled text/Text
/Span
Textunstyled text/Text
Span
Textmore styled text/Text
/Span
/Paragraph
And we don't currently support Span in TextAreaSkin.
I'm
OK, but that means that when a paragraph has multiple styles, we end up
with the following structure:
Paragraph
Span
Textsome styled text/Text
/Span
Textunstyled text/Text
Span
Textmore styled text/Text
/Span
/Paragraph
Right. This is similar to how it would work in HTML:
Hi
Greg, are you particularly attached to having font styling in the
Element class? The way the code is working out, it's going to be a lot
simpler if I push font styling attributes down into the TextNode
class.
In particular, line breaking in the skin becomes a lot simpler (at the
moment it
I'd prefer to keep it in Element, for a couple of reasons:
1) It allows sub-nodes to inherit the styles.
2) A TextNode is simply meant to represent a run of text independent of
styling. It should determine any and all styles from its parent (generally
either a Paragraph or a Span).
G
On Jun
