Closed Bug 6486 Opened 26 years ago Closed 26 years ago

rm old files in cvs

Categories

(Core :: XUL, defect, P2)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: tao, Assigned: matt)

References

()

Details

Whenever applicable, please convert HTML file to XUL file so we can externalize localizable resources. Also, refer to the "XUL Coding Style Guidelines" in the URL above for how to make XUL localizable. Thanks!
Q: are these four files all obsolete? ./xpfe/browser/src/appshell.html ./xpfe/browser/src/contentframe.html ./xpfe/browser/src/sidebar.html ./xpfe/browser/src/status.html ./xpfe/browser/src/BrowserInitPage.html
Changing QA contact to myself
Assignee: rods → don
Yes, these are obsolute. Don, someone in your group should look over the makefiles, like (S:\mozilla\xpfe\browser\src\makefile.win) and determine what files are current and what one are not and they should remove the ones that are no longer being used.
Assignee: don → matt
Priority: P3 → P2
Target Milestone: M6
Matt, is this part of the other work you're doing?
Status: NEW → ASSIGNED
Summary: appshell.html: please convert to localizable XUL file → rm old files in cvs
These are all files we don't use. I was going though some of the files but was deleting only the files that where mine. I can blow the other ones away also. ./xpfe/browser/src/status.html ./xpfe/browser/src/BrowserInitPage.html ./xpfe/browser/src/sidebar.html ./xpfe/browser/src/appshell.html ./xpfe/browser/src/downloadProgress.xul ./xpfe/browser/src/downloadProgress.css
Target Milestone: M6 → M7
Component: other → XUL
Target Milestone: M7 → M8
Move to M8. No hurry to do this ...
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
fixed. Didn't remove the downloadProgress b/c i think this is going to be a sample
Status: RESOLVED → VERIFIED
BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL. XUL component will be deleted.
Component: XUL → XP Toolkit/Widgets: XUL
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: tao → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.