** with apologies for cross-posting **

On 22 May 2007, at 07:40, sbbluebox wrote:

> working with macfusion, macfuse & ntfs-3g
>
> - using normal ftp-apps will avoid copying "._ files" to the server,

   This is sometimes a bad thing. I have recently reviewed my opinions
   of previously valued 'normal' FTP- and SFTP-oriented applications.
   (A separate thread. More on this to follow.)

> but if you mount your ftp-directory with macfusion on your desktop
> these files will created. Especially for instant edting of *.css &
> *.html files or copying them to your web-directory via finder this
> will a greater issue, because e.g. pmwiki is not able to load a unique
> file anymore, due to the both files named "my_html.tmpl" &
> "._my_html.tmpl". Any ideas to handle this?

Issues such as this are, IMO, most definitely problems for end users.

Consider my thoughts at
<http://code.google.com/p/macfusion/issues/detail?id=115#c4> but
please note that the issue there is _specific to Xbox_ and I'm doing
plenty of _guesswork_.

Defocusing from pmwiki and Xbox, I predict a variety of curious or  
annoying situations, arising from the way that Finder (Mac OS X 10.4)  
copies from multi-fork capable file systems including *but not  
limited to* HFS+.

<http://code.google.com/p/macfusion/issues/detail?id=45> for examples  
of other multi-fork capable protocols/systems.

That prediction need not be gloomy. I have contacts, way beyond  
MacFusion, with individuals and groups who may have vested interests  
in solving (or at least working around) such issues. I can't promise  
anything, but ... watch this space.


##

In the meantime, for sbbluebox, a question/suggestion:

If you use something like GrimRipperCM
<http://free.abracode.com/cmworkshop/grim_ripper.html> to positively  
strip the resource forks from source files, prior to Finder copying  
to the remote destination:

   * do you still end up with ._ dot underscore counterparts at the  
destination?

(Don't remove resource forks unless you _really_ want to do so.)


## Applications' occasional disrespect for
## deprecation of resource forks

Whilst resource forks may be deprecated, not all 'modern'  
applications respect that deprecation. (AFAIK for years following the  
introduction of Mac OS X, Microsoft Office continued to needlessly  
add a resource fork to each and every file that it saved. Don't get  
me started on Microsoft.)

Finder aside:

   * might the applications that are used for
     editing of .css and .html files be
     adding resource forks where they are not needed?

If application developers (some of whom have a Windows-oriented  
heritage) follow Microsoft's published statements on the purpose of  
resource forks, then those developers may well misunderstand the true  
purpose.

-- 

Graham Perrin
MacFusion Project member (non-code contributor)
<http://code.google.com/p/macfusion/>

MacFusion - a GUI for MacFUSE
<http://www.sccs.swarthmore.edu/users/08/mgorbach/MacFusionWeb/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"macfuse-devel" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/macfuse-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to