Difference between revisions of "DevelopersHome"
From The Battle for Wesnoth Wiki
(→Tools and Packaging) |
m (Added FOSDEM 2010 & 2011) |
||
| Line 86: | Line 86: | ||
** [[Fosdem2008]] | ** [[Fosdem2008]] | ||
** [[Fosdem2009]] | ** [[Fosdem2009]] | ||
| + | ** [[Fosdem2010]] | ||
| + | ** [[Fosdem2011]] | ||
* Google Summer of Code | * Google Summer of Code | ||
| Line 91: | Line 93: | ||
** [[SoC_Information_for_Google]] - Our organization profile for Google | ** [[SoC_Information_for_Google]] - Our organization profile for Google | ||
** [[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 = | ||
Revision as of 04:04, 10 August 2011
Contents
General Information
- Links
- Changelog - the most recent changes made to the game
- Latest commits - Up-to-date commit messages
- Coding Guidelines
- HackingWesnoth - guide for programmers
- CodingStandards - for programmers
- DeveloperGuide - for those who received SVN commit rights
- Library documentation
- http://www.sgi.com/tech/stl/ - Standard Template Library
Tools and Packaging
- Supporting Websites
- WesnothSVN - accessing the source code
- http://websvn.wesnoth.org/ Web-Access to svn - Gna! - websvn -
- http://gettext.wesnoth.org/ - gettext status
- Compiling and Building
- CompilingWesnoth - how to compile Battle for Wesnoth (it's not hard)
- SCons
- UsingAutotools
- Packaging and Releasing
- ReleasingWesnoth - steps to follow to release a new version
- WesnothPackagersGuide - guidelines for packaging Wesnoth for different platforms
- 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
- Wesnoth_Acronyms_and_Slang
Game - Create content
- BuildingScenarios and related useful forum discussions:
- ReferenceWML
Code documentation
- http://devdocs.wesnoth.org - generated code documentation
- AI
- 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
- FOSDEM
- 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