Whats a good way to get familiar with the code?
Many users find it easiest to approach GOPchop development by adding better support for their specific need. Reading the C++ APIs for the MPEG2Parser class is a good place to start if you’re a video format junkie. For those of you interested in user interface changes, you may want to review the GTK API, and the Glade UI designer.
You can start with the Doxygen documentation. There you can find not only the usual Doxygen stuff but also different categorized views into the inkscape source. In the Documentation section of the Inkscape website you can find some high-level diagrams and links to other documentation that’s been produced such as the man page. Historically, this codebase has not been kept well documented so expect to find many areas where the only recourse is to work through the code itself. However, we place importance on working to change this, and to flesh out the documentation further as we go. Some developers have found that testing patches is a good way to quickly get exposure to the code, as you see how other developers have approached making changes to the codebase. Other developers like to pick an interesting feature request (or perhaps a feature wish of their own) and focus on figuring out how to implement it. Occasionally we also have large scale grunt-work type changes that need to be applie
