Le 16 août 07 à 14:36, Jean-Marc Lasgouttes a écrit :
Mael Hilléreau <[EMAIL PROTECTED]> writes:
Of course, but as it is a presentation issue, it can be fixed later.
I would rather advocate to use character properties in current code
and switch to insets-as-character-properties later. Any text longer
than one of two words put in such an inset will be ugly.
Then many things are already ugly, e.g. charstyles :) Storing a
spellchecker setting into a character or font is senseless, whereas
an inset is designed for functional purposes. Providing spellcheck
control has nothing to do with possibilities in terms of appearance,
even though I admit that presentation could be improved once provided
by an inset class. But clearly, appearance is _not_ the main needed
functionality. The real problem you mentioned may be that insets do
not provide as many display schemes as needed. New schemes would be
useful for other purposes as well, e.g. for charstyles; however
that's not a reason for putting charstyles properties into a font.
Moreover, I don't know if you very often need to mark as non
spellchecked more than one or two words (I mean outside e.g. a note)?
Not me, that's not very usual. That's why I think that this solution
is acceptable for now.
In addition, there's currently some interesting work from Martin,
JMarc and Richard on charstyles, layouts and insets (notably
InsetCollapsable). Hopefully, once this is done, the way towards a 3-
box-drawing presentation scheme will be more clear.
This work is unrelated to 3-box insets.
Ok. As 3-box is a way to display insets, I thought that this could
have consequences on how it will be managed.
Mael.
