I used to have a JIRA to Omnifocus Script which fell into disrepair for a bit.
It worked well, but as the Mac modernized itself it ended up with a lot of issues.
So I rewrote it by splitting it into a front-end (JIRA) and back-ends (the different task managers) for Yosemite and El Capitan. Now it’s called JIRA To Task Managers.
The one I use and support is JIRA and Things, which is the task manager I’ve been using lately.
Take a look and have fun!
My experiences with the iPad so far
Yesterday I went ahead and picked up an iPad. A lot of people are wondering if it makes sense as a device. Here are my impressions.
Continue reading “iPad – first impressions”
Have you ever seen a stream of data coming from a network, and it has some European accented characters in an encoding you don’t recognize? Sometimes bad coding practices or assumptions about encoding when pasting into documents make the encoding on the file not match all or part of the encoding of a document. This is a quick way to find out what encoding(s) match.
It’s not fully automated, it still requires your eyes. But it can make a difference when you’re writing parsing code and you don’t know what to do with some edge cases. Maybe some code like this coupled with a spell checker inside the loop would give you some sense of automation.
Continue reading “Figure out the encoding of a stream”
Yesterday a coworker pointed me to ruby’s appscript. I have found it nothing short of amazing.
I love my Mac, and many of us like the idea of automating our software, until we try to use AppleScript to do it. To say that Applescript is professional developer unfriendly is an understatement. I like ruby but to make ruby and applescript talk requires sending strings to osascript in just the right way and getting the output from osascript back. Not a lot of fun at all.
Enter appscript. Appscript is a ruby library that interfaces with applescript seamlessly.
Continue reading “Ruby Appscript – Sweet automation”
If you’re a developer and use Terminal.app, don’t set “unlimited” on the buffer size. After a day of using it heavily to review logs and whatnot your computer will be *really* slow. It’s Terminal.app keeping in RAM what you did yesterday. Stupid and Obvious, but still figured I’d write it down.
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 ]