Talk:Resource fork

From Wikipedia, the free encyclopedia

This article is part of WikiProject Macintosh. This means that the WikiProject has identified it as an article pertaining to Apple Computer, but is not currently working to improve it. WikiProject Macintosh itself is an attempt to improve, grow, standardize, and attain featured status for Wikipedia's articles related to Apple Macintosh and Apple Computer. We need all your help, so join in today!
??? This article has not yet received a rating on the assessment scale.
News This article has been cited as a source by a media outlet. See the 2004 press source article for details.
  • "The Terminal in OS X." (July 15, 2004). Sitepoint. [1].

Could someone translate the japanese version of this page to English - it is much longer than this.

Listed on translation requests —Home Row Keysplurge 22:39, 21 May 2006 (UTC)
All the information from the Japanese Wikipedia article for resource fork has now been translated and added to the English article. It might require editing to make it consistent (notably, the detail about MFS below), and should probably be given some sort of structure, since at the moment the first section is a series of paragraphs with little connection between them. - Grgcox 16:11, 18 September 2006 (UTC)

[edit] MFS had it too

The first sentence of the article asserts that the resource fork is something that enxists in HFS and HFS Plus but that's not accurate. It existed from the beginning, in the days of MFS. ;Bear 00:22, 2004 Nov 6 (UTC)

Could you point to a source to back this up? To be clear I'd be willing to bet you are right, I'd just like to see a source to remove all doubt. AlistairMcMillan 08:43, 6 Nov 2004 (UTC)
Inside Macintosh from the very boopseginning, when it was loose-leaf. I ditched my copy years ago as it had become so obsolete. Maybe somebody else has one. ;Bear 22:10, 2004 Nov 6 (UTC)
I hereby do declare and proclaim that I've used MFS disks myself in the olden days and yes, Macintosh files have always had resource forks, even in the MFS days. - Cymydog Naakka 15:23, 8 Nov 2004 (UTC)
Res forks were indeed part of MFS. I have reworded the article - see if you think it's OK. I have stated that the resource fork is a construct of the operating system, though it's implemented in the file system. I think this is reasonable, since conceptually the res fork exists even if the actual implementation is in a separate file, as it is for many OS X apps - to the programmer the separate file still "looks like" the traditional resource fork.Graham 22:32, 8 Nov 2004 (UTC)

[edit] cleanup

Hi Graham. You're right, it's by no means a bad article. I've certainly seen—and probably even written—worse. I added the cleanup tag as I think the writing style is a bit uneven, and the article could do with a clearer structure. More a bit of spit and polish than anything else.

It's the sort of thing I'm not very proficient at, so I decided I'd mark the article and come back to it at some other point.

As regards structure, one possible divide I had in mind was to split it into the following sections (in no particular order):

  • brief intro
  • filesystem and communications (dual forks, streams and attributes in other OSes, binhex et al)
  • the original intent and actual use (metadata for some documents, CODE resources, GUI resources etc)
  • Limitations (slow, prevented swapping in blocks of code; 'the resource manager is not a database')
  • the APIs and other implementations
  • the history/future/influence.

What do you think? Cmdrjameson 23:50, 7 February 2006 (UTC)

Looks OK, though possibly reverse (2) and (3) since the need for such a thing will probably provide a better background to the implementation. I agree it's a little uneven, but it can probably be licked into shape with fairly minimal work. Graham 23:55, 7 February 2006 (UTC)

I have here with me a bunch of books that talk about resource forks. In faculty's library there exists I to VI inside macintosh volumes, so in the next week or so i'll post a more detailed description of resource forks. Cariquez 20:00 24 February 2006 (GMT)

Once someone does the cleanup, here are a few more things that could be added:
  • to be precise, the Resource Fork is not the database but just a second _file_ (i.e. sequential stream of bytes) attached to the main file. This fork may as well contain random binary data, at least the file system allows that. The database needs to be named differently, e.g. "Resource File" (which appears to be the name used by Apple in many places) or "Macintosh Resource", perhaps?
  • speaking of forks: other file systems, e.g. NTFS and HFS Plus, have the concept of multiple forks in a file, meaning that even more metadata can be stored in additional forks.
  • Not only MFS, HFS and HFS+, but also UDF and ISO 9660 provide support for storing Macintosh Resource Forks (ask me if you need more info on this, I've done a lot of programming in that area)
Tempel 07:54, 23 March 2006 (UTC)
You're right that the fork is just a file stream, like any other. However, since the Resource Manager assumes ownership of this stream and imposes its own format upon it, it's good enough to talk about the fork and the database as one and the same thing. After all, we are not an apple developer documentation source, but an encyclopedia. I agree it's worth listing the file systems that support it. Graham 09:50, 23 March 2006 (UTC)
Graham: Good points. I agree with you. Tempel 12:13, 28 March 2006 (UTC)

[edit] Operating Systems were commonplace

"Unlike most prior microcomputer systems, in which programs directly accessed hardware and were responsible for user interaction and input/output themselves, the Macintosh provided operating system services for many I/O functions, notably the graphical user interface." I think this sentence is misleading. There were a lot of general purpose computers before the Macintosh which had an operating system "for many I/O functions". Few of them had a GUI, that is true, but even today the line between the GUI and the OS is blurry. In addition to being somewhat untrue, saying 'the mac was unique at the time because it had an OS' doesn't have a lot to do with the fact that it's file system had a feature for storing file metadata specially. I mean, we could also say 'the mac was one of the first computers to have a mouse' in this article as well, but it wouldn't be pertinent. Jfm3 15:46, 11 June 2006 (UTC) jfm3