2718.us blog » whocalled.us http://2718.us/blog Miscellaneous Technological Geekery Tue, 18 May 2010 02:42:55 +0000 en hourly 1 http://wordpress.org/?v=3.0.4 NCIDStatusBarMenu v0.1a Release Notes http://2718.us/blog/2007/10/14/ncidstatusbarmenu-v01a-release-notes/ http://2718.us/blog/2007/10/14/ncidstatusbarmenu-v01a-release-notes/#comments Mon, 15 Oct 2007 03:07:40 +0000 2718.us http://2718.us/blog/?p=49 Initial Release Notes for the first release of NCIDStatusBarMenu (copied into the blog)

  • This is the first thing I’ve ever written with Objective-C/Cocoa and the first OS X-native GUI app I’ve ever written. This is also the first release. There are probably bugs.
  • The preferences have no default settings yet.
  • The program won’t create the log file if it doesn’t exist.
  • If you don’t have Growl, you will be prompted to install it at some point. Install it.
  • The lookups to whocalled.us may make use of /usr/bin/curl, but I think that’s in the base install of OS X 10.4+
  • Requires OS X 10.4+
]]>
http://2718.us/blog/2007/10/14/ncidstatusbarmenu-v01a-release-notes/feed/ 0
Why NCIDStatusBarMenu? http://2718.us/blog/2007/10/14/why-ncidstatusbarmenu/ http://2718.us/blog/2007/10/14/why-ncidstatusbarmenu/#comments Sun, 14 Oct 2007 18:58:53 +0000 2718.us http://2718.us/blog/?p=51 I got tired of hunting for one of my cordless phones to check the caller ID every time someone was calling and figured that since I’m sitting at a computer 90% of the time, there had to be a way to get the caller ID on there. The big problems for me were that my primary machine no longer has a modem and that my primary machine isn’t the only one I use. I tried some of the existing OS X programs and some of them looked good, but none quite did what I wanted.

When I learned about Network Caller ID (NCID), I knew it was exactly what I wanted. I’ve got an old, but caller-ID capable, modem in an old OpenBSD box and it grabs all the caller ID data and serves it up. The only thing left is to get that data to each machine.

I was very disappointed in the choices in NCID clients for OS X. I settled on using David LaPorte’s shell scripts that hook into the command-line tool for Growl notification. This worked pretty well. Annoyingly for me, I get calls about every half-hour during the day, six days a week, mostly from “Toll-Free” or “Out-of-Area” and my annoyance with not knowing who’s calling had led me to whocalled.us. I was able to use Maxim Samo’s junk_lookup.agi script to help me modify David LaPorte’s scripts so that now all my incoming calls were looked up on whocalled.us. This worked reasonably well.

I now had an AppleScript app on my desktop that ran the shellscript that started the command-line NCID client that triggered a shell script that used curl and some other voodoo to query whocalled.us and reprocess all that info into a log and into the command-line interface for Growl. If I were busy all the time, I wouldn’t have given this a second thought, since it worked. But what I really wanted was a single program with a nice little menu thing up by the clock that controlled it. So I learned some Objective-C and some Cocoa and here’s the result.

]]>
http://2718.us/blog/2007/10/14/why-ncidstatusbarmenu/feed/ 0