Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
public:gsoc:pythonprofiler [2020/02/05 07:30]
cfsmp3 [Ideas]
public:gsoc:pythonprofiler [2020/02/27 21:33] (current)
kdrag0n
Line 1: Line 1:
-===== Introduction ​=====+===== Program Flow Visualizer ​===== 
 + 
 +==== Introduction ​====
 Read [[https://​medium.com/​@carlosfernandezsanz/​generating-videos-of-algorithms-implementations-with-python-3422c4dd04f0|this]] and then come back here :-) Read [[https://​medium.com/​@carlosfernandezsanz/​generating-videos-of-algorithms-implementations-with-python-3422c4dd04f0|this]] and then come back here :-)
  
-===== Your job ===== +==== The Task ==== 
-We want to build a complete profiler tool. During ​GCI we created several proofs of concept, so we know it's possible, and we also know that it's a really good idea that got popular really fast. For reference, as you can see in the article linked above, five high school students created each their own implementation (by themselves) in around one month with really impressive results.+We want to build a complete profiler tool. During ​Google Code-in ​we created several proofs of concept, so we know it's possible, and we also know that it's a really good idea that got popular really fast. For reference, as you can see in the article linked above, five high school students created each their own implementation (by themselves) in around one month with really impressive results.
  
-You can take their job (hey, this is open source, ​it's all about using someone else's work) and build on it, or you can do your own thing. But of course, your result ​must show that it's a GSoC project ​- you have 3 months ​working full time :-)+You can take their existing work (it'​s ​open-source after all) and build upon it, or you can do your own thing. But of course, your product ​must demonstrate ​GSoC quality ​- you'll be working full-time for 3 months ​:-)
  
-===== Ideas =====+==== Ideas ====
  
   * Explore use-cases other than algorithms ([[https://​news.ycombinator.com/​item?​id=22179697|comment on Hacker News]])   * Explore use-cases other than algorithms ([[https://​news.ycombinator.com/​item?​id=22179697|comment on Hacker News]])
Line 18: Line 20:
   * Integration with gdb and in general, support for other languages [if possible]   * Integration with gdb and in general, support for other languages [if possible]
   * Manual control keys (Play, pause, speed)   * Manual control keys (Play, pause, speed)
 +  * Control flow chart (as an overview)
 +  * Support for //all// types of objects in saved sessions, even those that cannot be serialized directly
 +
 +
 +This is another potential source of inspiration:​ https://​github.com/​hediet/​vscode-debug-visualizer/​tree/​master/​extension
 +
 +==== Qualification tasks ====
 +In order to qualify for our projects, you must complete a qualification task or accrue sufficient qualification points from GitHub issues.
  
 +Take a look at [[https://​ccextractor.org/​public:​gsoc:​takehome|this page]] for tasks oriented for people who are working on new projects like this one. Alternatively,​ you can go the traditional route of fixing GitHub issues on the main CCExtractor project, which is written in C. You can find more information about this [[https://​ccextractor.org/​public:​gsoc:​ideas_page_for_summer_of_code_2020#​about_the_projects_and_getting_accepted|here]].
  • public/gsoc/pythonprofiler.1580887816.txt.gz
  • Last modified: 2020/02/05 07:30
  • by cfsmp3