create desktop shortcut on install (maemo 5)

VERIFIED WONTFIX

Status

Firefox for Android Graveyard
General
VERIFIED WONTFIX
9 years ago
8 years ago

People

(Reporter: madhava, Unassigned)

Tracking

Fennec 1.1
ARM
Maemo

Details

(Reporter)

Description

9 years ago
We should create a desktop shortcut to Firefox when it is installed on maemo 5.
This is a pretty big discoverability issue, IMO, though perhaps it's usual for Maemo users to go dig out their applications from the menu? Nominating for blocking (which is irksome this close to release, I know) in hopes that there's a trivial fix, and maybe to get it in the 1.1 pipeline.
tracking-fennec: --- → ?
(Reporter)

Comment 2

9 years ago
Sounds like there may be a trivial fix (mfinkle said in channel that you can make a shortcut from the command line).

I don't think there _is_ a usual for maemo 5 users, as new as it is.  The main list is where all installed apps go, so I don't know if it'll be a discoverability issue, but there's certainly a convenience factor.
I don't know if a real API exists to add a shortcut, but you can do it using the "gconftool-2" commandline tool.

To see a list of the current task shortcuts use:

gconftool-2 --get /apps/osso/hildon-home/task-shortcuts

To add Fennec to the list use:

gconftool-2 --set --type=list --list-type=string /apps/osso/hildon-home/task-shortcuts [<all-existing-shortcuts>,fennec.desktop]

Not sure if it will be easy to add this to the postinst, but we might be able to add it to our commandline handler and call it from postinst

Updated

9 years ago
tracking-fennec: ? → 1.0-
Keywords: qablocker
Keywords: qablocker
From my conversation with stuart, no other application on maemo 5 does this, so not blocking 1.0/RC.
I'd go further and say we should WONTFIX this.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WONTFIX
Agreed.
Status: RESOLVED → VERIFIED

Updated

8 years ago
Component: Linux/Maemo → General
OS: Mac OS X → Linux (embedded)
QA Contact: maemo-linux → general
Hardware: x86 → ARM
You need to log in before you can comment on or make changes to this bug.