Thursday, May 21, 2015

jQuery event namespacing


var obj = $({});

function log(evt, obj, src) {
    $('#log').append(obj + ':' + evt.type + '.' + evt.namespace + ' ' + src + '\n');

obj.on('save.billing', function (evt, obj) {
    log(evt, obj, 'save base');

obj.on('save.billing.widget', function (evt, obj) {
    log(evt, obj, 'save widget');

obj.on('save.billing.consumer', function (evt, obj) {
    log(evt, obj, 'save consumer');

//triggers base, widget, and consumer
obj.trigger('save.billing', 1);
//remove widget listeners'.billing.widget');
//triggers base and consumer
obj.trigger('save.billing', 2);
//remove all billing listeners'.billing');
//triggers nobody
obj.trigger('save.billing', 3);

Monday, April 20, 2015

Grunt-JSDoc prevent output of source code

By default JSDoc will include your source code in the resulting documentation.  To prevent this from happening when using grunt-jsdoc you'll have to create an external configuration file:

build: {
    options: {
        destination: '<%= path %>/doc',
        configure: 'conf.json'

  "source": {
    "include": "app/js/ascendon.service.js"
  "templates": {
    "default": {
      "outputSourceFiles": false

Tuesday, April 7, 2015

Browserify and Grunt using jQuery from a CDN

Below is a sample configuration in which jQuery, backbone, and underscore are all referenced externally so that they are not included in the browserify bundle. Notice also that there is a transform for underscore templates in the grunt config. The resulting bundle is built as a standalone so that the module can be instantiated by our clients.  You'll need to npm install browserify-shim and modify your package.json file.  After building this module your html page will also need to reference jQuery because the jQuery code will not be in the bundle.

  "name": "packageName",
  "version": "15.3.1",
  "devDependencies": {
    "browserify": "9.0.7",
    "browserify-shim": "3.8.3",
    "grunt": "0.4.5",
    "grunt-browserify": "3.6.0",
  "browser": {
    "jquery": "./app/js/lib/jquery-1.11.2.min.js",
    "backbone": "./app/js/lib/backbone-1.1.2.min.js",
    "underscore": "./app/js/lib/underscore-1.8.3.min.js"
  "browserify": {
    "transform": [ "browserify-shim" ]
  "browserify-shim": {
    "jquery": "global:$",
    "underscore": "global:_",
    "backbone": "global:Backbone"

gruntfile browserify options
    js: {
        src: ['app/js/main.js'],
        dest: 'app/js/company.modulename.js'
    options: {
        transform: ['node-underscorify'],
        browserifyOptions: {
            standalone: 'company.modulename'

Tuesday, March 19, 2013

Code: C# when not to use var

I ran into a bug today that might have been avoided if we weren’t using var.  Both old/new methods return a byte array but the second method is incorrect as the ToUnixTime() in the new method returns an int.  Some might say better unit testing would have caught the issue, and that's true, but it's pretty hard to deny that using var introduced a bug.  As a general rule I try to use specific types instead of var for native types (int, long, string, datetime), the word var only saves me a few characters, and as shown below the return type is important.

Old method:
private static byte[] GenTimeStamp(DateTime currentTime)
    long FileTime = currentTime.ToFileTime();

    // convert to milliseconds since Jan 1, 1601 00:00 UTC
    // and subtract milliseconds between Jan 1, 1601 & Jan 1, 1970
    Int64 HostUnixTime = ((Int64)FileTime / 10000) - WINDOWS_TO_UNIX_MAGIC_NUMBER;
    Int64 NetUnixTime = IPAddress.HostToNetworkOrder(HostUnixTime);
    return BitConverter.GetBytes(NetUnixTime);

New/refactored method (data type is int instead of long):
private static byte[] GenTimeStamp(DateTime currentTime)
    var hostUnixTime = currentTime.ToUnixTime();
    var netUnixTime = IPAddress.HostToNetworkOrder(hostUnixTime);

    return BitConverter.GetBytes(netUnixTime);

Friday, February 8, 2013

Code as Craft

The team over at Etsy creates some pretty interesting software and they have a really interesting blog.  If you are a software developer its worth your time to read it.

Monday, November 19, 2012

VS2012 Active Line Highlight color

Dark theme in VS2012 a little too dark?  Here is how to change it:
Install the  Visual Studio 2012 color theme editor 
Tools - Customize Colors
Active line with default dark theme.
Change these values
New active line highlighting

Saturday, September 1, 2012

How To Replace Rear Speakers in a Honda Accord

Replacing the rear speakers in my 2008 Honda Accord went pretty smoothly.  Overall install time was about 1 hour.  I replaced with the Polk db651.

--Update: Turns out that the Honda head unit will decrease the bass level as volume is turned up, so even though these speakers are better, the Honda stereo is still taking measures to prevent blowing the cheap factory speakers, which leads to only a marginally better sound out of the speakers.

Start by prying off the speaker cover from the outside corner.  Where the screwdriver is in the picture.  Don't try to pry from the inside as the tabs on the inside go underneath the deck.

This is passenger side speaker grill

There is one bolt on the top of the factory speaker, remove it with a Philips screwdriver

Now go inside the trunk and unclip the wiring harness 

The gasket might be a little sticky, but the speaker will now pop right out.  Notice the little clip in the top left in the picture below.  That is the nut for the bolt that you removed previously.  Pop that clip out.

I replaced with the Polk DB651.  Much larger magnet and is noticeably heavier.

Now take the mounting bracket that came with your speaker and mark holes for drilling from the underside of the rear deck.  The mounting bracket for the Polks was NOT symmetrical, so be sure that you are looking at the bottom of the bracket when marking holes.  I'm actually doing it wrong in this picture and had to re-mark and re-drill.  I used a 1/8" bit so that the screws included with the new speakers would anchor in to the rear deck.  I used a cobalt metal drill bit and had no problems going through the metal.

Now screw in the mounting bracket.  Be sure to get all screws started before tightening.

Drop in the new speaker and screw it to the bracket.

Get back in the trunk and connect the wiring.  I left the factory harness in place and just bent the end of the connecting wire a few times and slid it in.  A quick google search says that the blue wire is R+, orange is R-, Yellow is L+, and Brown is L-.

Now just replace the speaker cover and enjoy!

Here are the tools I used