DevelopersHome: Difference between revisions
From The Battle for Wesnoth Wiki
m →Code documentation: update a link |
m Fix section headings. Do not use first-level headings in page contents. |
||
| Line 1: | Line 1: | ||
= General Information = | == General Information == | ||
* Links | * Links | ||
** [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game | ** [http://changelog.wesnoth.org Changelog] - the most recent changes made to the game | ||
| Line 18: | Line 18: | ||
** [[DebuggingWesnoth]] | ** [[DebuggingWesnoth]] | ||
= Tools and Packaging = | == Tools and Packaging == | ||
* Supporting Websites | * Supporting Websites | ||
** [[WesnothRepository]] - accessing the source code | ** [[WesnothRepository]] - accessing the source code | ||
| Line 34: | Line 34: | ||
** [[UsingGooglePerformanceTools]] to profile Wesnoth CPU and memory usage. | ** [[UsingGooglePerformanceTools]] to profile Wesnoth CPU and memory usage. | ||
= I want to start coding, what can I do? = | == I want to start coding, what can I do? == | ||
* [[EasyCoding]] - Bugs and features that are easy to implement for new coders | * [[EasyCoding]] - Bugs and features that are easy to implement for new coders | ||
* [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them | * [[NotSoEasyCoding]] - Bugs and features which are doable but lacking someone working on them | ||
| Line 41: | Line 41: | ||
* [[Glossary]] | * [[Glossary]] | ||
= Game - Create content = | == Game - Create content == | ||
* [[BuildingScenarios]] and related useful forum discussions: | * [[BuildingScenarios]] and related useful forum discussions: | ||
** [http://www.wesnoth.org/forum/viewtopic.php?t=4188 Beginning Campaign Development] | ** [http://www.wesnoth.org/forum/viewtopic.php?t=4188 Beginning Campaign Development] | ||
| Line 47: | Line 47: | ||
* [[ReferenceWML]] | * [[ReferenceWML]] | ||
= Code documentation = | == Code documentation == | ||
* http://devdocs.wesnoth.org - generated code documentation | * http://devdocs.wesnoth.org - generated code documentation | ||
* AI | * AI | ||
| Line 68: | Line 68: | ||
** [[SavegameClassHierarchy]] | ** [[SavegameClassHierarchy]] | ||
= Communication, Feedback, Events = | == Communication, Feedback, Events == | ||
* Gna! links | * Gna! links | ||
** http://bugs.wesnoth.org/ - Gna! - bugs and feature requests | ** http://bugs.wesnoth.org/ - Gna! - bugs and feature requests | ||
| Line 97: | Line 97: | ||
** [[SoC_People_to_bug_on_IRC]] - Who GSoC students can ask for help | ** [[SoC_People_to_bug_on_IRC]] - Who GSoC students can ask for help | ||
= Miscellaneous = | == Miscellaneous == | ||
* [[DebugMode]] and [[CommandMode]] - in game debugging commands | * [[DebugMode]] and [[CommandMode]] - in game debugging commands | ||
* [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing | * [http://www.wesnoth.org/units/trunk/animations.html Missing unit animations] - what's available and what's missing | ||
Revision as of 20:14, 30 August 2017
General Information
- Links
- Changelog - the most recent changes made to the game
- Latest commits - Up-to-date commit messages
- Coding Guidelines
- Git_for_Wesnoth_Crash_Course - guide for contributors who are new to git
- HackingWesnoth - guide for programmers
- CodingStandards - for programmers
- DeveloperGuide - for those who received repository commit rights
- SoftwareTesting - for programmers
- Library documentation
- Debugging Tips
Tools and Packaging
- Supporting Websites
- WesnothRepository - accessing the source code
- http://gettext.wesnoth.org/ - gettext status
- Compiling and Building
- CompilingWesnoth - how to compile Battle for Wesnoth (it's not hard)
- SCons
- Packaging and Releasing
- ReleasingWesnoth - steps to follow to release a new version
- Documentation
- Doxygen - Documentation generator
- More stuff
- ExternalUtilities (Wercator, CampGen, wmllint, etc.)
- MaintenanceTools WMLLint, WMLIndent and WMLScope
- UsingGooglePerformanceTools to profile Wesnoth CPU and memory usage.
I want to start coding, what can I do?
- EasyCoding - Bugs and features that are easy to implement for new coders
- NotSoEasyCoding - Bugs and features which are doable but lacking someone working on them
- GettingStarted
- FrequentlyProposedIdeas - summary of past often-repeated forum discussions
- Glossary
Game - Create content
- BuildingScenarios and related useful forum discussions:
- ReferenceWML
Code documentation
- http://devdocs.wesnoth.org - generated code documentation
- AI
- Wesnoth_AI - Starting point for AI documentation
- Themes
- ThemeSystem - customizing the screen layout for the game and the editor
- Multiplayer
- WesnothdDesign - Guide to the design of wesnothd, the multiplayer server.
- Gui2 - The new Gui-Framework
- Savegames
Communication, Feedback, Events
- Gna! links
- http://bugs.wesnoth.org/ - Gna! - bugs and feature requests
- http://patches.wesnoth.org/ - Gna! - patches
- Mailing lists
- https://mail.gna.org/listinfo/wesnoth-dev/ - wesnoth-dev
- https://mail.gna.org/listinfo/wesnoth-commits/ - wesnoth-commits
- IRC
- freenode/#wesnoth-dev - IRC (alias to irc.freenode.net)
- http://irclog.wesnoth.org/ - IRC logs
- Forum - http://forum.wesnoth.org
- This wiki - http://www.wesnoth.org/wiki/Main_Page
- Google Summer of Code
- SummerOfCodeIdeas - Ideas for GSoC
- SoC_Information_for_Google - Our organization profile for Google
- SoC_People_to_bug_on_IRC - Who GSoC students can ask for help
Miscellaneous
- DebugMode and CommandMode - in game debugging commands
- Missing unit animations - what's available and what's missing
- http://units.wesnoth.org/ - Unit reference
This page was last edited on 30 August 2017, at 20:14.