Trying to understand iphoto 'structure'

ok so i have some photos on one of my three hard drives in my mac pro.. when i import them into iphoto library, something happens within the pictures folder inside of the user folder. I see what appears to be a duplicate of the original photo.
is this a correct observations, and if so, am i actually decreasing my overall harddrive space because of it, OR, are those just thumbs of the originals..? thxs.
only been using iphoto for a couple months. i trying to just figure out the structure of the sofware.
thxs

If Terence jumps in, he can probably explain this better but...
Among other things, there's an "Originals" folder that contains the original (surprise) "out of the camera" files. IF you modify any photos, the modified version will go into (surprise, again) a "Modified" folder. In addition, there's a "Data" folder that contains small thumbnails versions.
Don't be concerned about looking around but do not so much as think of changing any internals. That's a sure invitation to bleeding ulcers. It's OK to rename and/or move the library folder itself (perhaps because you want several libaries) but do not ever muck around with the internals. You can do absolutely anything you want from inside the iPhoto application itself and you're most welcome to post back here should you need assistance.

Similar Messages

  • Still trying to understand iPhoto's trash

    So I have decided to get really organized in iPhoto and am using the Albums to do my main organization to create slide shows etc. I chose Albums over Events because I could not move the photos around in Events.
    Then I started deleting away the shots I thought were not good. Just so happens I was a little to delete-key happy and I deleted some that I shouldn't have.
    Now I go to iphoto trash. First I cannot look at the photos at a large scale by double clicking on it. When I use the toggle at the bottom to enlarge all photos I quickly loose track of the photo I was wanting to look at. Even if that photo is selected it still does not center the enlargement on that photo. (annoying)
    So to look at it I have to restore it or move it back to the library. Being a person who is using Albums to organize my photos, I would have preferred to move it directly into the Album. Not possible.
    Now what I have deciphered as the only way to get out of this mess ...
    First I have to restore the photo then go back to Events and find that single photo in the mix of hundreds of other photos, and then if it is indeed the photo I was looking for, then I move it back to the Album.
    This is sure a lot of work, and makes me rather disenchanted with iPhoto. I think it should be easier than this!
    So my questions :
    Are Albums the right way to organizing photos in iPhoto, or is there a better way? And why can't we organize and move photos around simply in Events?
    Is it possible to indefinitely delete one photo from the trash and not empty the whole trash in iPhoto?
    I have not found a conversion feature in iPhoto similiar to iTunes... for example sometimes I have some photos which I would like to keep in high resolution, but others I could reduce their size to make space. I know I can use photoshop to do this but its very time-consuming. Is there another way to batch process photos?
    thanks for taking the time answer my questions!

    Melissa
    Welcome to the Apple user to user assistance forums
    Are Albums the right way to organizing photos in iPhoto, or is there a better way?
    Yes - albums and smart albums( using keywords) are the way. When you keyword and rate your photos smart albums become very powerful
    And why can't we organize and move photos around simply in Events?
    Because that is not the way iPhoto works - this is a user forum and we can tell you how it works - you need to talk to Apple about why it works like it does and to suggest changes - iPhoto menu ==> provide iPhoto feedback
    Is it possible to indefinitely delete one photo from the trash and not empty the whole trash in iPhoto?
    No
    I have not found a conversion feature in iPhoto similiar to iTunes... for example sometimes I have some photos which I would like to keep in high resolution, but others I could reduce their size to make space. I know I can use photoshop to do this but its very time-consuming. Is there another way to batch process photos?
    iPhoto always keeps the original, the digital negative - you can not change that
    LN

  • Trying to Understand the Structure of table GLPCT

    Hello SCN Community,
    I'm in the process of learning about how the fields in table GLPCT are closely connected to fields in related tables such as GLPCA, GLPCC, and GLPCO. All has been accomplished except for the source of GLPCT-SOBJNR (Object number for FI-SL tables). I suspect that the value stored in this field comes from another 'check' type of table just as the value in GLPCT-ROBJNR is derived from table GLPCO and GLPCT-COBJNR is derived from table GLPCC. However, I have searched the SAP data dictionary, SDN, OSS, and the internet in general without any luck of locating this information. I appreciate in advance anyone's time and effort.
    Our team is using SAP ECC 6.0
    Thanks and regards,
    -Steve

    Hello SCN Community,
    I'm in the process of learning about how the fields in table GLPCT are closely connected to fields in related tables such as GLPCA, GLPCC, and GLPCO. All has been accomplished except for the source of GLPCT-SOBJNR (Object number for FI-SL tables). I suspect that the value stored in this field comes from another 'check' type of table just as the value in GLPCT-ROBJNR is derived from table GLPCO and GLPCT-COBJNR is derived from table GLPCC. However, I have searched the SAP data dictionary, SDN, OSS, and the internet in general without any luck of locating this information. I appreciate in advance anyone's time and effort.
    Our team is using SAP ECC 6.0
    Thanks and regards,
    -Steve

  • Trying to understand how iPhoto keeps track of pictures...

    I am trying to understand how iPhoto stores & organizes pictures.
    I moved JPEGs from a portable drive to my hard drive, set iPhoto's preferences to not copy pictures when importing them, then imported them. Unfortunately, all pictures from a certain import has duplicated in iPhoto.... so I "moved to trash" all pictures from that import and tried importing again since the JPEGs were still where I moved them to. When importing, it said they were duplicated .
    I am confused. If I "move to trash", I assumed it got rid of whatever index (and preview cache) to that particular JPEG. I was actually surprised it did not delete the actual JPEG but I'm ok with that.
    Can someone help explain this behavior?
    Thanks
    -Ed

    iPhoto is a relational database program
    In the strongly recommended managed library (you have chosen to ignore this recommendation and use a referenced library) imported photos are copied to the iPhoto library and stored in the originals folder, a thumbnail jPEG is created and places in the data folder and when any modification is made (including autorotation) a modified version of the photo is created and placed in the modified folder. iPhoto updates its database entries to reflect everything it does.
    It is critical that you do not make any modifications of any sort to the content or structure of the iPhoto library - doing so is likely to corrupt the library and cause you to lose data.
    When you use the referenced mode which you are doing (and which is not recommended) you are taking total responsibility for the original photos which included not moving or modifying them while iPhoto is referencing them
    Unfortunately, all pictures from a certain import has duplicated in iPhoto.... so I "moved to trash" all pictures from that import
    Did you do this with the iPhoto trash? or did you use the finder to modify the contents of the iPhoto library.
    If I "move to trash", I assumed it got rid of whatever index (and preview cache) to that particular JPEG. I was actually surprised it did not delete the actual JPEG but I'm ok with that.
    again - iPhoto trash or finder trash. If you move a photo to the iPhoto trash and empty it all traces of that photo in the iPhoto library will be removed - nothing will be done to any file outside of the iPhoto library -- ever
    LN

  • I was trying to move iphoto library to my external hardrive, realised it was incompatible with Mac.  The iphoto will not open now, message is "Iphoto library is either in use by another application or has become unreadable".  I have read other posts.

    Hi,
    I was trying to save a copy of my iphoto library by copying images to my external harddrive.  I wasn't sure how to do it, realised the hard drive is not compatible. Now the iphoto library wont open and reads "iphoto library is either in use by another application or has become unreadable".
    I have tried to use options command and click on iphoto then rebuild yet nothing happens and same error message occurs.
    I have gone to  my personal drive, desktop, iphoto library, and found file Albumdata.xml and when i click on it, there is a lot of text in it, i am assuming these are all my photos.
    I have tried clicking and dragging this file to iphoto app and it doesn't work, as the same error comes up in iphoto being in use or unreadable....
    What am I meant to do with albumdata.xml file and how do I reopen Iphoto from here on in?
    Please help as I am not technically minded and still trying to understand how to use the Macbook at all as I am used to Microsoft.
    Thank you very much,
    KS

    Rule Number One - NEVER go directly uinto the iPhoto library - there are no user servicable parts in it and making any change no matter how small can corrupt your library and cause data or photo loss
    Exactly how were you trying to save a copy of your iPhoto library?
    Albumdata.xml does not contain your photos - and again NEVER make any changes to the content of the iPhoto library - no dragging - no changes - never go into the library
    We need to know exactly what you did
    And probalby the easiest solution is to load your backup from before you messed things up
    For reference after you get things working
    Moving the iPhoto library is safe and simple - quit iPhoto and drag the iPhoto library intact as a single entity to the external drive - depress the option key and launch iPhoto using the "select library" option to point to the new location on the external drive - fully test it and then trash the old library on the internal drive (test one more time prior to emptying the trash)
    And be sure that the External drive is formatted Mac OS extended (journaled) (iPhoto does not work with drives with other formats) and that it is always available prior to launching iPhoto
    And backup soon and often - having your iPhoto library on an external drive is not a backup and if you are using Time Machine you need to check and be sure that TM is backing up your external drive
    LN

  • Trying to understand the basic concept of object oriented programming.

    I am trying to understand the basic concept of object oriented programming.
    Object - a region of storage that define is defined by both state/behavior.
    ( An object is the actual thing that behavior affects.)
    State - Represented by a set of variables and the values they contain.
    (Is the location or movement or action that is the goal that the behavior is trying to accomplish.)
    Variables- (What does this mean?)
    Value - (What does this mean?)
    Behavior - Represented by a set of methods and the logic they implement.
    ( A set of methods that is built up to tell's the how object to change it's state. )
    Methods - A procedure that is executed when an object receives a message.
    ( A very basic comand.For example the method tells the object to move up, another method tells the method to go left. Thus making the object move up/left that combination is the behavior.)
    Class - A template from which the objects are created.
    ( I am very confused on what classes are.)
    - The definitions of the words I obtained from the "Osborne Teach Yourself Java". The () statements are how I interperate the Mechanisms (I do not know if Thats what you call them.) interact with each other. I understand my interpretation may be horribly wrong. I will incredibly appreciate all the support I may get from you.
    Thank you

    Object oriented programming is a replacement for the older idea of procedural programming (you can research procedural programming in google). As I understand it, in procedural programming, you have a step by step set of function calls to accomplish some task. Each function receives a data structure, manipulates it, and passes it to the next function. The problem with this is that each function preforms some action for the overall task and can't easily be reused by some other task. Its also harder to read the flow of what is happening with raw data structures flying all over the place.
    In object oriented programming, an object calls a function of another object and receives back, not a data structure, but another object. Objects contain a data structure that can only be accessed by its functions. An object is not so much a sub component of a bigger task, as it is a service that any other task can use for any purpose. Also, when you pass an object to the caller, the caller can ask questions about the data structure via its functions. The developer doesnt have to know what the previous function did to the data by reading up on any documentation, or having to reverse engineer the code.
    I suggest the best way of learning this is to code something like a library object.
    A library object contains a collection of book objects
    A book object contains a collection of chapter objects
    A chapter object contains a collection of paragraph objects
    A paragraph object contains a collection of sentence objects
    A sentence object contains a collection of word objects.
    Add functions to each object to provide a service
    Example: A library object should have a:
    public void addBook(Book book)
    public Book getBook(String title)
    public boolean isBookInLibrary(String title)
    The key is to add functions to provide a service to anyone who uses your object(s)
    For example, what functions (service) should a paragraph object provide?
    It shouldn't provide a function that tells how many words there are in a sentence. That function belongs to a sentence object.
    Lets say you want to add a new chapter to a book. The task is easy to read
    if you write your objects well:
    Sentence sentence1=new Sentence("It was a dark and stormy night");
    Sentence sentence2=new Sentence("Suddenly, a shot ran out");
    Paragraph paragraph=new Paragraph();
    paragraph.addSentence(sentence1);
    paragraph.addSentence(sentence2);
    Paragraphs paragraphs=new Paragraphs();
    paragraphs.addParagraph(paragraph);
    Library library= new Library();
    library.getBook("My Novel").addChapter("Chapter 1",paragraphs).
    Now, lets say you want to have a word count for the entire book.
    The book should ask each chapter how many words it contains.
    Each chapter should ask its paragraphs, each paragraph should ask
    its sentences. The total of words should ripple up and be tallied at each
    stage until it reaches the book. The book can then report the total.
    Only the sentence object actually counts words. The other objects just tallies the counts.
    Now, where would you assign a librarian? What object(s) and functions would you provide?
    If written well, the project is easily extensible.

  • Trying to understand BtrFS snapshot feature

    I'm trying to understand how the copy-on-write and Btrfs snapshot works.
    Following simple test:
    <pre>
    # cd /
    # touch testfile
    # ls --full-time testfile
    -rw-r--r-- 1 root root 0 2012-10-15 12:04:43.629620401 +0200 testfile
    Test 1:
    # btrfs subvol snapshot / /snap1
    # touch testfile
    # ls --full-time testfile /snap1/testfile
    -rw-r--r-- 1 root root 0 2012-10-15 12:04:43.629620401 +0200 /snap1/testfile
    -rw-r--r-- 1 root root 0 2012-10-15 12:07:38.348932127 +0200 testfile
    Test 2::
    # btrfs subvol snapshot / /snap2
    # touch testfile
    # ls --full-time testfile /snap1/testfile /snap2/testfile
    -rw-r--r-- 1 root root 0 2012-10-15 12:04:43.629620401 +0200 /snap1/testfile
    -rw-r--r-- 1 root root 0 2012-10-15 12:07:38.348932127 +0200 /snap2/testfile
    -rw-r--r-- 1 root root 0 2012-10-15 12:09:21.769606369 +0200 testfile
    </pre>
    According to the above tests I'm concluding/questioning the following:
    1) Btrfs determines which snapshot maintains a logical copy and physically copies the file to the appropriate snapshot before it is modified.
    a) Does it copy the complete file or work on the block level?
    b) What happens if the file is very large, e.g. 100 GB and there is not enough space on disk to copy the file to the snapshot directory?
    c) Doesn't it have a huge negative impact on performance when a file needs to be copied before it can be altered?

    Hi, thanks for the answers!
    I guess calling it "logical copy" was a bad choice. Would calling the initial snapshot a "hard link of a file system" be more appropriate?
    Ok, so BTRFS works on the block level. I've done some tests and can confirm what you said (see below)
    I find it interesting that although the snapshot maintains the "hard link" to the original copy - I guess "before block image" (?) - there really is no negative performance impact.
    How does this work? Perhaps it is not overwriting the existing file, but rather creating a new file? So the snapshot still has the "hard link" to the original file, hence nothing changed for the snapshot? Simply a new file was created, and that's showing in the current file system?
    It actually reminds me of the old VMS ODS filesystem, which used file versioning by adding a simicolon, e.g. text.txt;1. When modifying the file the result would be text.txt;2 and so on. When listing or using the file without versions, it would simply show and use the last version. You could purge old version if necessary. The file system was actually structured by records (RMS), similar like a database.
    <pre>
    [root@vm004 /]# # df -h /
    Filesystem Size Used Avail Use% Mounted on
    /dev/sda3 16G 2.3G 12G 17% /
    # time dd if=/dev/zero of=/testfile bs=8k count=1M
    1048576+0 records in
    1048576+0 records out
    8589934592 bytes (8.6 GB) copied, 45.3253 s, 190 MB/s
    Let's create a snapshot and overwrite the testfile
    # btrfs subvolume snapshot / /snap1
    # time dd if=/dev/zero of=/testfile bs=8k count=1M
    dd: writing `/testfile': No space left on device
    491105+0 records in
    491104+0 records out
    4023123968 bytes (4.0 GB) copied, 21.2399 s, 189 MB/s
    real     0m21.613s
    user     0m0.021s
    sys     0m3.325s
    <pre>
    So obviously the there is not enough space to maintain the original file and the snapshot file.
    Since I'm creating a complete new file, I guess that's to be expected.
    Let's try with a smaller file, and also check performance:
    <pre>
    # btrfs subvol delete /snap1
    Delete subvolume '//snap1'
    # time dd if=/dev/zero of=/testfile bs=8k count=500k
    512000+0 records in
    512000+0 records out
    4194304000 bytes (4.2 GB) copied, 21.7176 s, 193 MB/s
    real     0m21.726s
    user     0m0.024s
    sys     0m2.977s
    # time echo "This is a test to test the test" >> /testfile
    real     0m0.000s
    user     0m0.000s
    sys     0m0.000s
    # btrfs subvol snapshot / /snap1
    Create a snapshot of '/' in '//snap1'
    # df -k /
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/sda3 16611328 6505736 8221432 45% /
    # time echo "This is a test to test the test" >> /testfile
    real     0m0.000s
    user     0m0.000s
    sys     0m0.000s
    # df -k /
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/sda3 16611328 6505780 8221428 45% /
    # btrfs subvol delete /snap1
    Delete subvolume '//snap1'
    # df -k /
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/sda3 16611328 6505740 8221428 45% /
    The snapshot occupied 40k
    # btrfs subvol snapshot / /snap1
    Create a snapshot of '/' in '//snap1'
    # time dd if=/dev/zero of=/testfile bs=8k count=500k
    512000+0 records in
    512000+0 records out
    4194304000 bytes (4.2 GB) copied, 21.3818 s, 196 MB/s
    real     0m21.754s
    user     0m0.019s
    sys     0m3.322s
    # df -k /
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/sda3 16611328 10612756 4125428 73% /
    There was no performance impact, although the space occupied doubled.
    </pre>

  • Trying to understand how pics are stored

    I'm new to Mac (iMac Core i5 27") and trying to understand how pictures are stored. I've searched and found some posts that are relevant, but I really wanted to try and confirm a couple of things that still aren't clear to me.
    First question is: Are the pictures in Events, Photos and Albums all the same photos?
    Second question: If I import pictures from my external drive into iPhoto, are they stored on the iMac hard drive in the Pictures folder, and just viewed in iPhoto?
    Thanks!

    First question is: Are the pictures in Events, Photos and Albums all the same photos?
    Yes. Iphoto works on a Library bsis. Every photo is in the Library. Events and Photos are both views of the Library. Albums reference photos in the Library. A photo can be in many Albums and use no extra disk space.
    If I import pictures from my external drive into iPhoto, are they stored on the iMac hard drive in the Pictures folder, and just viewed in iPhoto?
    Yes, by default. There are other options - for instance, iPhoto integrates with almost every app on your Mac, you can store the Library on an external etc etc. If you tell us what you'd like to achieve we may be able to help you.
    Regards
    TD

  • Mac newbie trying to understand

    I haven't learned to think in Mac yet. I'm trying to understand what actually happens to the files that I have imported from my memory card into iphoto and then exported to another folder on my hard drive for use in other applications or on a Windows PC. Are the files moved from the iphoto library and then tracked in iphoto or are they copied to the new folder thus creating two copies on the hard drive? Any of the above?
    I am trying to avoid creating duplicates of the originals in order to save space and would like to understand this before I go much further and wind up with a huge mess. I'm thinking maybe I should use image capture to get the photos from the card to a folder and then import into iphoto so the originals would be more readily available for burning cds/dvds for use use in Windows as I will be doing that a lot. How would that work?
    That's probably about as clear as mud. Anybody understand and can educate me? By the way, love my iMac.
    Thanks.

    Lonr
    Welcome to the Apple user to user assistance forums
    And welcome to the Mac
    while you will find the Mac very intuitive and easy to use it is different from a PC and there is a learning curve - the Apple tutorials are very helpful - see the right hand column for a list by major topic - http://www.apple.com/startpage/
    I'm trying to understand what actually happens to the files that I have imported from my memory card into iphoto and then exported to another folder on my hard drive for use in other applications or on a Windows PC. Are the files moved from the iphoto library
    By default (and strongly recommended) the imported photos are copied to the iPhoto library -- there is an option not to do this but it can be extremely problematic and unless you are a very experienced user it is strongly recommended that you use the default of copying all imported photos to the iPhoto library
    and then tracked in iphoto
    Yes - by default
    or are they copied to the new folder thus creating two copies on the hard drive?
    The original is left alone unless you choose to have iPhoto delete the photos form the camera after importing (it is best not to have iPhoto do this but to use the camera to reformat the card once everything is firmly in iPhoto and the camera is properly disconnected. Once you have imported the photos to iPhoto you can delete the original that is outside of iPhoto
    I am trying to avoid creating duplicates of the originals in order to save space and would like to understand this before I go much further and wind up with a huge mess. I'm thinking maybe I should use image capture to get the photos from the card to a folder and then import into iphoto so the originals would be more readily available for burning cds/dvds for use use in Windows as I will be doing that a lot. How would that work?
    This will create two copies of each original and is unnecessary - it is better to export the photos you want to use and delete the exported versions after you use them.
    LN

  • Understanding iPhoto 08 Architecture

    Recently I moved all my picture files and folders (.jpg, .bmp, .avi, etc) off my windows computer to a new external HDD that was single partitioned with MAC OSX (Journaled).
    I then created a new iPhoto Library on that external HDD and dragged my photos from each folder into iPhoto. I went into the "Advanced" tab under Preferences and made sure to uncheck the box that would have copied the files, as I want to conserve disk space as much as possible ( I thought this option, if I had left it checked, would have created a duplicate file of the same image and put it in the iPhoto Library...am I right?).
    I also thought that by unchecking this option I would be creating a "pointer" in iPhoto between where the file actually was and where I saw it in iPhoto. I thought if I wanted to delete the actual picture file I would have to open Finder and manually delete that file. I thought if I did that first before deleting it in iPhoto 08 I would get some sort of an error msg. in iPhoto, since the pointer wouldn't be able to find the picture file because I had removed it. Vise-Versa, if I removed the picture in iPhoto 08 first I thought I would also have to go into Finder and manually remove the picture if I didn't want it.
    While the later seems to be true, in that I do have to manually remove the file using Finder after I've removed it in iPhoto the former doesn't. If I deleted the file first using Finder and then go into iPhoto the picture is still there. I'm left scratching my head....
    So my question is.....drum roll please....
    What is actually being stored in iPhoto when you import pictures? Is it an actual image file? If so where are those actual image files being stored and are they accessible? It seems that while everywhere I read it says that the iPhoto Library is a "folder" I can't seem to access what's inside of that folder from Finder. I'm obviously missing the thought process behind iPhoto, however I'd like to understand iPhoto's architecture a little better.
    Also, if iPhoto is actually storing an image file somewhere within the iPhoto Library folder, thereby making a duplicate of the file I have in my own file structure what's the point of the setting in the "Advance" tab under Preferences that says "Copy Items into the iPhoto Library"?
    Maybe my head is still too stuck in the Windows world. Can I deleted all the files, after I've imported them to iPhoto, I have in the file structure I created when I originally moved these pictures to this external HDD?
    Thanks for any clarification someone can offer.

    scottstephens84
    You have a REFERENCED library, and in this scenario, iPhoto does not copy the File from your filing structure, but creates an Alias to it in the /Originals folder inside the iPhoto Package File. Then - as is the case with a MANAGED library as well, it also create a thumbnail and - if you edit the pic - a Modified version.
    The thumbnail is what you see in the Organise parts of iPhoto (unless you scale to full-size.)
    The correct way to trash pics is: In the iPhoto Window put them in the iPhoto trash and empty it. This removes the Alias, the thumbnail and modified version. Then remove the file from your own filing structure.
    However, you need to be aware of a number of potential pitfalls using a REFERENCED library.
    1. Import and deleting pics are more complex procedures
    2. You cannot move or rename the files on your system or iPhoto will lose track of them
    3. Most importantly, migrating to a new disk or computer can be much more complex.
    Always allowing for personal preference, I've yet to see a good reason to run iPhoto in referenced mode unless you're using two photo organisers.
    If disk space is an issue, you can run an entire iPhoto Library from an external disk:
    1. Quit iPhoto
    2. Copy the iPhoto Library as an entity from your Pictures Folder to the External Disk.
    3. Hold down the option (or alt) key while launching iPhoto. From the resulting menu select 'Choose Library' and navigate to the new location. From that point on this will be the default location of your library.
    4. Test the library and when you're sure all is well, trash the one on your internal HD to free up space.
    If you're concerned about finding the files, There are many, many ways to access your files in iPhoto:
    For 10.5 users: You can use any Open / Attach / Browse dialogue. On the left there's a Media heading, your pics can be accessed there. Apple-Click for selecting multiple pics.
    To upload to a site that does not have an iPhoto Export Plug-in the recommended way is to Select the Pic in the iPhoto Window and go File -> Export and export the pic to the desktop, then upload from there. After the upload you can trash the pic on the desktop. It's only a copy and your original is safe in iPhoto.
    This is also true for emailing with Web-based services. If you're using Gmail you can use THIS
    If you use Apple's Mail, Entourage, AOL or Eudora you can email from within iPhoto.
    If you use a Cocoa-based Browser such as Safari, you can drag the pics from the iPhoto Window to the Attach window in the browser.
    Or, if you want to access the files with iPhoto not running, then create a Media Browser using Automator (takes about 10 seconds) or use THIS
    Other options include:
    1. *Drag and Drop*: Drag a photo from the iPhoto Window to the desktop, there iPhoto will make a full-sized copy of the pic.
    2. *File -> Export*: Select the files in the iPhoto Window and go File -> Export. The dialogue will give you various options, including altering the format, naming the files and changing the size. Again, producing a copy.
    3. *Show File*: Right- (or Control-) Click on a pic and in the resulting dialogue choose 'Show File'. A Finder window will pop open with the file already selected.
    Regards
    TD

  • I am trying to update 'iPhoto' and am getting this....To update this application, sign in to the account you used to purchase it.

    I am trying to update 'iPhoto' and am getting this....To update this application, sign in to the account you used to purchase it.

    Dear Brother David,
    You are way out of order and actually just wrong and seem to lack any empathy or understanding for users, let alone anything other than text book/google regurgitations.
    I thank you for highlighting your illusions of granduer  and for your wonderful, thoughful and intelligent insults.
    I re- post a fix below that worked for me:
    As a user and you may find this bug, you can either ring apple or try the below,
    All my apps now appear in the purchases section of App store and iMovie also updated itself.
    I have only one ID software is presinstalled and software was "not hidden" or even showing...I just got various error messages and ID errors.
    It was not spotlight indexing either.
    cheers
    "sls6
    Re: App Store: says You cannot update this software since you have not owned the major version of this software - when it came with the computer!! 
    Mar 19, 2013 10:04 AM (in response to amala.amilo)
    I had a similiar problem that I fixed doing this:
    Close Mac App Store
    Go into this folder
    /Library/Application Support/App Store
    Drag this file to the desktop
    adoption.plist
    Repen Mac App Store and log in
    If it fixes your problem, great, if not, you can move the old adoption.plist file back"
    from:
    https://discussions.apple.com/thread/4728740?start=0&tstart=0

  • Hello, World - trying to understand the steps

    Hello, Experts!
    I am pretty new to Flash Development, so I am trying to understand how to implement the following steps using Flash environment
    http://pdfdevjunkie.host.adobe.com/00_helloWorld.shtml         
    Step 1: Create the top level object. Use a "Module" rather than an "Application" and implement the "acrobat.collection.INavigator" interface. The INavigator interface enables the initial hand shake with the Acrobat ActionScript API. Its only member is the set host function, which your application implements. During the initialize cycle, the Acrobat ActionScript API invokes your set host function. Your set host function then initializes itself, can add event listeners, and performs other setup tasks.Your code might look something like this.
    <mx:Module xmlns:mx="http://www.adobe.com/2006/mxml" implements="acrobat.collection.INavigator" height="100%" width="100%" horizontalScrollPolicy="off" verticalScrollPolicy="off" >
    Step 2: Create your user interface elements. In this example, I'm using a "DataGrid" which is overkill for a simple list but I'm going to expand on this example in the future. Also notice that I'm using "fileName" in the dataField. The "fileName" is a property of an item in the PDF Portfolio "items" collection. Later when we set the dataProvider of the DataGrid, the grid will fill with the fileNames of the files in the Portfolio.
    <mx:DataGrid id="itemList" initialize="onInitialize()" width="350" rowCount="12"> <mx:columns> <mx:DataGridColumn dataField="fileName" headerText="Name"/> </mx:columns> </mx:DataGrid>
    Step 3: Respond to the "initialize" event during the creation of your interface components. This is important because there is no coordination of the Flash Player's initialization of your UI components and the set host(), so these two important milestone events in your Navigator's startup phase could occur in either order. The gist of a good way to handler this race condition is to have both your INavigator.set host() implementation and your initialize() or creationComplete() handler both funnel into a common function that starts interacting with the collection only after you have a non-null host and an initialized UI. You'll see in the code samples below and in step 4, both events funnel into the "startEverything()" function. I'll duscuss that function in the 5th step.
                   private function onInitialize():void { _listInitialized = true; startEverything(); }

    Hello, Experts!
    I am pretty new to Flash Development, so I am trying to understand how to implement the following steps using Flash environment
    http://pdfdevjunkie.host.adobe.com/00_helloWorld.shtml         
    Step 1: Create the top level object. Use a "Module" rather than an "Application" and implement the "acrobat.collection.INavigator" interface. The INavigator interface enables the initial hand shake with the Acrobat ActionScript API. Its only member is the set host function, which your application implements. During the initialize cycle, the Acrobat ActionScript API invokes your set host function. Your set host function then initializes itself, can add event listeners, and performs other setup tasks.Your code might look something like this.
    <mx:Module xmlns:mx="http://www.adobe.com/2006/mxml" implements="acrobat.collection.INavigator" height="100%" width="100%" horizontalScrollPolicy="off" verticalScrollPolicy="off" >
    Step 2: Create your user interface elements. In this example, I'm using a "DataGrid" which is overkill for a simple list but I'm going to expand on this example in the future. Also notice that I'm using "fileName" in the dataField. The "fileName" is a property of an item in the PDF Portfolio "items" collection. Later when we set the dataProvider of the DataGrid, the grid will fill with the fileNames of the files in the Portfolio.
    <mx:DataGrid id="itemList" initialize="onInitialize()" width="350" rowCount="12"> <mx:columns> <mx:DataGridColumn dataField="fileName" headerText="Name"/> </mx:columns> </mx:DataGrid>
    Step 3: Respond to the "initialize" event during the creation of your interface components. This is important because there is no coordination of the Flash Player's initialization of your UI components and the set host(), so these two important milestone events in your Navigator's startup phase could occur in either order. The gist of a good way to handler this race condition is to have both your INavigator.set host() implementation and your initialize() or creationComplete() handler both funnel into a common function that starts interacting with the collection only after you have a non-null host and an initialized UI. You'll see in the code samples below and in step 4, both events funnel into the "startEverything()" function. I'll duscuss that function in the 5th step.
                   private function onInitialize():void { _listInitialized = true; startEverything(); }

  • Trying to understand Android OS updates delays

    This is not another hate mail, it´s more about trying to understand the facts and motives regarding the OS updates (or lack of).
    Hopefully this material will arrive at someone from Sony with enough power to do something about it.
    Ever since I can remember, Sony has been THE brand for electronics. I can´t remember a TV or VCR in my house that it wasn´t Sony, and they lasted for LOTS of years.
    When a couple years ago I finally had the money (and the need) for a Smartphone, i chose the X10 Mini, which is a great little phone from a great brand, but it´s stuck at Android 2.1... which makes it a crippled android nowadays...
    It really bothered me the lack of OS updates, so I chose to buy a Galaxy Nexus, but it´s really expensive in my country. So my second option was a Galaxy Ace 2, but they haven´t arrived to my country yet, so I went with my third option: Xperia Sola, knowing beforehand that it´s a great phone, a great brand, but I might get slow OS updates.
    I bought it about 10 days ago when I saw they were starting to roll out the updates.
    10 days later I still don´t have my update. And not only that, but I don´t see much light at the end of the tunnel...
    I found a thread with the SI numbers that were updated, and there were a bunch on Oct 1, another bunch on Oct 4, and one code on Oct 8, and no other update since...
    I also read that those who did get the update, were having bugs with the OS, and also found threads from other Xperia models, whose updates began rolling 3 months ago, and there is still people who hasn´t gotten the update...
    As a customer, and a owner/CEO of a small company, I have a really hard time understanding how a HUGE company like Sony can be making such mistakes...
    I have been thinking objective reasons, and I can only think of one. I know it´s a wild guess, but I´m starting to think that our salvation might be the very thing that means our condemnation: CYANOGENMOD!!!
    Think about it: Why would Sony spend more money hiring twice as much programmers, when they can make only one update per phone, and sit down and see how CM releases begin to appear, for all tastes and needs. And... IT´s FREE!!!
    Also, if there is a software related problem (way more likely than a hardware problem), then the CM developers take the fall, instead of Sony. And I´m beginning to see custom OS installers that are more user friendly, so it might be something that they take in accout when neglecting OS updates.
    If that´s the line Sony is following, it´s a very risky move and it won´t work. Sony Mobile will crash and burn, but it´s still a better business plan that "let´s get lazy and make ULTRA slow updates so we don´t spend a lot of money programming".
    If you can´t afford more programmers, stop including so much bells and whistles and make your OS near vanilla. Include a couple of Xperia menus, a custom theme and voila!
    The main reason I wanted the Galaxy Nexus is Vanilla OS, which means inmediate OS updates. Sony on the other hand, takes a year or two to release it after its launch. If they release it at all...
    Another though...  why not stop making that many different phones! Really! There are like 5 Xperia models i can´t tell one from the other... even with specs side by side!
    You are trying to make too many phones and you are failing with all of them! (Software and software updates are also part of the phone, one of the most importants...)
    I know hiring programmers is expensive, but you are sacrificing one of the most expensive values for a company EVER: Customer credibility! Which as you know better than me, takes years to create.
    If Apple had problems with carriers and code aprooving and stuff, they might get away with it, becouse they alone have all the devices. If iOS 6 is delayed a few months, it´s delayed for everyone, and besides Apple fanboys rarely complain about Mac products, but Android is a more independent and educated market.
    I´m not saying that Apple users are ignorant, not at all, but I´m pretty sure most iPhone owners don´t even know what processor or how much RAM their phone has. They just "swallow" the Apple Way of Life. (it´s a good phone becouse Apple says so).
    The Android user on the other side, because of the fragmentation of the market, has many brands and models to choose from. An Android user about to buy a new phone will most likely go online looking for different models, specs, reviews in webs and forums...etc.
    You can´t say "I don´t know how HTC and other companies get their updates so soon, but we take a lot more becouse Google and the Operators must aproove the code.", because there are many other brands that have exactly the same difficulties or more, since they are smaller, and we can SEE online that they are indeed delivering solid and relativly fast updates.
    Did we miss something? Does HTC use Witchcraft to get their code aprooved?
    My underlying point is this: You are getting lazy... VERY lazy with software programming for your phones, and WE KNOW IT!
    It´s not the "difficulties" you claim, becouse every brand has those difficulties.
    This isn´t 1999 you know. We are in the information age. If you lie to us and tell us that your phones have the latest OS, I can go online and see that you don´t (Hello!!!). If I see that the company lies to it´s customers, I will stop buying their products. If I´m so dissapointed with how Sony handles OS updates and their customers queries about it, then I want for the first time ever to sell my Cell Phone becouse I´m not happy with it, or the brand behind it.
    We also live in the "Here and now" age. You can´t expect your customers to read about new Android releases on news and blogs, and wait YEARS with arms crossed waiting for their update... The world doesn´t work like that. Not anymore at least...
    It´s not a matter of how many recources you have, it´s about how you use and balance them. GIVE MORE IMPORTANCE TO SOFTWARE UPDATES! IT´S WAY MORE IMPORTANT THAT YOU THINK! LISTEN TO YOUR CUSTOMERS!!!
    You guys are Sony are smart and design great products, but you are not GOD! You are not our wife, no one has sworn alliagence to you.
    If you stop giving us good products and start lying to us, we hate you and stop giving you our money. Simple as that.
    My sola is beatiful, I love the design, the screen, the hardware... but it hasn´t been updated yet to 4.0, not to mention 4.1, which REALLY is the latest version... so stop advertising that your phones have the latest Android OS, unless you want angry customers switching to other companies, which you are getting.
    I also read some stories that Androind 4.0 was announced for the Xperia PLAY, and then it was called off... Do you have any idea how pissed I would be and ripped off I would be if I bought my phone based in that information and then you say it won´t be available?
    Well, actually right now my possition is worse, since you SAY you will update my phone, but you don´t say when, and I read online about people still not getting their updates months after the rollout started, so I´m in the limbo right now...
    As a company, one of the worse things you can do is calling your customers stupid, and when I see the answers you give in this forum, then I feel insulted. I feel like they are talking to an idiot or ignorant person with the so called "diplomatic" answers, which are basicly empty excuses for not doing your job right.
    You gave us the frikking CDs, DVDs and Blu-Rays!!! Don´t tell us you can´t tweak an already built OS in a year!
    I really hope you change their OS update policies really soon, before you lose the already small cellphone market share you have, or at least change your P.R. and C.M. policies towards a more open one.
    We all are humans and make mistakes, but we customers really appreciate honesty and truth.
    Have an open conversation with your customers! Don´t lie about your shortcomings! Accept then and ask the community to help you solve them, ask them what they biggest problems are, what features are most important to them, how often do they expect updates... LISTEN TO THEM!!
    "Succes is a meneace. It tricks smart people into thinking they can´t lose."
    Ps: Nothing personal with the mods from this forum, I´m not killing the messenger, I know that you can ONLY give the info you are allowed to give, and even if you wanted, you probably don´t know the answers yourself, since you work in the Communications department, not Developement or anything technical, and if you can't give any given info, then they probably won´t give it to you either... My message is to the company as a whole. I just hope you will be a good messenger and give this to whoever needs to read it.

    My bad, it´s closer to 40 the number of phones released hehe
    I know it´s all about money, and I know Sony is obligated to neglect users who haven´t given them money after an x ammount of time. However, it´s not a matter of making the phones obsolete earlier, so the users want to buy a new phone faster and therefore getting more money.
    A person will buy a new phone when he/she has the money to do so and wants to do so.
    It´s not a matter of WHEN. It´s a matter of WHAT.
    The question is not "When will that user buy a new phone?", but rather "When that user buys a new phone, whenever that is, what phone will it be?"
    I have a love/hate relationship with Apple. I would never use a iPhone. I would love having any Mac, if someone gives it to me, but I would never spend my harn earned dollars on such an overpriced piece of hardware over general principals.
    However, i do recognice that Steve Jobs was a business genius. Weather you like or love his ideas and methods, he turned a garage project into the biggest company in the world, with a market value higher than Exxon with 1/3 of it´s assets.
    Apple is a money making machine, and that is where the "hate" part of my relationship comes from.
    However, it surprised me a lot to see that they released iOS 6 for the iPhone 3GS, released in 2008!
    That get´s you thinking, that inside all that "SELL NOW" culture Apple is, they also support their older devices that people bought years ago but can't buy a new phone now. However, when they can do it, it will surely be another iPhone. Because they FEEL that the company listens and cares for them.
    Also if you jump from iOS 6 on the 3 GS to a brand new iPhone 5, the transition will be virtually non-existant, except for Siri and a couple of features.
    However jumping from Android 1.5 or 2.1 to Jelly Bean, might not be so easy on some users, making them more likely to give iPhone a shot.
    Since they have to adapt to another phone anyway, they might as well try the apple...
    And for old users, it gives people a sense of continuity and care about the user. Otherwise we feel like being kicked out of a restaurant right after we payed the bill.

  • I am trying to upgrade iPhoto from a .dmg file ???

    I am trying to upgrade iPhoto 9.4.2 to 9.4.3 on a Mac Mini with Mountain Lion.  When I run the iPhoto9.4.3Update.dmg file, I get the alert:
    The version of iPhoto installed on this Mac must be updated through the Mac App Store.  Check the Mac App Store to see if an update is available.
    When I close the alert, it shuts down the update. 
    Since at our location our only option to get on the internet is via a 3G modem with a data cap of 5 GB per month, we take a laptop into the local library, hop on their wifi, and download dmg files for large upgrades like iPhoto (in this case, 766 MB).  This has always worked before - what is different here?
    Since we were near the end of our data month and still had a GB left, I then tried the software update route from the Apple menu on the Mac mini.  It started downloading the 9.4.3 update which was only 177 MB.  2 hours later it had just finished the download and suddenly continued onto another download (still in the iPhoto upgrade) of a 1.2 GB file.  So I aborted.  So my 2nd question is what was happening here.
    And my 3rd question is what to do next?

    Evidently there was more than one update listed for your Mini.  Next time launch the App Store app in your Applications folder and log in with the Apple ID used to purchase your Mini. Click on the Updates folder and look for available updates.  There you can select one at a time for installation.
    Look in the Download folder in your Home folder to see if the 9.4.3 update is there.
    OT

  • I am trying to access iPhoto from my MacBook Pro on my iPhone 5s

    I am trying to access iPhoto on my iPhone 5s from my 2008 MacBook pro. I have synced both devices, have set up iCloud, have downloaded iOS7 and Mavericks, and have photo sharing and photo stream turned on on the iPhone. I am using iPhoto '08, version 7.1.5. There is a newer for purchase version of iPhoto. Could it be that I have to buy this update to connect from my iPhone? I just bought the iPhoto by Apple app but it only allows me to view albums and photos that are already on my iPhone.

    Thanks for your reply. I am still ever-hopeful this can be done. Checking the iPhoto '11 site, I see this info:
    -View and automatically import recent photos taken on your iOS devices
    -Automatically send newly-imported photos to all your iOS devices
    -iPhoto '11 works with iCloud Photos, so the photos you take on your iOS devices automatically appear in iPhoto,
    I ask this respectfully. If indeed iPhoto version 9.5 is iCloud friendly, why would it not be accessible from my iPhone? It seems to me that the mission of iCloud is to effect the "commonality" between iPhone and the Mac - and other Apple devices. Do you know the technical reason for this or am I going to have to accept that it simply won't work? <grin>

Maybe you are looking for