3 ms·
> My first encounter of this was the stupid filesystem abstraction iPhoto decided to enforce upon me. After removing iPhoto, it was bearable. This makes no sen
by revscat 14y ago
> My first encounter of this was the stupid filesystem abstraction iPhoto decided to enforce upon me. After removing iPhoto, it was bearable.
This makes no sense. iPhoto stores your photos in a directory structure on your system. This directory is like any other. If you want to extract the photos from them you can. You can also just right-click on your photos from within iPhoto and extract them.
> After removing iPhoto, it was bearable.
What was bearable? Why didn't you try and fix the problem? I've been using iPhoto for almost 10 years, across ~6 different machines, and have never had any issues with it.
- calinet6 14y agoIt's sometimes not intuitive that some directories on Mac look like packages. Sometimes you just need to right-click View Package Contents to access the directory, and I'm sure that tiny fence solves many many support headaches for 99% of users.
- meaty 14y agoIt was unbearable because the abstraction was inconsistent when it came to: a) talking to the library from the command line - the mapping between the UI and the filesystem was completely abstract. b) talking to the library from apps - the UI was horrible and inconsistent. c) metadata was entirely non transparent and hard to get at. Bearable was removing iPhoto and installing Nikon ViewNX which came with my D70. This has no abstraction - the filesystem is the abstraction. (I know how to access the source files BTW).
- revscat 14y ago> a) talking to the library from the command line - the mapping between the UI and the filesystem was completely abstract. So... doing "find . -type f -name '*.jpg' -print" is outside of your capabilities? > b) talking to the library from apps - the UI was horrible and inconsistent. What were you trying to do? > c) metadata was entirely non transparent and hard to get at. man mdls
- meaty 14y agoSo... doing "find . -type f -name '.jpg' -print" is outside of your capabilities?* No but doing that when iPhoto stores backups of your images is a pain in the arse. b) talking to the library from apps - the UI was horrible and inconsistent Automator + Photoshop. > c) metadata was entirely non transparent and hard to get at. Yes but that doesn't deal with folders which aren't indexed. For example if you do an iPhoto import it can lag for a while before Spotlight catches up. Bang - synchronisation problem. This shot me badly. The whole solution is just bad.
- revscat 14y ago> No but doing that when iPhoto stores backups of your images is a pain in the arse. In what way? > Yes but that doesn't deal with folders which aren't indexed. For example if you do an iPhoto import it can lag for a while before Spotlight catches up. Bang - synchronisation problem. Moving goalposts. First you said the metadata was opaque. It wasn't. Now you're saying there is lag. What were you trying to do? I do a lot of photography, and while I am no means a pro -- or even a semi-pro -- I have done automator scripts against iPhoto with zero problems. You still haven't said what you were trying to accomplish.