Closed Bug 225641 Opened 16 years ago Closed 16 years ago

Installer should ask where to put icons

Categories

(Firefox :: Installer, defect, P3)

x86
Windows 2000
defect

Tracking

()

VERIFIED FIXED
Firefox1.0beta

People

(Reporter: Bugzilla-alanjstrBugs, Assigned: bugs)

References

()

Details

(Keywords: conversion, Whiteboard: fixed-aviary1.0)

Attachments

(1 file, 2 obsolete files)

The installer created shortcuts in the Start Menu, QuickLaunch toolbar, and on
the deskop.  One would have been sufficient.  Firebird should ask where to
create shortcuts.
Summary: Installer doesn't ask where to put icons. → Installer doesn't ask where to put icons.
Bug 28174 is the Seamonkey version of this bug.
Summary: Installer doesn't ask where to put icons. → Installer should ask where to put icons
This includes asking whether the icons are for All Users or for the currently
logged in user.  If someone installs the application into a directory that only
they can access, for example.  
Blocks: 230734
No longer blocks: 230734
*** Bug 230734 has been marked as a duplicate of this bug. ***
*** Bug 228809 has been marked as a duplicate of this bug. ***
Blocks: 233536
Keywords: conversion
I think conversion is a bit of an overstatement.  How does having deleteable
icons placed on the desktop/startmenu stop people using Firefox?  IE puts them
there, afterall.  I agree that there should be an option (I don't want them
there either), but disagree with the conversion keyword.
From the Designed for Windows XP Application Specification:

"F1.1 Install shortcuts correctly

The Start menu is designed to give users easy access to launch applications.
Usability studies show that when the Start menu and/or Windows Desktop become
too cluttered, users have a very difficult time finding and launching their
programs. This leads to a bad user experience.

* Do not place shortcuts on the Desktop except by request of the user. If an
option to add such a shortcut is offered to the user, then this should not be
checked by default. Automatic installs should not place any shortcuts on the
Desktop. 

[...]

* Do not place shortcuts to documents, such as Readme files, in the Start menu.
If you have important information that the user should see, consider displaying
that information during the install process or on the help menu of the application."
Flags: blocking1.0?
+ing to see if I can find an easy way of doing this. Will take a patch!
Flags: blocking1.0? → blocking1.0+
OK I know how to do this

1) add a new page to the installer (custom path only)
2) page contains checkboxes for Desktop, Quick Launch and Start Menu
3) checkboxes set registry keys for current user
4) browser.jst reads these keys to determine what shortcuts to create. 
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → Firefox1.0beta
(In reply to comment #8)
> OK I know how to do this
> 
> 1) add a new page to the installer (custom path only)
> 2) page contains checkboxes for Desktop, Quick Launch and Start Menu

And the Desktop checkbox should not be checked by default, as explained in
comment 6.
Flags: blocking1.0+ → blocking0.9+
Attached patch partial progress (obsolete) — Splinter Review
This re-enables the "Windows Integration" page for custom installs, and
populates the checkboxes with values, but doesn't do anything yet.

Stage 2 (tomorrow): have these things set registry keys, and make the installer
scripts read those keys before creating shortcuts.
Attached patch it's alive! (obsolete) — Splinter Review
Attachment #149745 - Attachment is obsolete: true
Attachment #149787 - Attachment is obsolete: true
Attachment #149790 - Flags: review?(mscott)
Attachment #149790 - Flags: review?(mscott) → review+
Fixed branch and trunk
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Verified fixed on trunk, 20040602 PC/Win2K
Whiteboard: fixed-aviary1.0
FYI for anyone looking for an update on the issue of icons created by the
installer...although this bug is closed, the problem lives on in bug 245392.
Status: RESOLVED → VERIFIED
QA Contact: bugzilla → installer
You need to log in before you can comment on or make changes to this bug.