Daniel Lohmann <[EMAIL PROTECTED]> writes: > Jean-Marc Lasgouttes wrote: >> Daniel Lohmann <[EMAIL PROTECTED]> writes: >> >>> As we are already on it :-) >>> >>> It also would be really nice, if >>> >>> 1) there is an opportunity to specify the *default* display for *new* >>> inset, preferably even customizable per inset-type. >>> >>> 2) the document-specific state of each inset would no longer be stored >>> in the document file (fancydoc.lyx), but in some extra settings file >>> (such as fancydoc.lyxrc). >>> (It is kind of annoying to get version control conflicts just because >>> of the fact the me and my colleagues prefer different ways to display >>> the insets on screen.) >> >> When people are beginning to ask for a brand new user interface for >> such a minuscule feature, something is wrong. What about a tooltip >> on the closed button instead?
> Do you really consider a team-work-feasible document format (in the > sense that it can be managed with tools such as svn or cvs) a > "minuscule feature" and an indicator for "something is wrong"? I just > can't believe that. Sorry, my comment was a bit harsh and short. My point was: - intended effect: have the contents of a closed float be visible when it is closed. - means: provide 3 levels of display for each inset (3 radio buttons); provide a default for new insets (3 radio buttons) configurable by inset types (one combox). I think that trying to solve this (real) problem by way of 7 different UI elements (and associated support code and file format extension) is a case of overengineering. I did not mean minuscule as "not useful", but as "we should be able to get it right without configuration". Note that I was not at all addressing the part 2) above, which is also a different and orthogonal problem. I do not think that anybody has a really good solution to this problem, actually. > Maybe I have not explained myself well enough. I am mainly asking for > separation of concerns between the document content and the > editor-ui-related data associated with it, which is IMHO a good design > principle anyway. As I wrote above, I was commenting about the other one. I am sorry that I was not very clear. > Character styles, however, are another story. I use them very > extensively, but had to learn that their default display style (with > label) is -- for me -- very distracting. It consumes too much space > and my eyes always stumble across the labels. So I tend to fold > them. I am not sure that having settings for each and every preference of users (a la Emacs or KDE) is the best way to go. > Another thing with the display of character style insets is that they > are not stored within the document in 1,4.x. This means that I have to > fold them every time I re-open the document, a fact I am actually glad > about; otherwise the frequency of svn conflicts would go up > significantly, which is the (practical) reason for the request for > separating content from ui-data on the file system. It would be nice to achieve, but not easy at all IMO. And with some documents (for example docs), we have ideas on how we want insets to be toggled or note when we distribute the file. JMarc
