I wrote:
Can anyone tell me the incantation to get Carbon Squeak on OS X to see an image on a file server created under Windows? There *has to be* a way to do this ...
I'm still clueless as to how to do this under MacOS 9, but under OS X (UNIX wins again!!) the following regime, while disgusting, will work:
1. Create an image that OS X Carbon Squeak will open. Inside Squeak do save as and save the image under the name you would like to copy from your "foreign" file server.
2. Copy the "foreign" image to some temp directory under Mac OS X. (This step can be omitted if you're using NFS or some other file system for which the following command will work directly.)
3. At the shell, overwrite .image and .changes files you made in step 1 by dd'ing them from the files you made in step 2.
Woila, Carbon Squeak will now see and open the image.
--- Jim Rosenberg http://www.well.com/user/jer/ CIS: 71515,124 WELL: jer Internet: jr@amanue.com
- Create an image that OS X Carbon Squeak will open. Inside Squeak do
save as and save the image under the name you would like to copy from your "foreign" file server.
- Copy the "foreign" image to some temp directory under Mac OS X. (This
step can be omitted if you're using NFS or some other file system for which the following command will work directly.)
- At the shell, overwrite .image and .changes files you made in step 1 by
dd'ing them from the files you made in step 2.
To me, this sounds like Mac file type / creator code issues, The Mac prior to OS X stores meta-data about the types of files. This allows files to maintain their type without requiring a specific file extension (as Windows does.)
Mac OS X complicates this, because it still respects the file type metadata but also uses extension information,
The problem is that, even if your .image and .changes files were copied properly, the meta-data is not preserved since most other operating systems do not have the same concept of meta-data.
I suspect the solution you want is the "Fix Squeak Files For Mac" application you'll find at ftp://st.cs.uiuc.edu/pub/Smalltalk/Squeak/3.0/mac/extraFiles/FixSqueakFilesForMac.sit
This program uses the extensions to give the Squeak files their proper file type. Drag and drop your foreign image and changes files on to this app. If all goes well, the icons should change to some Squeak-looking icons.
-Eric
Eric Scharff wrote:
- Create an image that OS X Carbon Squeak will open. Inside Squeak do
save as and save the image under the name you would like to copy from your "foreign" file server.
- Copy the "foreign" image to some temp directory under Mac OS X. (This
step can be omitted if you're using NFS or some other file system for which the following command will work directly.)
- At the shell, overwrite .image and .changes files you made in step 1 by
dd'ing them from the files you made in step 2.
To me, this sounds like Mac file type / creator code issues, The Mac prior to OS X stores meta-data about the types of files. This allows files to maintain their type without requiring a specific file extension (as Windows does.)
Yes, we know this. :-) The frustrating thing is that there isn't a simpler way in OS X (or OS 9 or any other Mac OS) to fix the file type problem for files downloaded from other operating systems, etc.
OS X actually comes close to handling this reasonably... if you double-click on the raw downloaded .image icon, it will prompt you with a dialog to select an application to run. So, we should be able to select the appropriate VM from this dialog, and all will be well, right? Wrong, it only seems to let you select an application with the appropriate matching file type (which the VM does not match), and the dialog doesn't offer any option to view "all files" or similar. AARGH! (Memo to myself: Must punish the person responsible for this "feature".)
- Doug Way dway@riskmetrics.com
To me, this sounds like Mac file type / creator code issues, The Mac prior to OS X stores meta-data about the types of files. This allows files to maintain their type without requiring a specific file extension (as Windows does.)
Yes, we know this. :-) The frustrating thing is that there isn't a simpler way in OS X (or OS 9 or any other Mac OS) to fix the file type problem for files downloaded from other operating systems, etc.
OS X actually comes close to handling this reasonably... if you double-click on the raw downloaded .image icon, it will prompt you with a dialog to select an application to run. So, we should be able to select the appropriate VM from this dialog, and all will be well, right? Wrong, it only seems to let you select an application with the appropriate matching file type (which the VM does not match), and the dialog doesn't offer any option to view "all files" or similar. AARGH! (Memo to myself: Must punish the person responsible for this "feature".)
- Doug Way dway@riskmetrics.com
1) Now be nice since that code is my fault. I spent a few minutes today fixing this. With the carbon mach-o version of 3.2.1Beta5 it links .image files with the Squeak VM, so installing the new VM gives you new icons and helps the finder find the owners for .image files.
2) The open file dialog box now will consider that a file is a valid file if it is a STim file type, or if the file name suffix matches the list of valid suffixes in an existing isThisAnImageFile check function.
So now you can do 'touch foobar.image' and it will appear as a squeak image, you won't get far trying to open that file, but this enables you to open images that have lost all traces of meta data.
Mmm I could add the feature to view 'all files' if one wants, but I'd think restricting the option to files of a know suffix might be safer, no?
John M McIntosh wrote:
OS X actually comes close to handling this reasonably... if you double-click on the raw downloaded .image icon, it will prompt you with a dialog to select an application to run. So, we should be able to select the appropriate VM from this dialog, and all will be well, right? Wrong, it only seems to let you select an application with the appropriate matching file type (which the VM does not match), and the dialog doesn't offer any option to view "all files" or similar. AARGH! (Memo to myself: Must punish the person responsible for this "feature".)
- Doug Way
- Now be nice since that code is my fault. I spent a few minutes
today fixing this.
Ah, somehow I was thinking that it was a generic dialog and thus someone at Apple's fault.
In any case, idle threats can sometimes be effective in getting things fixed. ;-)
With the carbon mach-o version of 3.2.1Beta5 it links .image files with the Squeak VM, so installing the new VM gives you new icons and helps the finder find the owners for .image files.
- The open file dialog box now will consider that a file is a valid
file if it is a STim file type, or if the file name suffix matches the list of valid suffixes in an existing isThisAnImageFile check function.
Sounds good!
So now you can do 'touch foobar.image' and it will appear as a squeak image, you won't get far trying to open that file, but this enables you to open images that have lost all traces of meta data.
Mmm I could add the feature to view 'all files' if one wants, but I'd think restricting the option to files of a know suffix might be safer, no?
Since image files will pretty much always have a .image suffix, restricting it to just those files is probably fine.
- Doug Way dway@riskmetrics.com
squeak-dev@lists.squeakfoundation.org
-
Doug Way -
Eric Scharff -
Jim Rosenberg -
John M McIntosh