On Fri, Mar 15, 2013 at 01:09:45PM +0100, Kai Labusch wrote: > As a first step, it would be sufficient for our purposes, if the extension > could specify the color of a smart-tag. > > Would it reduce your concerns that the patches would give to much control to > the extension if we remove the possibilty to specify the line type?
IMO it's fine if the smart tag extension specifies both underline color and style, but the application code, before applying it, should check that the settings do not overlap with the other settings for spell and grammar checking, and in case the smart tag extensions overlaps with the other settings, apply some default. Here the priority is the user experience: the user should clearly distinguish the different markups. > However, I already heared some complaints that the smart-tags are not visible > enough. In other editor applications, we change the background color of > the text in order to make the problems more visible. You could implement something similar to the fields shading, may be also a more detailed mouse-over hint in the tooltip (see void SwEditWin::RequestHelp(const HelpEvent &rEvt) ), etc. etc. There are place for improvement in the current implementation (always taking take that Writer is supposed to be WYSIWYG editor, so all these visual hints should be configurable). Regards -- Ariel Constenla-Haile La Plata, Argentina
pgpSsyDXnGWvD.pgp
Description: PGP signature
