Sorry I was on vacation when you held this meeting. Here are some of my
comments:
* "Links" (CopyToFollowingLinks()) methods go away. the followLinks
attribute will apply to all methods.
Just for clarification, the |followLinks| attribute should be read-only.
It should be set at creation and not modified during the objects
lifetime. This is because a resolved path may become invalid if this
flag is modified. Because of this and since the "Links" methods are
going away, one must not construct a new nsFile if they need to operate
in a different followLinks mode.
* append() assumes resolution, regardless of followLinks state.
I am not sure what this means. Suppose C:\symlink\foo I append 'b',
what is the result in both followLinks states?
* file locations should be returned as relative, not absolute. this will
allow profiles to be moved around. This would require an XP path format.
what does this mean?
Judson Valeski wrote:
> Scott Collins/Frank Tang - specific questions regarding the UTF8'ization
> of all the char*/Unicode methods we have right now. Basically, what
> should be done here? We have a strong UTF8 contingency, but implicity
> UTF8 formatted char*'s are worrying folks.
>
> We discussed nsIFile today, see
> http://www.mozilla.org/projects/embedding/apiReviewNotes.html#nsIFile
> (just checked it in, it may take a few hours before updating), for details.
>
> Pete Collins is going to begin impl'ing and doc'ing. Hopefully we'll be
> done w/ the open issues by the time he's ready to move onto them :-).
>
> Jud
>
>
