Main Page
From GunGame5 Documentation
Line 11: | Line 11: | ||
== GunGame Documentation == | == GunGame Documentation == | ||
- | * [[:Category:Package Overview|GunGame Package Overview]]: | + | === The GunGame Package === |
+ | * [[:Category:Package Overview|GunGame Package Overview]]: View the contents of the entire GunGame package. | ||
+ | |||
+ | === GunGame Packages, Modules, Classes, Methods, & Functions === | ||
* [[:Category:Package|GunGame Package Reference]]: Information about GunGame packages. | * [[:Category:Package|GunGame Package Reference]]: Information about GunGame packages. | ||
** [http://docs.python.org/tutorial/modules.html#packages What is a "package"?] | ** [http://docs.python.org/tutorial/modules.html#packages What is a "package"?] |
Revision as of 04:37, 28 April 2009
MediaWiki has been successfully installed.
Consult the User's Guide for information on using the wiki software.
Contents |
Getting started with GunGame
- Installation
GunGame Addons
GunGame Documentation
The GunGame Package
- GunGame Package Overview: View the contents of the entire GunGame package.
GunGame Packages, Modules, Classes, Methods, & Functions
- GunGame Package Reference: Information about GunGame packages.
- GunGame Module Reference: Information about GunGame modules.
- GunGame Class Reference: Information about GunGame classes.
- GunGame Class Method Reference: Information about GunGame class methods.
- GunGame Function Reference: Information about GunGame functions.
Python Scripting for GunGame
- Where did "gungamelib" go?
-
GunGame 5.1 takes full advantage of Python Packages which allows us to better organize and structure the code into logical groups. This not only helps the developers find/fix bugs faster due to the fact that we can now see which module is causing the error but enables us to see which packages and modules have been changed separately. GunGame 5.1 now uses "intra-package references" instead of a congested library that contains all gungame-related commands.
-
Originally, when we added changes to gungamelib, we only knew (without delving through several revisions) that "something" had been changed in the core functionality of GunGame. If this caused a bug, it became very hard to track down (especially if the bug did not manifest itself or be report until several revisions down the line).
Now, we use separate Python Packages and Python Modules