From: Akihiko Odaki <akihiko.odaki@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Christian Schoenebeck" <qemu_oss@crudebyte.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Cameron Esfahani" <dirty@apple.com>,
"qemu Developers" <qemu-devel@nongnu.org>,
"Roman Bolshakov" <r.bolshakov@yadro.com>,
"Will Cohen" <wwcohen@gmail.com>
Subject: Re: [PATCH v6 11/15] ui/cocoa: Add Services menu
Date: Sat, 19 Feb 2022 02:49:55 +0900 [thread overview]
Message-ID: <CAMVc7JWuwTLsP__A33wBGsf7QFstuEuP1JAdJOtxdW9y-W0YWQ@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA89pP021OxJM9pqivmTHWAjSSHGkNoGAJYB77OH1RpRyg@mail.gmail.com>
On Sat, Feb 19, 2022 at 2:33 AM Peter Maydell <peter.maydell@linaro.org> wrote:
>
> On Tue, 15 Feb 2022 at 08:26, Philippe Mathieu-Daudé via
> <qemu-devel@nongnu.org> wrote:
> >
> > From: Akihiko Odaki <akihiko.odaki@gmail.com>
> >
> > Services menu functionality of Cocoa is described at:
> > https://developer.apple.com/design/human-interface-guidelines/macos/extensions/services/
> >
>
> I tested this, and while it does create a Services menu, none of
> the items in it seem very relevant to QEMU (on my machine, there's
> Activity Monitor, Time Profile Active Application, and some other
> software-development related things). In fact, every app I looked
> at exposed the same list of things in the Services menu. So I'm
> not sure why this is even an application-specific menu that needs
> specific code to support, rather than something system-wide that
> Apple automatically adds to the UI where it wants it.
>
> -- PMM
Actually I wanted to use those services from Xcode to debug QEMU. I
have no idea why Apple decided to do it this way, but an application
template from Xcode does the same although it uses an interface file
instead of Objective-C code.
Regards,
Akihiko Odaki
next prev parent reply other threads:[~2022-02-18 17:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 8:02 [PATCH v6 00/15] host: Support macOS 12 Philippe Mathieu-Daudé via
2022-02-15 8:02 ` [PATCH v6 01/15] MAINTAINERS: Add Akihiko Odaki to macOS-relateds Philippe Mathieu-Daudé via
2022-02-15 8:02 ` [PATCH v6 02/15] configure: Allow passing extra Objective C compiler flags Philippe Mathieu-Daudé via
2022-02-18 18:08 ` Akihiko Odaki
2022-02-15 8:02 ` [PATCH v6 03/15] tests/fp/berkeley-testfloat-3: Ignore ignored #pragma directives Philippe Mathieu-Daudé via
2022-02-18 18:09 ` Akihiko Odaki
2022-02-15 8:02 ` [PATCH v6 04/15] hvf: Use standard CR0 and CR4 register definitions Philippe Mathieu-Daudé via
2022-02-15 8:02 ` [PATCH v6 05/15] hvf: Make hvf_get_segments() / hvf_put_segments() local Philippe Mathieu-Daudé via
2022-02-15 8:02 ` [PATCH v6 06/15] hvf: Remove deprecated hv_vcpu_flush() calls Philippe Mathieu-Daudé via
2022-02-15 8:02 ` [PATCH v6 07/15] block/file-posix: Remove a deprecation warning on macOS 12 Philippe Mathieu-Daudé via
2022-02-18 18:11 ` Akihiko Odaki
2022-02-15 8:03 ` [PATCH v6 08/15] audio/coreaudio: " Philippe Mathieu-Daudé via
2022-02-18 18:26 ` Akihiko Odaki
2022-02-15 8:03 ` [PATCH v6 09/15] audio/dbus: Fix building with modules on macOS Philippe Mathieu-Daudé via
2022-02-15 8:03 ` [PATCH v6 10/15] ui/cocoa: Remove allowedFileTypes restriction in SavePanel Philippe Mathieu-Daudé via
2022-02-18 18:28 ` Akihiko Odaki
2022-02-15 8:03 ` [PATCH v6 11/15] ui/cocoa: Add Services menu Philippe Mathieu-Daudé via
2022-02-15 16:38 ` Will Cohen
2022-02-18 17:33 ` Peter Maydell
2022-02-18 17:49 ` Akihiko Odaki [this message]
2022-02-18 18:18 ` Christian Schoenebeck
2022-02-15 8:03 ` [PATCH v6 12/15] ui/cocoa: Do not alert even without block devices Philippe Mathieu-Daudé via
2022-02-15 8:03 ` [PATCH v6 13/15] ui/cocoa: Fix the leak of qemu_console_get_label Philippe Mathieu-Daudé via
2022-02-15 8:03 ` [PATCH v6 14/15] lcitool: Refresh Philippe Mathieu-Daudé via
2022-02-15 8:03 ` [PATCH v6 15/15] gitlab-ci: Support macOS 12 via cirrus-run Philippe Mathieu-Daudé via
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMVc7JWuwTLsP__A33wBGsf7QFstuEuP1JAdJOtxdW9y-W0YWQ@mail.gmail.com \
--to=akihiko.odaki@gmail.com \
--cc=dirty@apple.com \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.com \
--cc=r.bolshakov@yadro.com \
--cc=wwcohen@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).