Closed
Bug 99160
Opened 23 years ago
Closed 23 years ago
Freeze nsIFile
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
FIXED
mozilla1.0
People
(Reporter: dougt, Assigned: dougt)
References
Details
(Keywords: embed, topembed-, Whiteboard: [fixed trunk])
Attachments
(1 file, 5 obsolete files)
43.63 KB,
patch
|
Details | Diff | Splinter Review |
nsIFile
* Requires: nsISimpleEnumerator
* To Do
* The implementation of NS_GetSpecialDirectory(...) should probably be moved
out of this IDL file.
nsILocalFile
* Requires: nsIFile, NSPR I/O
nsIProperties
nsIDirectoryService
* Requires: nsIDirectoryServiceProvider
nsIDirectoryServiceProvider plugin requirement.
Assignee | ||
Updated•23 years ago
|
Target Milestone: --- → mozilla1.0
Assignee | ||
Updated•23 years ago
|
Keywords: mozilla1.0
Assignee | ||
Comment 1•23 years ago
|
||
nsIDirectoryService is frozen. adjusting summary
Summary: Freeze nsIFile nsIDirectoryService → Freeze nsIFile
Updated•23 years ago
|
Keywords: mozilla1.0+
Updated•23 years ago
|
Keywords: mozilla1.0
Assignee | ||
Updated•23 years ago
|
Assignee | ||
Updated•23 years ago
|
Assignee | ||
Comment 2•23 years ago
|
||
Posted on the newsgroup:
With less than three weeks left or so before Mozilla 1.0 (according to the
Mozilla Road Map), and a requirement that nsILocalFile be frozen, I propose that
we mark theses interfaces as FROZEN as-is.
Please send your flames and offers to help to dougt@netscape.com, or better yet,
use the tracking bug:
http://bugzilla.mozilla.org/show_bug.cgi?id=99160
Comment 3•23 years ago
|
||
Doug,
Please, before mozilla 1.0, re-commit the changes that you made in revision
1.48 of nsIFile (moving the inline NS_GetSpecialDirectory into a separate file
and wrapping it in '#ifndef MOZILLA_STRICT_API').
Without this change, the purpose of MOZILLA_STRICT_API would be defeated: a
client would end up having to include the 'obsolete' ComponentManager and
ServiceManager headers before including nsIFile.
Assignee | ||
Comment 4•23 years ago
|
||
Yup.
revision 1.49
date: 2002/01/29 21:42:38; author: dougt%netscape.com; state: Exp; lines: +46 -36
Backing out nsIFile changes which should not have landed.
Assignee | ||
Comment 5•23 years ago
|
||
As Mark mentioned, this needs to happen before the interface is frozen.
Comment 6•23 years ago
|
||
Comment on attachment 74847 [details] [diff] [review]
Moves utility function into header file
sr=rpotts@netscape.com
Attachment #74847 -
Flags: superreview+
Comment 7•23 years ago
|
||
Comment on attachment 74847 [details] [diff] [review]
Moves utility function into header file
r=jband
Attachment #74847 -
Flags: review+
Comment 8•23 years ago
|
||
Comment on attachment 74847 [details] [diff] [review]
Moves utility function into header file
Why is the new file named with the nsI prefix? It defines no interface, in
particular it does not define nsIFileUtils. Rename it to nsFileUtils.h, or
perhaps nsSpecialDirectory.h?
/be
Assignee | ||
Comment 9•23 years ago
|
||
new file name is nsDirectoryServiceUtils.h
Attachment #74847 -
Attachment is obsolete: true
Comment 10•23 years ago
|
||
Those patches look the same to me, and to diff. :-)
/be
Assignee | ||
Comment 11•23 years ago
|
||
Attachment #74872 -
Attachment is obsolete: true
Assignee | ||
Comment 12•23 years ago
|
||
I think we have a problem if this does not work!
Attachment #74878 -
Attachment is obsolete: true
Assignee | ||
Comment 13•23 years ago
|
||
There is a problem with 0.99. I could not get the file://path_to_patch/patch
to notice my changes.
Attachment #74879 -
Attachment is obsolete: true
Comment 14•23 years ago
|
||
Comment on attachment 74880 [details] [diff] [review]
attempt 4 using Nav4.7
Carrying forward r= and sr=, adding a= for 1.0 checkin -- good file name!
/be
Attachment #74880 -
Flags: superreview+
Attachment #74880 -
Flags: review+
Attachment #74880 -
Flags: approval+
Comment 15•23 years ago
|
||
dougt: make sure jkeiser is aware of the problem you were seeing... it may be
some side effect of the new form POST implementation.
Assignee | ||
Comment 16•23 years ago
|
||
i tried to reproduce the problem but could not. Thanks for pointing me at jkeiser.
Assignee | ||
Comment 17•23 years ago
|
||
That last patch was checked in.
Checking in MANIFEST;
/cvsroot/mozilla/xpcom/io/MANIFEST,v <-- MANIFEST
new revision: 3.24; previous revision: 3.23
done
Checking in Makefile.in;
/cvsroot/mozilla/xpcom/io/Makefile.in,v <-- Makefile.in
new revision: 1.60; previous revision: 1.59
done
Checking in makefile.win;
/cvsroot/mozilla/xpcom/io/makefile.win,v <-- makefile.win
new revision: 1.50; previous revision: 1.49
done
RCS file: /cvsroot/mozilla/xpcom/io/nsDirectoryServiceUtils.h,v
done
Checking in nsDirectoryServiceUtils.h;
/cvsroot/mozilla/xpcom/io/nsDirectoryServiceUtils.h,v <--
nsDirectoryServiceUtils.h
initial revision: 3.1
done
Checking in nsIFile.idl;
/cvsroot/mozilla/xpcom/io/nsIFile.idl,v <-- nsIFile.idl
new revision: 1.51; previous revision: 1.50
done
Comment 18•23 years ago
|
||
here's a preliminary patch for XP_UNIX that compiles only in xpcom/io
it changes nsIFile and nsILocalFile to use AUTF8String strings.
and i created a hopefully shortlived interface nsILocalFileInternal for all of
the old string and wstring methods to ease the transition to UTF-8.
Comment 19•23 years ago
|
||
cc'ing some more folks who might want to comment on this...
Comment 20•23 years ago
|
||
this is fantastic. It is exactly what I wanted to see happen :)
The patch looks great from my initial scan.
Comment 21•23 years ago
|
||
Yeah. As far as the string params, looks good.
There's still some symlink following API issues discussed in bug 94323 but this
string param work is the biggest fish to fry.
Comment 22•23 years ago
|
||
actually darin it seems like your patch belongs in bug 129279.. a mere
technicality :)
Also, one thing in the patch - can you make the "Native" versions of each
function [noscript] just so people won't be tempted, since string wasn't meant
to handle non-ascii?
The nice thing about this patch is that JavaScript probably won't need any
changes, since as long as the attribute names stay the same, JS will simply
start using the UTF8 attribute instead! You'll probably fix a few bugs related
to that just by fixing this..
Updated•23 years ago
|
Comment 23•23 years ago
|
||
Comment on attachment 74880 [details] [diff] [review]
attempt 4 using Nav4.7
obsoleting patch which was checked in so this doesn't look like an approved
change that is still not landed.
Attachment #74880 -
Attachment is obsolete: true
Comment 24•23 years ago
|
||
marked nsIFile and nsILocalFile as frozen on the trunk and branch ;-)
Status: NEW → RESOLVED
Closed: 23 years ago
Keywords: fixed1.0.0
Resolution: --- → FIXED
Whiteboard: [fixed trunk]
You need to log in
before you can comment on or make changes to this bug.
Description
•