Bug 50278 - Provide separate dock icons for each component on macOS instead of or in addition to the global launcher aka make components single apps
Summary: Provide separate dock icons for each component on macOS instead of or in addi...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
Master old -3.6
Hardware: All macOS (All)
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 57594 97946 126372 133132 (view as bug list)
Depends on:
Blocks: macOS-UI-polish
  Show dependency treegraph
 
Reported: 2012-05-23 05:28 UTC by Chris Cunningham
Modified: 2024-07-03 12:45 UTC (History)
11 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Cunningham 2012-05-23 05:28:14 UTC
LibreOffice counterpart to https://issues.apache.org/ooo/show_bug.cgi?id=87090

Presently, LibreOffice for Mac OS X installs the entire suite into one .app bundle. There are no separate launchers for the individual components, so users cannot have e.g. an icon for Writer in the dock.

The AOO ticket has an attached solution in the form of "dummy" .apps for each component which only contain a bit of AppleScript. Whether the license is suitable or not (the attachment dates back to 2008, as the bug was originally filed against OO.o) it should be easy enough to reconstruct from first principles.
Comment 1 Roman Eisele 2012-05-24 03:01:33 UTC
Set Status to NEW because this is a valid enhancement request (there are no separate dock icons for the components of LibreOffice 3.3.x, 3.4.x, or 3.5.x on MacOS X).

(Personally, I don't know if this would be a good enhancement -- I prefer the way it is now --, but this does not change the fact that this is a valid request. ;-)
Comment 2 Roman Eisele 2012-11-27 10:11:09 UTC
*** Bug 57594 has been marked as a duplicate of this bug. ***
Comment 3 Roman Eisele 2012-11-27 10:12:20 UTC
(Copied “see also” hint to appropriate field.)
Comment 4 Emir Sarı 2012-11-27 10:51:53 UTC
I also do support this. 

+1
Comment 5 GSC 2014-12-08 11:00:01 UTC
Still an issue with 4.3.4.1 on OS X 10.10. Is it so hard for osx?
Comment 6 Alex Thurgood 2014-12-08 16:35:46 UTC
(In reply to GSC from comment #5)
> Still an issue with 4.3.4.1 on OS X 10.10. Is it so hard for osx?

Yes. The simple fact of the matter is that there are an insufficient number of developers working on the OSX port, and other more important problems to solve. 

The solution to this :

- put up with it ;
- do it yourself ;
- find someone to do it for you for free ;
- pay someone to do it for you.
Comment 7 Markus 2015-05-05 09:43:48 UTC
I understand that there are not that many people on the OSX ported version and this is a great free software but also matter of the fact is I just tried to switch to LibreOffice for the first time and this seemingly little usability issue made me uninstall it again.

Having to do this two-step process should not be necessary in the first place. Otherwise I would love to support this wonderful open source software and recommend it to other people.
Comment 8 How can I remove my account? 2018-05-24 14:17:45 UTC
This is hardly of "high" importance?
Comment 9 Alex Thurgood 2018-05-25 07:47:20 UTC
(In reply to Tor Lillqvist from comment #8)
> This is hardly of "high" importance?

Agreed. Medium at best.
Comment 10 younky.yang 2018-11-13 01:35:44 UTC Comment hidden (me-too)
Comment 11 James 2018-12-29 20:11:32 UTC Comment hidden (me-too)
Comment 12 younky.yang 2019-08-09 00:33:00 UTC Comment hidden (me-too)
Comment 13 steve 2019-09-22 17:01:21 UTC
*** Bug 97946 has been marked as a duplicate of this bug. ***
Comment 14 steve 2019-09-22 17:02:00 UTC
Adding notes from https://bugs.documentfoundation.org//show_bug.cgi?id=97946

Discussed this in the ESC meeting Jul/18 2019 and there was agreement to modify the installer.

         + only a matter of adding launchers (Christian)
             + provide a template and pull it into your dock easily
             + D&D installer gets you 1 application
             + perhaps a folder with some templates you can drag → launcher
             + no LibO code-change necessary.
         + lets find some volunteer that cares to write it (Michael)
Comment 15 Chris Cunningham 2019-09-24 18:26:36 UTC
The only things that are needed for component-specific bundles are:

1. A one-liner shell script which invokes `soffice --<component>` for each component;
2. A basic Info.plist which points to the shell script (handled by sysui/Package_infoplist.mk);
3. The application icon (handled by sysui/Package_osxicons.mk).

The directory structure is:

Component.app
|-Contents
  |-MacOS
    |-shellscript
  |-Resources
    |-icon.icns
  |-Info.plist

The shell script is literally just:

#!/bin/bash
/Applications/LibreOffice.app/Contents/MacOS/soffice --writer

The actual bundling lives in solenv/bin/modules/installer/simplepackage.pm from around line 263-436.

The easiest thing to do would probably be to add an extra step in there which iterates over each component, generates the directory structure, generates the shell script and Info.plist, and copies script, icon and plist into the directory.
Comment 16 How can I remove my account? 2020-04-27 10:45:27 UTC
> /Applications/LibreOffice.app/Contents/MacOS/soffice --writer

Surely one can't assume that the LibreOffice.app is installed in /Applications. This is not the right way to solve this issue.
Comment 17 Chris Cunningham 2020-04-27 12:31:09 UTC
(In reply to Tor Lillqvist from comment #16)
> > /Applications/LibreOffice.app/Contents/MacOS/soffice --writer
> 
> Surely one can't assume that the LibreOffice.app is installed in
> /Applications. This is not the right way to solve this issue.

Making the assumption that the launcher is in the same directory as the main LibreOffice app bundle (which I think is the only practical solution), it's not difficult to use a relative path:

dir=$(dirname "$0")
"${dir}/../../../LibreOffice.app/Contents/MacOS/soffice" --writer

So long as both app bundles are in the same directory this should work regardless of where they are on disk.
Comment 18 Heiko Tietze 2020-07-04 20:34:33 UTC
*** Bug 133132 has been marked as a duplicate of this bug. ***
Comment 19 Stéphane Guillou (stragu) 2024-07-03 12:45:24 UTC
*** Bug 126372 has been marked as a duplicate of this bug. ***