SummerOfCode/2013/newMemoryPage/week5: Difference between revisions

Having happily addressed the problem of data polling in the second week, I did not think I would have to look into it again. But, as it turns out, I had to look, and look hard. It turns out that the memory reporters come in two flavors -- the 'single' memory reporters, and 'multi' memory reporters. It has generally been agreed that this project should be useful to web developers, and for it to do that, it must address the individual tabs in a separate visualization.

Unfortunately, the data that I had been polling, from the single reporters, did not contain that data. It was a time of great distress, because I tried every trick I knew, but could not get the multi reporters to talk to me in the way that I wanted (read: could not get a hierarchical structure). That is when my mentor stepped in and showed me how to design a dedicated multi-reporter-enumerator method ([https://github.com/abhishekchoudhary/fx-statistics/blob/master/lib/main.js#L102 see it here]).

Roadblock : avoided! On to the visuals again!