https://bugs.documentfoundation.org/show_bug.cgi?id=87714
Heiko Tietze <tietze.heiko@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needsUXEval |difficultyInteresting,
| |easyHack, needsDevEval
CC|libreoffice-ux-advise@lists |tietze.heiko@gmail.com
|.freedesktop.org |
--- Comment #13 from Heiko Tietze <tietze.heiko@gmail.com> ---
(In reply to Yousuf Philips (jay) from comment #11)
Maybe the simplest thing is to show the Open With list of the particular
image type provided my the OS.
The default graphics editor is defined on Windows at
HKEY_CLASSES_ROOT\SystemFileAssociations\image\shell\edit\command but there
isn't such an export variable or the like in Linux. The info for the Open With
menu is extracted from <app>.desktop at /usr/share/applications or
~/.local/share/applications/ where MimeType defines for what file type this
program is applicable. Not sure how macOS handles this task but likely in the
same way.
Putting all together I think Cor's suggestion from comment 9 is the easiest way
- and perhaps a nice easyhack with a higher difficulty. Ideally we get a
command .uno:ExternalEditor, which is disabled when the option is not set. It
opens the program parametrized with the internal image. That could be tricky.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 87714] CONTEXT MENU: Better integration with image editing apps · bugzilla-daemon
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.