Difference between revisions of "Portal:Developers"
(add poll) |
|||
Line 4: | Line 4: | ||
<div> | <div> | ||
{| width="100%" style="border:0; margin: 0;" cellspacing="0" | {| width="100%" style="border:0; margin: 0;" cellspacing="0" | ||
− | | | + | | valign="top" | |
− | <div style="float:right; width:100%"> | + | <br /><!-- newline as poll has a bug that gives it an emptly line at the top |
+ | --><div style="float:right; width:100%"> | ||
{{Developers/box-header|''Categories''|Developers/Categories}} | {{Developers/box-header|''Categories''|Developers/Categories}} | ||
</div> | </div> | ||
| valign="top" | | | valign="top" | | ||
+ | <div valign="top"> | ||
+ | {{#lst:Poll|polldevelpage}} | ||
+ | </div> | ||
+ | |} | ||
+ | </div> | ||
+ | <!-- third row of boxes | ||
+ | --><div> | ||
+ | {| width="100%" style="border:0; margin: 0;" cellspacing="0" | ||
+ | | width="33%" valign="top" | | ||
<div style="float:right; width:100%"> | <div style="float:right; width:100%"> | ||
{{Developers/box-header|''Report System''|Developers/Write a Report}} | {{Developers/box-header|''Report System''|Developers/Write a Report}} | ||
+ | </div> | ||
+ | | width="33%" valign="top" | | ||
+ | <div style="float:right; width:100%"> | ||
+ | {{Developers/box-header|''Internationalization''|Developers/Internationalization}} | ||
+ | </div> | ||
+ | | valign="top" | | ||
+ | <div style="float:right; width:100%"> | ||
+ | {{Developers/box-header|''Specifications''|Developers/Specifications}} | ||
</div> | </div> | ||
|} | |} |
Revision as of 19:51, 6 March 2007
Gramps is programmed in the Python language.
If you are an adventurous user, have some technical experience, or have a programming background, you might like to try Getting started with Gramps master.
You might want to start with obtaining the source code or have a look at Getting started with Gramps development. Once you have the code, writing a report or a quick view report is a great way to learn to navigate through the codebase; see also Addons development.
After becoming familiar with Gramps, you might want to help work on a proposal, or make a proposal yourself you want to spend time on. Both can be done at the Proposals Portal, in collaboration with the bug/feature tracker.
Developer Resources
- Getting started with Gramps development - introduction.
- Getting started with Gramps master - advanced.
- Gramps-devel mailing list
- Debugging Gramps
- Using database API - basics introductory programmer's guide to using the Gramps database access routines.
- Signals and Callbacks - The Gramps signaling system used to pass changes in the db, GUI, or other sources to various elements (usually the GUI) that need to be updated when changes occur.
- Translation tutorial
- Programming guidelines
- Developer policies
- Official committing policies
- Project License
- What to do for a new Gramps release - includes process for creating a Gramps source package.
- Addons development
- Git tutorial - used for Gramps and addons development. (for Gramps 4.2 and newer)
- Subversion (SVN) tutorial - used for addons development (for Gramps 4.1 and older)
- Using the bug tracker
- Python.org
- Python, Gtk3 tutorial
- Gramps Code Documentation
- API.svg - Simple class diagram in the Unified Modeling Language (UML in svg format) showing the system's classes, their attributes, operations (or methods), and the relationships among objects.
edit Categories
Developers Categories : Artwork | General | Packaging | Addons / Plugins | References | Reports | Roadmap | Translation | Tutorials |
No poll running at the moment |
edit Report System
A good way to learn the Gramps codebase is by writing a small report.
Reports are plugins that can be distributed separately as unofficial Addons/plugins; see Addons development. Documentation for writing reports can be found in the Database API and Report API. There is also a Report writing tutorial and a technical description of report generation. |
edit Internationalization
|