First off: You need to understand that no one posting here is speaking for Apple. No one is employed by Apple. We're all just users like you. So there are no "typical Apple responses" here. I'm just someone who's quite familiar with the application, the forum and the questions that come up here.
This question of where the files are stored comes up frequently enough. And in some cases it's asked by people migrating from other OSes. The point I'm making is that it's the wrong question in almost all cases. So, I can tell you that, yes, the files are stored inside the iPhoto Library package. There now, that's that answered. Thread closed. Right?
But it's not. Because the real question is "how do I access my photos to print/edit/upload/ whatever"? And if that's the real question the fact that the files are stored within the Library package not very useful, is it?
So, I try and explain how to access the photos, and, why it's built that way.
Once you get to the "control" word you can see where the issue lies. iPhoto controls your photos in exactly the same way as AddressBook controls your addresses. But you never see people asking 'Where does AddressBook store the addresses"? Because it doesn't matter. AddressBook allows you to do everything you need to do with this material throughout the OS. You can edit it, add to it, export it to standard formats and access it from Applications and dialogues throughout the OS.
Now try that Paragraph again:
iPhoto allows you to do everything you need to do with this material throughout the OS. You can edit it, add to it, export it to standard formats and access it from Applications and dialogues throughout the OS.
And that's the point of a Photo Manager. The files don't matter, the photographs do.
And why are the files hidden (behind what is a very, very thin wall)? Because for years inexperienced Users damaged their libraries by manipulating the data via the Finder. They merrily renamed files and folders, deleted material and trashed their libraries in many ways. Since the package was introduced with iPhoto 08 such postings have reduced enormously.
I assume you are agreeing with my statement that Apple is for a home user, however you are way out there in left field to carry on about using a iPhone to shoot a wedding. That was just a way to dig at something.
Yes I was agreeing with you. i was merely saying that using iPhoto in a pro setting was as appropriate as shooting a wedding with a phone.
You are correct in your statement, however depending on the user this may not be the ideal method.
And in that circumstance... you use an app that works the way you prefer. Word is an enormously powerful application. But it doesn't work the way I like. I don't trash Word because of this. I just use one that works the way I prefer.
I was stating Apples culture; they build their products around the Apple way of doing things. The sad thing is in introduces a lot of threads like this were users have to defend the product regardless if it is flawed or not. (Note I am not referring to iPhoto, this is a general statement of all Apple products regardless if its hardware or software issues).
Try that paragraph using MicroSoft or Adobe instead of Apple. Still works, doesn't it?
Again its all about workflow on what the user likes to do.
So, you find the app that works for you. You don't expect that every app will work the way you want.
because you will need to access your files at some point. For example if I use Adobe Bridge with iPhoto, I will need to access the Master folder at some point.
But you wouldn't want to access your iPhoto files with Adobe Bridge. Why? Remember what I said about users damaging their libraries? A lot of that was done by people using Bridge. Plus, Bridge fulfills something of the same role in the Workflow as iPhoto, and using two managers makes little sense - Like using iPhoto and Lightroom, Or Aperture and Bridge or Lightroom and Bridge, Picasa and Lightroom etc. Using more than one manager is akin to writing your novel in two word processors at the same time. Confusion abounds.
And if you're worrying about Bridge as a front end for Photoshop all of these apps can function instead of Bridge in this role.
but you could accidently offload your camera with iPhoto and need to move everything to a different folder.
Why would you need to access the Masters folder to do that? That's what FIle -> Export is for, no? Moving the files with Bridge and/or the Finder would trash the Library.
- My point here is to simply show that the scenarios you are suggesting have been built-in to the application. Yes, there is a learning curve. There's a learning curve with Bridge, Lightroom, The Finder, Windows Explorer and everything else.
As for your comment about databases: the basic paradigm of computing is changing. We've been working on a crude analogy since the arrival of the GUI. Data is a document, documents are stored in folders, folders go inside other folders and they get put in a filing cabinet. That's all a about documents. Now that machines are much more powerful all the OS designers are moving away from that. Now the model is about managing Data not documents. Soon everything will be a database. Photo apps and NLE video editors have got there first, but now Word Porcessors and Spreadsheets are happening too. And that's happeniong on Windows as well as Macs.
For information on how to run a Referenced Library - and the pitfalls attached - see
https://discussions.apple.com/thread/3062728?tstart=0