Purpose
As mentioned in the previous post, in order to create good client side controls that interact well with the ASP.NET MVC system, we need to have a way to visualize data that the control either generates, or passes to the controllers. I found this difficult to acheive in IE as well as Firefox. I did not need/want all of the complexities of Firebug or IE's Developer tools (which are great btw). I just wanted to see my data! The problem with the previous version of the debugger was that it was too dang simple! If I were to use it like this:
_('Test').clear() .write('(Simple)') .set(complexArray) .write('(Complex Array)') .set({ one: { a: 'Hospital', b: 4, c: {x:3,y:5}}, two: 'test'}) .write('(Complex Object)') .set(function(arg) { alert('HI!' + arg); }) .write('(function)') .set({ one: new Array('Happy', 'debugger', 'array'), two: 'test'}) .write('(Complex Object)') .set( new Array( new Array( {a: 1, b: 2, c: 3}, {a: 4, b: 5, c: 6}, {a: 7, b: 8, c: 9}), new Array( {a: 'one', b: 'two', c: 'three'}, {a: 'four', b: 'five', c: 'six'}, {a: 'seven', b: 'eight', c: 'nine'}))) .write('(Complex Array)'); });
the debugger would simply not be good enough!
Continue reading Creating Advanced ASP.NET MVC Controls (Part 2, Finished Debugger)