Closed
Bug 33554
Opened 25 years ago
Closed 16 years ago
Make the Readme visible from help after installation.
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: vparthas, Unassigned)
References
Details
(Whiteboard: [xpibug][low-hanging])
Attachments
(1 file)
9.74 KB,
patch
|
Details | Diff | Splinter Review |
Need to create Program Folder shortcuts for Readme/License Texts during the
Seamonkey install.
set to m18
Component: Installer: XPInstall Engine → Installer
Target Milestone: --- → M18
Reassigning QA Contact to Grace for Installer issue.
QA Contact: jimmylee → gbush
grace, do we have such critters? I mentioned creating them in some other bug.
If this is for the commercial side, please move to bugscape.
Keywords: nsbeta3
Comment 4•24 years ago
|
||
Lack of shortcuts to the Readme or License file isn't going to stop us from
Shipping PR3 so [nsbeta3-], but CC'ing PM folks for a second opinion.
Whiteboard: [nsbeta3-]
Comment 7•24 years ago
|
||
Not a stop-ship, but would be good if we could get this in.
Comment 8•24 years ago
|
||
I can't see the PDT approving this based on other P3 rejections. If this is a
strong requirement please have the PDT comment in this bug that they are open to
accepting this before I have Sean go off and waste time coming up with a patch.
Whiteboard: [nsbeta3-] → [nsbeta3-][rtm-]
Comment 9•24 years ago
|
||
Unsetting missed milestones to aid triage queries.
Target Milestone: M18 → ---
Comment 10•24 years ago
|
||
This can be a placeholder for "Desktop Integration". Talk to kmurray.
Whiteboard: [nsbeta3-][rtm-] → [xpibug][nsbeta3-][rtm-]
Comment 12•24 years ago
|
||
Should be easy for someone who wants to learn about install
Comment 14•24 years ago
|
||
adding ktrina as QA contact for subset of Installer bugs
I will continue to monitor as well
QA Contact: gbush → ktrina
Comment 15•23 years ago
|
||
ccing Curt and Dave. This is not urgent, but in the comments it said this should
be easy for someone who wants to learn about install.
Updated•23 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.6
Updated•23 years ago
|
Target Milestone: mozilla0.9.6 → mozilla0.9.7
Comment 17•23 years ago
|
||
I'm working on this now. The license file makes plenty of sense, but I don't
even see a readme for the product anywhere. It isn't checked in anywhere,
displayed by the installer, or installed (that I can find). What have we been
doing for a readme? (Or am I hallucinating?)
Comment 18•23 years ago
|
||
Since I need to know a bit more about the readme before I can handle it (i.e.,
where is it going to be checked in and do we want to do more than just add an
icon for it) this patch if only for the license file, which already exists. I
did add a variable for the readme so we'll be better prepared for it when I
know where it lives and such.
If this patch looks good I'll create another for the ns trunk also?
Comment 19•23 years ago
|
||
Better get someone on this list who knows what he is doing to keep me honest!
Updated•23 years ago
|
Target Milestone: mozilla0.9.7 → mozilla0.9.8
Updated•23 years ago
|
Whiteboard: [xpibug][low-hanging] → [xpibug][low-hanging][mcp-working]
Comment 20•23 years ago
|
||
Gregg, Grace and I looked this over together. The browser already displays the
license file in Help|About. A link to the release notes is available under
Help|Help and Support Center. I need to know if marketing is really wanting to
do what this bug suggests since the license file is accessable already from the
browser and the readme isn't even installed with the product currently. And, if
we're going to add these to the product folder, do we want to add a link to the
release notes also? These are probably as useful to have around as the readme.
Gregg, let me know what you want.
Comment 21•23 years ago
|
||
I don't think we should add a shortcut to the ReadMe. Instead, I think it
should what http://bugzilla.mozilla.org/show_bug.cgi?id=115901 says; Which is
allow a client page the ability to point to the flat file. This bug should be
merged with 115901 or retired.
No longer depends on: 115901
Comment 22•23 years ago
|
||
Since 115901 deals with getting the readme installed, I'm changing the
description of this bug to reflect the desire of the docs dept., making it
dependant on 115901 and assigning it to Steve to update the Help/Help and
Support Center to display the readme.
We are happy with the way the license file is being handled so no further action
is required there.
Assignee: curt → rudman
Status: ASSIGNED → NEW
Summary: Need to create Program Folder shortcuts for Readme/License Texts. → Make the Readme visible after installation.
Whiteboard: [xpibug][low-hanging][mcp-working] → [xpibug][low-hanging]
Comment 23•23 years ago
|
||
I don't remember now what the Mozilla read me says (there is one, isn't there?).
In any case, the Netscape version will surely be different from the Mozilla one.
Access to the Mozilla version can't happen via the Help and Support Center,
since that is on the Netscape side only. But at least, if Mozilla really
wants/needs a Read Me, at least a user could search one's system for the file,
which Curt is exposing.
Reassigning to Jatin.
Assignee: rudman → jatin
Comment 24•23 years ago
|
||
Adding oeschger@netscape.com for discussion of Readme placement so that it's
accessible from the Help Menu Screen.
Comment 25•23 years ago
|
||
Jatin, I wasn't thinking that it should be accessible from the Help menu. It
should be a link (a relative one) from the Help and Support Center page, I
think. Unless you think otherwise.
Comment 26•23 years ago
|
||
Yes, the Readme should be accessible from the Help and Support Center menu. I
didn't mean to imply that it should be on the Help drop-down.
Comment 27•23 years ago
|
||
see bug 115901 for adding readme to start menu
will add attachment showing placement-
does this satisfy requirements for this bug?
Comment 28•23 years ago
|
||
I guess that I marked this bug fixed prematurely now that I reread the summary.
On the other hand, I believe that my part is done so it should be reassigned to
someone else now? Who?
Comment 29•23 years ago
|
||
For MachV, I'll be updating the Help and Support Center welcome page with a link
to the following URL, which is a link to the flat file:
resource:///readme.txt
Comment 30•23 years ago
|
||
I can't get the following URL to work as an HTML link:
resource:///readme.txt
Is there a workaround you know about?
Comment 31•23 years ago
|
||
The Read Me file can now be accessed from the Start Menu, making it now visible
after installation. I feel this reduces the need for the file to be accessible
from within the product as was originally proposed. Shall I resolve this bug as
fixed?
Comment 32•23 years ago
|
||
I don't think so, because we've got a bug to pull it back out of the Start Menu.
Comment 33•23 years ago
|
||
What's the bug to remove it from the Start menu? Why are we doing that? In any
case, the read me doesn't show up in the Start menu in commercial builds (using
build of 3/28).
I just checked a few other apps of the relatively few I have on my system
(recently wiped clean)... Acrobat, FrameMaker, and Winamp have read me files
directly accessible from the Start menu (though Winamp's is called "What's New,"
but it's a text file that is read me-ish).
Anyone have some idea why Jatin is having the problems he mentioned with
resource:///readme.txt?
Status: NEW → ASSIGNED
Comment 34•23 years ago
|
||
un-signed HTML cannot access file: or resource: urls for security reasons
(cross-domain scripting exploints). I think we worked around this in the
commercial build by putting a copy of the readme and license into a chrome .jar
Comment 35•23 years ago
|
||
My earlier comment about the Read Me file being in the Start menu turns out to
be incorrect, as Steve mentioned.
Dan, although we now have a copy of the readme and license in a chrome .jar, how
do we link to it from the Help? The About: Page seems to be able to link to the
license. How is that done, and can we replicate that in the Help and Support
Center main menu?
Comment 36•23 years ago
|
||
Jatin, have you tried using:
jar:resource:///chrome/en-US.jar!/locale/en-US/global/readme.txt
That is the equivalent to what the license link is doing.
Updated•23 years ago
|
Component: Installer → Help
Updated•23 years ago
|
Assignee: jatin → cotter
Status: ASSIGNED → NEW
Comment 37•23 years ago
|
||
That seems to work with an added target="_blank" statement. Thanks much Curt!
Reassigning bug to Sean Cotter <cotter@netscape.com>, who is helping with the
Help and Support Center links.
Sean, the link should use the following HTML with "Read Me Title" being a
variable to be replaced with the appropriate Read Me title:
<a href="jar:resource:///chrome/en-US.jar!/locale/en-US/global/readme.txt"
target="_blank">Read Me Title</a>
Comment 38•23 years ago
|
||
Resetting milestone.
Updated•22 years ago
|
Target Milestone: mozilla1.0 → ---
Comment 39•22 years ago
|
||
Is this bug for Netscape or Mozilla? Is it still live?
If it is still live, then we just need to make sure both Netscape and Mozilla
put the readme's in the same spot and it can be linked from the Help menu I think.
Comment 40•22 years ago
|
||
This is likely a cross-platform issue.
OS: Windows NT → All
Hardware: PC → All
Comment 41•22 years ago
|
||
The initial description specifically says "Program Folder shortcuts" (I
personally have no opinion, there are reasons for both: you might need the
readme when the app fails to start, but cluttering up the start menu for stuff
that is almost never used is not great either), which would be platform specifc.
OS: All → Windows NT
Hardware: All → PC
Comment 42•22 years ago
|
||
do we really need this bug? Currently ReadMe only talks about where to download
Mozilla and how to install it, so there's really no need to read it after
installation.
Comment 43•21 years ago
|
||
Why is this bug in the Help component? This bug has nothing to do with the
Mozilla Help Viewer.
Daniel: Can you move this to a more appropriate component? Thanks!
QA Contact: ktrina → stolenclover
Summary: Make the Readme visible after installation. → Make the Readme visible from help after installation.
Comment 44•21 years ago
|
||
-> Doc: User
More appropriate than browser: help :)
Component: Help → User
Product: Browser → Documentation
Version: Trunk → unspecified
Comment 45•16 years ago
|
||
Actually, I don't think we want this for help. On mac, the readme is visible from the dmg window.
Assignee: cotter → general
Component: Help Viewer → General
Product: Documentation → SeaMonkey
QA Contact: danielwang → general
Version: unspecified → Trunk
Updated•16 years ago
|
Assignee: general → nobody
Priority: P2 → --
Comment 46•16 years ago
|
||
We won't fix this the way described here, but we may want to include the new about:rights work done for Firefox that makes the license stuff easily available to people on a first start.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•16 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•16 years ago
|
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•