2718.us blog » NCIDStatusBarMenu 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 Open Source (BSD/MIT License) http://2718.us/blog/2009/09/06/open-source-bsd-license/ http://2718.us/blog/2009/09/06/open-source-bsd-license/#comments Sun, 06 Sep 2009 10:24:58 +0000 2718.us http://2718.us/blog/?p=170 I’ve released a few things as open source recently, under BSD or MIT license, hosted at Google Code.

  • asLJCore is the primary component of the LiveJournal client asLJ, managing all communication with the server.
  • YDDecode is a Cocoa class wrapped around some public-domain C code for decoding data encoded with YEnc.
  • NCIDStatusBarMenu is a utility to help pull NCID-based callerID notifications and display them as Growl notifications (among other things).  I’d been meaning to update it for nearly 2 years with no success and the future isn’t looking much better, so I’m releasing the source instead.

(My musings on licensing below the cut.)Permissive BSD/MIT licenses because in writing asLJ among other things, I’ve had to work to find libraries, frameworks, components, classes, etc., that weren’t GPL-licensed so that I could continue to choose how I wanted to release my software.  I am also heavily influenced by the simplicity of the BSD and MIT licenses compared to the lengthy GPL (and while the LGPL ought to be workable for many libraries, I couldn’t quite wrap my head around the language of it–the LGPL is several paragraphs of modification to the GPL).

(The song lyrics and commentary for OpenBSD4.3 have a lot to do with how I feel about GPL versus BSD/MIT.)

]]>
http://2718.us/blog/2009/09/06/open-source-bsd-license/feed/ 0
NCIDStatusBarMenu Bug http://2718.us/blog/2007/10/21/ncidstatusbarmenu-bug/ http://2718.us/blog/2007/10/21/ncidstatusbarmenu-bug/#comments Sun, 21 Oct 2007 18:53:00 +0000 2718.us http://2718.us/blog/?p=50 There seems to be some sort of bug in v0.1a where caller ID info isn’t logged and probably isn’t even acted upon when the screensaver is active or perhaps when the screen has gone into powersave (I’m not sure since it seems that the misses only happen when I’m not home…). I hope to have a fixed and improved v0.2a soon. Rebooting my (rarely rebooted) Mac Pro seems to have solved the problem. As an aside, the program doesn’t seem to work after the machine has been put to sleep and woken up. I’ll look into this soon.

]]>
http://2718.us/blog/2007/10/21/ncidstatusbarmenu-bug/feed/ 0
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