Difference between revisions of "Developer Documentation"
From Synfig Studio :: Documentation
m (add buggennie in Other (links)) |
|||
| Line 30: | Line 30: | ||
* [http://synfig.org/wiki/index.php?title=Special:PrefixIndex&from=&namespace=102 All Dev namespace pages] | * [http://synfig.org/wiki/index.php?title=Special:PrefixIndex&from=&namespace=102 All Dev namespace pages] | ||
| + | * [http://www.synfig.org/issues/thebuggenie/synfig Synfig Issue tracker] (bug, wishlist...) | ||
* {{l|Dev:Translation|Translate the application}} | * {{l|Dev:Translation|Translate the application}} | ||
* {{l|Dev:Release|Release procedure}} | * {{l|Dev:Release|Release procedure}} | ||
* {{l|Dev:GoogleSoC|Google Summer of Code}} | * {{l|Dev:GoogleSoC|Google Summer of Code}} | ||
Revision as of 11:54, 6 January 2013
The Developer Documentation part of this wiki is primarily for the following groups of people:
- Current developers of the code
- Future and potential developers
- Those interested in bug filing and generating ideas
Index:
- Build Instructions
- Building Documentation
- Source code description and workflow
- Roadmap
- Wish List
- Coding Conventions
Synfig is divided into three main components: etl, synfig-core and synfig-studio.
- ETL is the extended template library. One of its most important components is the shared object class, which is the base class for most other parts of the application. Using "handles" to shared objects instead of c++ pointers provides garbage collection via reference counting.
- The core/command-line renderer ("synfig") contains the document data structure for the application: valuenodes, layers, and canvases.
- Synfig Studio ("synfig-studio") provides the gui for the application.
- See also: How Synfig Works
Complete coding tutorials:
- Adding a Layer
- Adding a Panel, Part I and Part II. Note: these are slightly out of date: please note that the directory "gtkmm" has been renamed to "gui" and some files were moved into subfolders.
Other:
