I am managing the network in my company.... and I have a lot of users who might want to create a library.
The macs user authentication is through binding to an AD domain, so the home directory is an SMB share, enforced by the domain (and iPhoto doesn't support creating a library on it.. )
I want my users to create they're library on a network share, so it will pass with them among computers....
and most important - I don't want to help users with it - I want it to just work...
because of that - I need it to work
I'm not sure if I was clear, so let me know if you didn't understand why I need it....
No it is not clear to me (but that probably has nothing to do with your description but my technical capabilities) - I doubt that you will find that answer here since this forum is made up of iPhoto users not iPhoto (or Mac) developers and it is not likely that any of the users here have that inside knoledge of iPhoto
And I suspect that what you want to do is beyond the capabilities of a virtually free program like iPhoto - although since I do not understand it I certainly am not sure
You might have bettter response in more technical forums about Mac application or scripting - you really are lookfor informatin on using the Mac, not using iPhoto
On the surface it seems that if users can create a file on their home directory to import a photo that they could create an iPhoto library in their pictures folder - but since I don't understand that probablhy is meaningless
Unless you can offer a share/location that is formatted OS X Extended (journaled) with the ownership set to be ignored you won't be able to share an iPhoto library over a network. You could have a dedicated host Mac on the network with a user account for each who want to have a library accessable from all Macs. Their library could then be copied to their account on that Mac and they could log in and access it from any Mac on the LAN.
Note: you won't want to access the library wirelessly as that is susceptable to occasional dropouts and if one occurs while iPhoto is writing to the database file the database will be damaged.
This I understand.
I have a share it can write to.
the only problem - is that it is not the default home directory.
I want my users to just open the application, click the "create library" and be directed to that share.
but after configuring the "defaults" from above - it doesn't map the user to the "defatult" library, it maps them to their home directory.
Do you know how to configure that?
it sounds to me like a bug, because after configurying the defaults from above - opening an existing library maps the user to the right directory.
also - if I try to create the library on the "bad" home directory, and it fails (as expected) - it changes the defaults to the home directory.....
Yes Apple charges for support - is this a bug? to me it sound like you are trying to do something tha tsimply is not supported and is far beyond the intended use of a free program - but I have no idea nor do I set apple policies - your choices are to submit feedback and see what happens - you will not receive a response - or to call support - maybe they will not charge - maybe they will - again I am just a user no different than you -
If it is a bug and Apple includes the fix in an upgrade then it will be fixed - the charge is not for fixing a bug but for diagnoising your issue which may or may not be a bug
I tell you why I think it is a bug:
there is a configuration for a default behavior of the application.
in one use case (openning an existing library in our case) - it uses the default configuration.
in another use case (creating a new library) - it ignores that.
Since the parameter name is "RootDirectory" (or "LibraryPath") - the name suggests it should behave the way I expect it to (if it wasn't ment for that use - the name of it should have been different).
But - I am a software architect, and currently I'm helping with automating processes... so my expertise is not related at all to using applications (and specifically - the iPhoto)...