Document code

[pjotrp]

At this point it is not too clear (to a newcomer) how the framework operates. I suggest to add a doment in ./doc/design.md which describes how interaction between components is achieved and what you would need to do to add another interactive component.

In the code itself we should put a short description above every function - unless it is totally self-explanatory. For example, in dataframe.js it should state what a dataframe is, what it does and how it interacts, so that people can understand the code beneath without going into detail.

If we document this project well, the chance is higher that other people will start using and contributing to the source base.

[domitry]

I try to add document about design, but I am going to change API from now, so before finishing gsoc term, sciruby blog will be useful instead of document. Thank you.

The progress of documented code:
./src/view

• pane.js

./src/view/diagrams

• bar.js
• box.js
• scatter.js
• venn.js
• line.js
• histogram.js
• diagrams.js
• heatmap.js
• multiple_venn.js
• vectors.js

./src/view/components

• axis.js
• filter.js
• legend_area.js
• simple_legend.js
• scale.js
• tooltip.js
• color_bar.js

./src/core/

• extension.js
• manager.js
• parse.js

./src/utils

• dataframe.js
• simplex.js
• color.js
• ua_info.js

[domitry]

Finished writing comments for documentation :)