I watched a screen-cast recently on how Ruby on Rails takes CRUD (Create, Read, Update, Delete) to its very extreme in order to come out with a software design that is to create, understand and modify. Here is the link for it: Love the CRUD.
After watching it, I couldn’t help but think back to a past project of mine where we kept running into the issue where our controllers and service classes kept turning into gigantic monsters and we would struggle to break them. The fact that we were stuck with an existing design that greatly contributed to this problem didn’t help either. Regardless, I think following the approach outlined in the screen cast would be a huge step in the right direction to help address this issue.
The screen-cast is somewhat lengthy so hope you can hang in there. 
Cheers!
JQuery snippet to detect keystrokes on the numeric key-pad.
The below JQuery snippet returns the character corresponding to the key that was pressed on the QWERTY keyboard or the numeric key-pad. For instance, pressing the ’1′ key will return the text ’1′. Similarly, pressing the ‘+’ key will return back the text ‘+’.
$(document).keydown(function (event) { toCharacter(event.keyCode); }); function toCharacter(keyCode) { // delta to convert num-pad key codes to QWERTY codes. var numPadToKeyPadDelta = 48; // if a numeric key on the num pad was pressed. if (keyCode >= 96 && keyCode <= 105) { keyCode = keyCode - numPadToKeyPadDelta; return String.fromCharCode(keyCode); } if (keyCode == 106) return "*"; if (keyCode == 107) return "+"; if (keyCode == 109) return "-"; if (keyCode == 110) return "."; if (keyCode == 111) return "/"; // the 'Enter' key was pressed if (keyCode == 13) return "="; //TODO: you should change this to interpret the 'Enter' key as needed by your app. return String.fromCharCode(keyCode); }
A little explanation is probably in order…
Javascript provides the
String.fromCharCode()
method that converts an ASCII character code into it’s equivalent text value. For instance,
String.fromCharCode(65)
returns the character ‘A’. The method works great until to try to use it for keys that live on the numeric keypad.
The ASCII code for the ’1′ key on the numeric key pad is 97. If you look this up on the ASCII Table, you will find that the ASCII code 97 corresponds to the character ‘a’ and not the character ’1′ denoted on the numeric key pad! The reason for this, as far I can tell, is that the numeric keys simply overload on the existing the ASCII codes.
A little calculation will reveal that subtracting 48 from the ASCII code of the numeric keys will give us the “correct” ASCII code. For instance, subtracting 97 (which is the ASCII code for the ’1′ key on the numeric keypad) from 48 gives us 49. Look up the ASCII code 49 on the ASCII Table and you will find that it maps to the character ’1′!
For the keys that correspond to the various symbols such as ‘+’, ‘-’, etc., I am simply returning back the corresponding character. No mystery there.
Hope this helps!