Closed
Bug 240277
Opened 21 years ago
Closed 20 years ago
Help is not packaged in installer builds
Categories
(Firefox :: Installer, defect)
Firefox
Installer
Tracking
()
VERIFIED
FIXED
People
(Reporter: Waldo, Assigned: jwalden+fxhelp)
References
Details
(Whiteboard: fixed-aviary1.0)
Attachments
(3 files, 3 obsolete files)
647 bytes,
text/plain
|
Details | |
4.25 KB,
patch
|
Details | Diff | Splinter Review | |
4.23 KB,
patch
|
Details | Diff | Splinter Review |
Firefox Help is not registered in the packages-static files for windows/unix
installers. There's also no help.jst file, either. Therefore, installer builds
don't have Help in them, a major omission.
Marking severity as major because Firefox Help is on the roadmap for Firefox
0.9, and if it's not in the installer builds (what most people will use) it
won't be used by the vast majority of users.
Reporter | ||
Comment 1•21 years ago
|
||
blocking0.9?
If built-in Firefox Help isn't in Installer builds (particularly for Windows),
it might as well not even be there for the newbies who want to use Firefox.
Flags: blocking0.9?
Comment 2•21 years ago
|
||
Why do you think Help should be optional?
Reporter | ||
Comment 3•21 years ago
|
||
(In reply to comment #2)
> Why do you think Help should be optional?
Aren't Help components typically optional installs for most programs? I'm sure
I could make a list of such programs if necessary. In any case, why not make it
optional? It's no extra bloat, I believe.
Comment 4•21 years ago
|
||
yes, Jeff I disagree. Help should be by default because it is end-user
documentation and end-users aren't going to do custom installs.
Reporter | ||
Comment 5•21 years ago
|
||
(In reply to comment #4)
> yes, Jeff I disagree. Help should be by default because it is end-user
> documentation and end-users aren't going to do custom installs.
I think I'm being misunderstood. I *am* saying that Help should be optional -
but *only for Custom installs*. If it's a regular install, Help will *always*
be installed. If the user *chooses* to go with Custom, then Help is
automatically selected, *but it can be deselected if the user chooses*. This is
win-win. It means faster downloads for the power user who feels he can intuit
how Firefox works (after net install is available, that is) - *he must remove
Help himself*. For the common user who won't opt for Custom install, Firefox
Help will *always* be installed without forcing the user to make that decision.
Perhaps another tack will explain better. Refer to the Installer UE page at
<http://www.mozilla.org/projects/firefox/ue/installer/>.
At page 3, if Standard is selected, Help will be installed because it is *a
"most common [option]"*. If Custom is selected, then page 6 will include a
third option roughly (text subject to change) as below:
[*] Firefox Help
Offline Help with learning about and using Mozilla Firefox.
Note that the [ ] is *automatically selected*, meaning that the power user still
must make a conscious effort to remove Help from the installation.
If that's not clear enough, I'm not sure what else I can say. If you still
either don't understand me or think it's still a bad idea, just change the bug
title.
Comment 6•21 years ago
|
||
oh OK. Sorry for the misinterpretation. That makes sense.
Thanks for the clarification, Jeff.
Comment 7•20 years ago
|
||
rjk, do we need a patch or any sort of build-fu to make this happen in the
installer?
Comment 8•20 years ago
|
||
This qualifies as a blocker, FF Help should have been in 0.8 but came in too
late. Its also easy enough to fix, it just needs the packaging-fu in place.
This is missing on both gtk2 and win32 installers.
cc-ing bryner for at least the Linux installer end of things.
Depends on: 234770
Flags: blocking0.9? → blocking0.9+
Summary: Include Help as an optional, default-on part of installer builds → Help is not packaged in installer builds
Comment 9•20 years ago
|
||
removing nonsensical dependency that I somehow added
No longer depends on: 234770
Reporter | ||
Comment 10•20 years ago
|
||
Reporter | ||
Comment 11•20 years ago
|
||
Here's some work I've done on this for the Unix installer. I can't test it and
have no idea what the code edited does, so this is at best a beginning for
someone else to make a better patch.
Reporter | ||
Comment 12•20 years ago
|
||
Here's some work I've done on this for the Windows installer. I can't test it
and have no idea what the code edited does, so this is at best a beginning for
someone else to make a better patch.
Comment 13•20 years ago
|
||
RJ, can you test these out? my windows build environment is dead atm
Comment 14•20 years ago
|
||
mconnor: my build is saying "Cannot find install.ini". This is more likely a
problem with my build system than with the environment. Is there something
special I should set? I've never tried using the installer before :P.
Comment 15•20 years ago
|
||
--> jwalden
I'm going to try and get a test build with this over the weekend.
Assignee: bugs → jwalden+bmo
Assignee | ||
Comment 16•20 years ago
|
||
Assignee: jwalden+bmo → jwalden+fxhelp
Attachment #148074 -
Attachment is obsolete: true
Status: NEW → ASSIGNED
Assignee | ||
Comment 17•20 years ago
|
||
This patch is for the Unix installer. It fixes two issues:
1) Help wasn't listed in the default components for the two types of setup.
2) Help was set as optional. With bug 242275 in effect, this is not a good
idea.
This patch has a better chance of working than the original, but I still don't
really know if it will work.
Attachment #148075 -
Attachment is obsolete: true
Assignee | ||
Comment 18•20 years ago
|
||
This patch is for the Windows installer. It fixes two issues:
1) Help wasn't listed in the default components for the two types of setup.
2) Help was set as optional. With bug 242275 in effect, this is not a good
idea.
This patch has a better chance of working than the original, but I still don't
really know if it will work.
Attachment #148076 -
Attachment is obsolete: true
Comment 19•20 years ago
|
||
I tested it, it works. Good enough for me. Checked in branch and trunk.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 20•20 years ago
|
||
The checkin was for Windows only according to Bonsai. Should I have bryner
review the Unix patch (even tho it's pretty much a line-for-line transliteration
of the Windows patch)? As it is right now, Help is presumably *not* part of the
Linux installer, and thus Linux installer builds are presumably affected by bug
242275. (Of course, this isn't easily testable because no Linux branch builds
are being made. A trunk build might demonstrate the bug, tho.)
Comment 21•20 years ago
|
||
I still see this on tinderbox build Mozilla/5.0 (Windows; U; Windows NT 5.1;
en-US; rv:1.7) Gecko/20040529 Firefox/0.8.0
1.7.20040.52905
that's after this was marked resolved.
Comment 22•20 years ago
|
||
Reopening. Also not seeing this in trunk build 20040529 PC/WinXP.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 23•20 years ago
|
||
Forgot to check in help.jst. Fixed now.
Status: REOPENED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 24•20 years ago
|
||
Am I wrong in also not seeing:
mozilla/browser/installer/unix/installer.cfg.in
mozilla/browser/installer/unix/config.it
mozilla/browser/installer/unix/packages-static
...not being checked in on the Firefox 1.0 branch? That's what it's looking
like to me on Unix.
Comment 25•20 years ago
|
||
Jeff, I'll check in the Unix version of this patch today. (If you don't see an
update by 5 PM, please email me :)
Comment 26•20 years ago
|
||
never mind, ben did it "I wonder what I have to do to make this file BE CHECKED
IN" :)
Comment 27•20 years ago
|
||
verifying fixed in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7)
Gecko/20040530 Firefox/0.8.0+
Updated•20 years ago
|
Whiteboard: fixed-aviary1.0
Comment 29•20 years ago
|
||
There was no Help in Mac version Firefox 0.9 RC...
Assignee | ||
Comment 30•20 years ago
|
||
(In reply to comment #29)
> There was no Help in Mac version Firefox 0.9 RC...
That's a separate bug - see bug 244479.
To verify that Help is packaged, type "chrome://help/content/help.xul". If you
see a pseudo-Help window, then Help is present - it's only the menu items that
aren't present (as a result of the aforementioned bug).
Comment 31•20 years ago
|
||
Thank you for information, Walden-san.
(In reply to comment #30)
> To verify that Help is packaged, type "chrome://help/content/help.xul".
Help was displayed now.
it seems to be the problem of a menu.
Updated•19 years ago
|
QA Contact: bugzilla → installer
You need to log in
before you can comment on or make changes to this bug.
Description
•