Am Samstag, 6. Januar 2007 20:08 schrieb Bo Peng: > > - paste > > - Paste Clipboard as Lines > > - Paste Clipboard as ParagraphsSelection as Paragraphs > > - Paste Selection as Lines > > - Paste Selection as Paragraphs > > > > Are all of them still needed? Do all of them still make sense as a menu > > entry? (yes/no) > > Michael, > > I propose that we remove "paste special -> paste selection as lines" > and "paste special -> paste selection as paragraph", due to the > following reasons: > > 1. these rarely used features can be easily done by clipboards. It is > OK to provide convenient alternatives for frequently used features, > but not for these special paste modes.
What do you do if you want to paste something from an application that does not support the clipboard? middle mouse button pastes as paragraph, but as lines is only possible with the lfun. Therefore keeping this menu entry makes sense IMHO. > 2. selection, middle-button paste would better be kept as simple as > possible for users. I have not seen any other application with > selection-related menu items. > > 3. They bring confusion to novice users since there is no 'paste > selection' menu item, only the advanced/special version of it. I don't think that there would be much confusion, after all the menu is named "paste special", but I don't have a strong opinion on removing those items or not. You should IMHO try to figure out why these menu items have been implemented before removing them. > After removing these two items, "paste clipboard as lines" and "paste > clipboard as paragraph" can be renamed to "paste text as lines" and > "paste text as paragraph". The previous menu names do not make enough > distinction between 'paste (full)' and 'paste text'. If you are going to rename that you should use "plain text" instead of "text", since that is the term we use elsewhere if we mean unformatted text. That would actually be useful information. > Because UI design should be independent of implementations, I ask you > to make the decision from an user point of view. (Whether or not > remove these features from lyx itself is another matter.) We should not remove these features. The code is needed anyway, so they don't cost anything, and there is a sensible use case, see above. Georg
