Quote
First, are you saying the endian order switches half way through the file??
I believe the resource format is very similar indeed. I guess I am the only one coding C, but if more were, someone should simply "port" the Macintosh Resource Manager to work with the rez format. i.e. GetRezResource, AddRezResource, WriteRezResource etc. Doing so would let Mac apps read and write the files natively and would make the process elementary.
The resource format has to be public knowledge, and if not, someone must of reverse-engineered it by now. Anyone willing to do a quick comparison?
(/B)
The problem is two-fold. The people who did WinEVN didn't do what you suggest, they made a way to convert the resource-fork data into normal data, and changed the EVN engine to work with this new data format.
The problem is a major difference in the way files are stored under Windows and MacOS... Windows uses vfat, which just has one place to store data in a file. MacOS uses hpfs(?), which apparently gives a file 2(or more, I dunno) places to store data... a data fork, which is just like the windows one, and a resource fork, which is where all the EV data is stored. To store Mac files under Windows and maintain that resource data requires a special format, called MacBinary(.bin). This format isn't toooo horrid, but really isn't exactly convienient.
Porting the Mac Resource Manager would require the permission of Apple, which, well, isn't likely, IMHO.
As a side note, I also work in C/C++(under windows) which will be rather handy when I have to convert all these Big Endian numbers around.
------------------
--
Alkiera Kerithor
