Bindings, Outlets, Target+Action across multiple NIBs

I’m a total troublemaker. For my first Core Data app I decided to do something nontrivial (multiple windows referring to a single document). Of course nontrivial means that the Interface Builder can only help me so far. So now I’m stuck trying to get things to work out right. Luckily Patrick Geiller has put together a good explanation of how you can share multiple nibs across an application. Now all I have to do is apply this same data sharing technique to the NSDocument instead.

When using multiple NIBs, we need a common object that will share data among them. That object will hold bindings, outlets, target/action shared across NIBs.

[From Bindings, Outlets, Target+Action across multiple NIBs ]

Creating a Git project for XCode/Cocoa apps

You can always count on somebody to have figured things out before you.. Chrisopher Roach’s blog has a nice quick setup guide to get your xcode project in a git repo (gitignores, attributes and basic git push capability).

Whenever I setup a new Xcode project, the first thing I do is initialize it as a Git repository and add some configuration to the project that will make using Git with Xcode a bit less messy.

[From christopherroach.com ]

And of course debate has already started on the merits of treating certain things as binary to avoid merging nightmares. <sarcasm>Don’t you love XML syntaxes?</sarcasm>

Ruby, Folder actions and full automation

I routinely scan my documents as PDFs so I can keep them in a virtual filing cabinet (you know, the whole “paperless office” thing). I use my HP all-in-one software running on a Windows VM inside a Mac (sorry, but the Mac scanning software on HP is complete garbage in my opinion).

What bothered me about this was that all the files scanned always end up named “scan12345.pdf”. Because of the way I file, I like having my things as “year/company/year-monty-date.pdf” instead.

Continue reading “Ruby, Folder actions and full automation”