Re: Problem with Cocoa App on FAT32-formatted external drive
Re: Problem with Cocoa App on FAT32-formatted external drive
- Subject: Re: Problem with Cocoa App on FAT32-formatted external drive
- From: Andrew Merenbach <email@hidden>
- Date: Fri, 25 Aug 2006 10:11:14 -0700
Hi, Glenn.
You say that separate partitions are out of the question, but how
about this:
Create a disk image, formatted HFS+, and put your Mac version of the
program onto it. Then put MyApplication.dmg (or whatever you happen
to call it) on the FAT32 disk.
This way, you can run your Mac app from a "virtual" (sort of) Mac
partition and still (theoretically) access database resources on the
FAT32 volume.
Cheers,
Andrew
On Aug 25, 2006, at 7:40 AM, Glenn Zelniker wrote:
I've hit the web looking for answers to this question but haven't
found anything definitive...
I have an app I've written that needs to live side-by-side with a
Windows app on a FAT32-formatted external drive. The user will be
running only one of the apps at a time, but both apps need to be
able to access common resources: jpg images, PDFs and the like, and
a SQL database. FAT32 was chosen as the format because the Windows
app is the more common deployment and it can't write to the
database if the disk uses HFS(+).
On Tiger, everything *usually* works fine, but on Panther there are
big problems with case-sensitivity. In particular, if I look inside
the app bundle using the Finder in Panther, I can see that some of
the resources have had their names and/or extensions randomly
capitalized. This is problematic because many of my GUI elements
are "skinned" and have TIFFs or PNGs as button images and
backgrounds. At runtime, the GUI elements are, of course, missing
from the screen!
I can, of course, make my code look for files in a case-insensitive
manner -- this is simple enough to do in places where the user
wants to open a file or when I want to populate a matrix of
thumbnail images, for example. But the real difficulty for me is in
dealing with the GUI bits that I've done using IB. There are
literally hundreds of NSButtons, NSImageViews, and the like that I
have "married" to image resources using IB and it would be a
nightmare to have to go into my code and set the images
programmatically. It gets even worse when you consider that many of
the buttons have multiple states that are represented with
alternate images, which is easy to handle in IB but not a lot of
fun to handle programatically when there are several hundred
elements to deal with.
BTW, separate partitions are out of the question from a
manufacturing point-of-view. Any advice would be appreciated.
Glenn Zelniker
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40ucla.edu
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden