Hi
I'm going to ask a couple of, sort of, related questions about resource
forks.
In an earlier discussion Doug McNutt mentioned:
BBEdit saves "state" in a database that is associated with
each user so that it is possible for different programmers
editing the same file at different times to retain different
display options.
Does this mean that there is still a resource fork for a BBEdit file?
And now to a broader question about resource forks.
In the next week or so I'm going to be uploading my greatly revamped web-site
to a server. It's all XHTML and CSS now :)
Anyway in the past I used to trash all the resource forks in the web-site
files before uploading to the server knowing they were of no use in that
environment (in the past I used Nisus Writer Classic for HTML creation but
that can't run on Intel Macs so I can't use it any more).
The FTP client I have is Panic's "Transmit" and it has a rather excellent
"Synchronise" feature. However I guess that to use the Synchronise feature I
would be leaving all resource forks in place, such as those on .png, .gif and
.jpg files for example.
So the question this is all leading to is: is it okay just to leave the
resource forks in place when uploading files to servers for use in web-sites?
--
Patrick
--
------------------------------------------------------------------
Have a feature request? Not sure the software's working correctly?
If so, please send mail to <[EMAIL PROTECTED]>, not to the list.
List FAQ: <http://www.barebones.com/support/lists/bbedit_talk.shtml>
List archives: <http://www.listsearch.com/BBEditTalk.lasso>
To unsubscribe, send mail to: <[EMAIL PROTECTED]>
