The animation below represents the first 6 years of development of the Tux Paint project, compressed down to about 1 and a half minutes. It's visualizes each of the project team members (shown as usernames), and the files they worked on in the source code repository for the core "Tux Paint" application (shown as colored dots — different colors represent different parts of the project, i.e., documentation, data files, and various parts of the source code).
It was generated in October 2008 using code_swarm.
Source Code Size
Below is an analysis of the size of Tux Paint's source code. It was generated in October 2008 using David A. Wheeler's SLOCCount tool.
|SLOC||Directory||SLOC by Language|
Totals grouped by language:
|Total Physical Source Lines of Code (SLOC)||= 27,208|
|Development Effort Estimate, Person-Years (Person-Months)|
(Basic COCOMO model, Person-Months = 2.4 * (KSLOC**1.05))
|= 6.42 (77.03)|
|Schedule Estimate, Years (Months)|
(Basic COCOMO model, Months = 2.5 * (person-months**0.38))
|= 1.09 (13.03)|
|Estimated Average Number of Developers (Effort/Schedule)||= 5.91|
|Total Estimated Cost to Develop|
(average salary = USD$56,286/year, overhead = 2.40).
Download Survey Form Feedback
The links below show statistical information and charts based on the collected feedback from the optional survey form on the Download page. From it, you can get an idea of who downloads Tux Paint (parents vs. teachers), what countries they're from, etc.
- Survey statistics: September 2003 through November 2008
The first major analysis of survey data, generated from over 62,000 submissions.