SummerOfCode/2013/newMemoryPage: Difference between revisions
No edit summary |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
== | == About the project == | ||
This is the development tracking page for the creation of a new memory information page, which is [http://www.google-melange.com/gsoc/project/google/gsoc2013/abhishekchoudhary/3001 a Google's Summer of Code project]. | This is the development tracking page for the creation of a new memory information page, which is [http://www.google-melange.com/gsoc/project/google/gsoc2013/abhishekchoudhary/3001 a Google's Summer of Code project]. | ||
The idea is to create an interactive | The idea is to create an interactive page which will demystify memory statistics for people who are ''not'' involved in developing the browser, but are interested users, or independent web developers, who would like to know about the footprint that the browser creates under-the-hood. | ||
The | The project will be developed as an extension using the Firefox Add-On (formerly Jetpack) SDK, and would mainly make use of HTML, CSS and JavaScript. The visualizations and interactions would be handled by the library [http://d3js.org/ D3.js]. | ||
== Development Chronology == | |||
✔ | ✔ [https://wiki.mozilla.org/SummerOfCode/2013/newMemoryPage/week1 Week 1] (Summary: Repository initialized) | ||
✔ | ✔ [https://wiki.mozilla.org/SummerOfCode/2013/newMemoryPage/week2 Week 2] (Summary: First data-set pulled) | ||
✔ | ✔ [https://wiki.mozilla.org/SummerOfCode/2013/newMemoryPage/week3 Week 3] (Summary: [http://bugzilla.mozilla.org/show_bug.cgi?id=893193 New bug] discovered) | ||
✔ | ✔ [https://wiki.mozilla.org/SummerOfCode/2013/newMemoryPage/week4 Week 4] (Summary: Target library running) | ||
✔ | ✔ [https://wiki.mozilla.org/SummerOfCode/2013/newMemoryPage/week5 Week 5] (Summary: Inconsistencies in the data-set corrected) | ||
✔ | ✔ [https://wiki.mozilla.org/SummerOfCode/2013/newMemoryPage/week6 Week 6] (Summary: Preparing first build) | ||
✔ | ✔ [https://wiki.mozilla.org/SummerOfCode/2013/newMemoryPage/week7 Week 7] (Summary: Prototype is up at [http://git.io/fx-stats git.io/fx-stats]) | ||
✔ [https://wiki.mozilla.org/SummerOfCode/2013/newMemoryPage/week8 Week 8] (Summary: Adding live updates) | |||
✔ [https://wiki.mozilla.org/SummerOfCode/2013/newMemoryPage/week9 Week 9] (Summary: Addressing memory leaks) | |||
✔ [https://wiki.mozilla.org/SummerOfCode/2013/newMemoryPage/week10 Week 10] (Summary: Adding a time-slider and start/stop concept to live updates) | |||
✔ [https://wiki.mozilla.org/SummerOfCode/2013/newMemoryPage/week11 Week 11] (Summary: Implementing more visualizations) | |||
✔ [https://wiki.mozilla.org/SummerOfCode/2013/newMemoryPage/week12 Week 12] (Summary: Improving new visualizations) | |||
✔ [https://wiki.mozilla.org/SummerOfCode/2013/newMemoryPage/week13 Week 13] (Summary: Re-factoring system calls to improve speed) | |||
✔ [https://wiki.mozilla.org/SummerOfCode/2013/newMemoryPage/week14 Week 14] (Summary: v1.0.0 is bundled and uploaded) | |||
== Additional Links == | |||
⦁ The [https://docs.google.com/file/d/0B4gxz1Wag9ISTzdKUTM5NEdyNWc original project proposal] | |||
⦁ The [https://github.com/abhishekchoudhary/fx-statistics code repository] | |||
⦁ The [http://trystswithcode.quora.com/In-the-name-of-numbers wrap-up post] by the [http://abhishekchoudhary.com/ developer] | |||
⦁ The extension on [https://addons.mozilla.org/en-US/firefox/addon/fx-statistics/ AMO] | |||
Latest revision as of 14:06, 25 September 2013
About the project
This is the development tracking page for the creation of a new memory information page, which is a Google's Summer of Code project.
The idea is to create an interactive page which will demystify memory statistics for people who are not involved in developing the browser, but are interested users, or independent web developers, who would like to know about the footprint that the browser creates under-the-hood.
The project will be developed as an extension using the Firefox Add-On (formerly Jetpack) SDK, and would mainly make use of HTML, CSS and JavaScript. The visualizations and interactions would be handled by the library D3.js.
Development Chronology
✔ Week 1 (Summary: Repository initialized)
✔ Week 2 (Summary: First data-set pulled)
✔ Week 3 (Summary: New bug discovered)
✔ Week 4 (Summary: Target library running)
✔ Week 5 (Summary: Inconsistencies in the data-set corrected)
✔ Week 6 (Summary: Preparing first build)
✔ Week 7 (Summary: Prototype is up at git.io/fx-stats)
✔ Week 8 (Summary: Adding live updates)
✔ Week 9 (Summary: Addressing memory leaks)
✔ Week 10 (Summary: Adding a time-slider and start/stop concept to live updates)
✔ Week 11 (Summary: Implementing more visualizations)
✔ Week 12 (Summary: Improving new visualizations)
✔ Week 13 (Summary: Re-factoring system calls to improve speed)
✔ Week 14 (Summary: v1.0.0 is bundled and uploaded)
Additional Links
⦁ The original project proposal
⦁ The code repository
⦁ The wrap-up post by the developer
⦁ The extension on AMO