Ticket #30 (assigned enhancement)
Connection assistant
| Reported by: | grahamperrin | Owned by: | mgorbach |
|---|---|---|---|
| Priority: | major | Milestone: | Later |
| Component: | MacFusion | Version: | |
| Keywords: | Cc: | grahamperrin |
Description
Connection assistant
Beyond the checks (in MacFusion 1.2 Beta 3) with which we are familiar:
- I'd like an assistant to check that the connection/volume supports ._ dot underscore files
- primarily in the manner and sequence used by (ubiquitous) Finder
- in other manners, if necessary (I haven't thought that far ahead).
Assistance should be optional:
- a preference within MacFusion?
- ideally, the preference should be available per-connection, so that experienced users can
- work with less compatible volumes
- without being assisted/cautioned every time the volume is mounted.
Implementation
I wondered whether an assistant might:
- walk a hierarchy
- seek and find a directory to which writing is possible
- perform tests
— but my concern is that with some types of hierarchy, the walk/seek/find operation could be wasteful or time-consuming.
So, an assistant might instead
- prompt the user to select a directory to which writing is possible
- perform tests.
Motivation
Following my first observations of Finder 10.5.3 with WebDAV I did some testing
- with SSHFS
- with cp
- with and without the -X option
- with TextEdit, Smultron, Word 2008 and other applications.
First impressions:
extended attributes and the resulting
._ files
are the norm (not the exception).
The presence of something as simple as a type code will normally require a ._ file when that type of file is saved or copied to a filing system that does not support such attributes. This is true even for the cp command (without the -X option).
Summary
Need to identify connections/volumes/file systems that are not wholly compatible with Mac OS X ways of working with extended attributes.
