Re: [lmi] Ellipses in menus

[Greg Chicares]

On 2015-10-17 15:18, Vadim Zeitlin wrote:
> On Sat, 17 Oct 2015 13:59:48 +0000 Greg Chicares <address@hidden> wrote:
> 
> GC> I'm thinking of removing the ellipsis for
> GC>   Help | About
> GC> because its dialog is not meaningfully interactive,
> GC> 
> GC> and adding ellipses for
> GC>   File | Default...
> GC>   File | Preferences...
> GC> because theirs are.
[...]
>  No objections from me, quite the contrary.

Very recent commits:

  20151018T1611Z Assimilate documentation to actual menus
Ellipses and actual wording didn't match in a few instances. We still have
to document group roster and group quote commands, but I wanted to clean
these other things up first.

  20151018T1612Z Refactor
Removed irregularities: two File menus used as <object_ref> without
explanation, and a third written inline with explanation.

Is there a more tasteful way to do this? Ideally we'd code "File | Open"
once and only once. I speculate that I could write this once:

    <object class="wxMenuItem" name="wxID_OPEN">
        <label>_Open...\tCtrl-O</label>
        <bitmap platform="win" stock_id="wxART_FILE_OPEN"/>
        <help>Open an existing document</help>
    </object>

and use it by <object_ref> in three places, assuming that all <object>s
are equal. I don't see a simple way to write a group of menuitems and
include the group--i.e., there seems to be no <multiple_object_ref>.

  20151018T1621Z Improve ellipsis usage
As discussed previously.

>  OTOH "Preferences..." or "Options..." menu item has always used and still
> continues to everywhere and lack of it in lmi was a bit jarring, so adding
> it there is even more important than removing it from "About".

Is it jarring that three "Census | Edit" commands and "Illustration | Edit cell"
still lack ellipses? I think so. The same answer should apply to all other
document types, wherever a magnifying-glass-with-dancing-m[ae]n icon appears.

Should "Census | Print" have an ellipsis? I suspect not: it causes a number
of PDFs to be dispatched to the operating system with the mime-type "print"
verb, so any print options are handled by the default PDF application.

If a census is the currently active child document, should we enable the
"File | Page setup..." menu command? I think this should be answered the same
way as the preceding question, for the same reason.

Aside from dancing men under a magnifying glass, and OAOO refactoring of the
File menu, I think we're okay now. I'm going to postpone those things for a
moment and get the census-group-* commands added first, because those are
required for the Halloween release.