"R. Lahaye" wrote:
> File->New // Collapse New and New_from_template.
> // Use "invalid" filename; when saved, call 'Save as...' automatically.
> // Should a window popup ask for Template/Class or assume a default for
>that?
> Open // Collapse Open and Import. Open according to file extension:
> // .lyx, .tex, .txt, .nw, .doc are opened as you expect.
> // Does ASCII (*.txt) input need a Lines/Paragraph popup?
I all of a sudden realize that part of this discussion might have
to deal with the widgets that popup when selecting a menu item.
For example, in the File->Open/New/Template issue I would like
to emphasize the following ambiguity in the current actions of
these entries:
1) "New": apart from doing a real "New",
I also can open an existing document, by just selecting it
in the file list, which is strictly spoken an "Open"
action and has nothing to do with "New"!
2) "New from template: apart from opening a new file w/ new template,
I once again can also open an *existing* document, which
has nothing to do with "New from template".
3) "Open": apart from opening an existing document, I also can just
type a new file name and so do basically a "New" instead.
Hmmm, to me this looks like every entry is designed as a sort of
failsafe:
if you hit the wrong entry you still can do what you wanted to do.
Personally I find this confusing and I believe it lacks common sense
logic (consequently: documentation is needed to explain what menu
buttons do).
Ideally, a menu entry does (only) what "the man in the street" expects
it should do. In that case you can reduce a lot of the menu documentation
in Gnu-plot style: "This menu entry does what you expect it does".
Regards,
Rob.
