| 25 | | |
| 26 | | == Writing add-on software == |
| 27 | | |
| 28 | | BOINC's architecture is 'open'; documented interfaces making it possible to develop various types of applications and web sites that interact with BOINC components. Examples include: |
| 29 | | |
| 30 | | * [GuiRpc Client GUIs]: Applications that control a local or remote core client. |
| 31 | | * [CreditStats Credit statistics web sites]: Web sites showing credit information (project totals, user/team/country leaderboards) based on daily XML feeds of statistics data from BOINC projects. The XML format is documented [XmlStats here]. |
| 32 | | * [AccountManagement Account managers]: Web sites that let BOINC users create and manage accounts on multiple projects. |
| 33 | | * [StatsXml Aggregate credit statistics]: Web RPCs for getting cross-project credit data for hosts, teams and users. |
| 34 | | * [WebRpc Web RPCs]: These interfaces let a program or web site obtain information about projects, and create/edit entities (users, teams, hosts) on projects. |
| 35 | | * [PrefsOverride Local editing of preferences]: This mechanism lets you write programs for local editing of preferences. |
| 36 | | |
| 37 | | Check [/addons.php the index of add-on software] before writing anything (it may already exist). The index has instructions for submitting new add-ons. |
