Difference between revisions of "DevelopersHome"
From The Battle for Wesnoth Wiki
Pentarctagon (talk | contribs) |
Pentarctagon (talk | contribs) (→Code documentation) |
||
| Line 56: | Line 56: | ||
** [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server. | ** [[WesnothdDesign]] - Guide to the design of wesnothd, the multiplayer server. | ||
* Gui2 - The new Gui-Framework | * Gui2 - The new Gui-Framework | ||
| + | ** [[https://devdocs.wesnoth.org/group__GUIWidgetWML.html|Widgets]] | ||
** [[GUIToolkit]] | ** [[GUIToolkit]] | ||
** [[GUILayout]] | ** [[GUILayout]] | ||
| − | |||
** Gui2 WML | ** Gui2 WML | ||
*** [[GUICanvasWML]] | *** [[GUICanvasWML]] | ||
*** [[GUIToolkitWML]] | *** [[GUIToolkitWML]] | ||
| − | |||
| − | |||
*** [[GUIWindowDefinitionWML]] | *** [[GUIWindowDefinitionWML]] | ||
| − | |||
| − | |||
== Communication, Feedback, Events == | == Communication, Feedback, Events == | ||
Revision as of 07:10, 22 January 2021
Contents
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
- Compiling Wesnoth - how to compile Battle for Wesnoth (it's not hard)
- 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
- Frequently Proposed Ideas - summary of past often-repeated forum discussions
- Glossary
Game - Create content
- BuildingScenarios and related useful forum discussions:
- ReferenceWML
- DeprecationLevels
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
Communication, Feedback, Events
- http://bugs.wesnoth.org/ - bug reports and feature requests
- http://patches.wesnoth.org/ - patches/pull requests
- Mailing lists
- 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