Open GoogleCodeExporter opened 8 years ago
Graham,
This is a good idea and we should be moving to inetloc files I think.
Can you please note here or by email to me any documentation you've found on the
format? We need to be able to store additional stuff beyond just the host, name,
path, and password. For example, authentication type information (in the case of
sshfs), and advanced options.
Original comment by mgorb...@gmail.com
on 18 Jun 2007 at 12:41
Experimenting on my own computer,
mimicing the contents of some .inetloc files,
a text file with an .inetloc extension to the filename,
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/
PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>URL</key>
<string>afp://tt@omnium.freeman-centre.ac.uk/Users/tt/</string>
</dict>
</plist>
> cannot be opened [by Finder] because it is damaged
but if I simply change the string,
<string>sftp://tt@omnium.freeman-centre.ac.uk/Users/tt/</string>
then the file launches Cyberduck.
My first experiments caused Cyberduck to present a dialogue requesting the
password for tt ... later
experiments simply caused Cyberduck to launch (without attempting a
connection).
A search of developer.apple.com for inetloc revealed nothing.
FWIW legacy <http://developer.apple.com/technotes/tn/tn1142.html#fndrfls>
explains that Internet location
files created by the Finder will have a creator type of
kInternetLocationCreator ('drag').
If you're wondering ... an .inetloc for an AFP connection appears to use the
resource fork alone.
Utilities such as DeleteFork <http://www.limit-point.com/Utilities.html> can
> move resources from a data fork into the resource fork,
> then delete the data fork
but resource fork data must be written in a certain way for it to be usable by
Finder.
Original comment by grahampe...@gmail.com
on 18 Jun 2007 at 10:32
~/Library/Application Support/MacFusion/Favorites
/Library/Application Support/MacFusion/Favorites
/Network/Library/Application Support/MacFusion/Favorites
-- introduces the slight risk of two or more files (favourites) having the same
name.
Original comment by grahampe...@gmail.com
on 18 Jun 2007 at 11:12
I see at least two other issues associated with this issue 194, I'll distance
them to Milestone-Release1.5 for
review by Michael.
Original comment by grahampe...@gmail.com
on 19 Jun 2007 at 10:40
> risk of two or more files (favourites) having the same name
that is, <http://code.google.com/p/macfusion/issues/detail?id=200>.
Original comment by grahampe...@gmail.com
on 19 Jun 2007 at 10:52
Original issue reported on code.google.com by
grahampe...@gmail.com
on 17 Jun 2007 at 12:06