Liviu Andronic wrote: > On Fri, Jul 10, 2015 at 11:23 AM, José Matos <[email protected]> wrote: >> On Thursday 09 July 2015 23:19:07 Liviu Andronic wrote: >>> Perhaps we should consider renaming it to something like: "Child >>> Document (TeX or LyX)"? >>> >>> Liviu >> >> Note that a child document can also be a programming listings or any >> other file to be included verbatim. :-) >> > Absolutely, yet our naming is so terse so as to prove confusing.
Yes, it is confusing. The reason why the menu items are as they are is the implementation in three different insets: Include inset, graphics inset and external inset. However the functionality of those insets overlaps, and there is a very old plan to get rid of the graphics inset in favour of the external inset. We need some volunteers;-) > Maybe > we need a tooltip there, or a status message appearing when hovering > the item, or something else. Otherwise people simply won't really know > what that item is supposed to do, or worse assume that LyX is unable > to do this at all (when it does!). I know RTFM would be one way to > approach this, but maybe there is something we can do to ease > confusion... Say, and yet another shot in the dark: "Include Child > Document (.tex, .lyx, etc.)" I guess it should be possible to rework the menu items independently of the insets, but I hjave no good idea myself. Georg
