Main Page
From GunGame5 Documentation
(Difference between revisions)
| (35 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| - | |||
| - | |||
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software. | Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software. | ||
== Getting started with GunGame== | == Getting started with GunGame== | ||
| - | * Installation | + | * '''[[Installation]]''' |
| - | + | * '''[[Updating]]''' | |
| - | + | ====If you have a question, check out our '''[[FAQ]]'''.==== | |
| - | * [[ | + | |
| - | + | ||
== GunGame Documentation == | == GunGame Documentation == | ||
| + | === 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"?] | ||
| Line 16: | Line 16: | ||
** [http://docs.python.org/tutorial/modules.html What is a "module"?] | ** [http://docs.python.org/tutorial/modules.html What is a "module"?] | ||
* [[:Category:Class|GunGame Class Reference]]: Information about GunGame classes. | * [[:Category:Class|GunGame Class Reference]]: Information about GunGame classes. | ||
| + | ** [http://docs.python.org/tutorial/classes.html What is a "class"?] | ||
* [[:Category:Method|GunGame Class Method Reference]]: Information about GunGame class methods. | * [[:Category:Method|GunGame Class Method Reference]]: Information about GunGame class methods. | ||
| + | **[http://docs.python.org/tutorial/classes.html#method-objects What is a "method"?] | ||
* [[:Category:Function|GunGame Function Reference]]: Information about GunGame functions. | * [[:Category:Function|GunGame Function Reference]]: Information about GunGame functions. | ||
| - | * | + | ** [http://www.penzilla.net/tutorials/python/functions/ What is a "function"?] |
| - | * [http://www. | + | |
| - | + | ||
| - | == GunGame Python Scripting == | + | === GunGame Addons: === |
| + | * [[scripts.included|Included Addons]] | ||
| + | * [[scripts.custom|Custom Addons]] | ||
| + | |||
| + | === Python Scripting For GunGame: === | ||
| + | * [[Coding custom addons]] | ||
| + | |||
| + | == Python Scripting for GunGame== | ||
* Where did "gungamelib" go? | * Where did "gungamelib" go? | ||
** <p>GunGame 5.1 takes full advantage of [http://docs.python.org/tutorial/modules.html#packages 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 [http://docs.python.org/tutorial/modules.html#intra-package-references "intra-package references"] instead of a congested library that contains all gungame-related commands. | ** <p>GunGame 5.1 takes full advantage of [http://docs.python.org/tutorial/modules.html#packages 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 [http://docs.python.org/tutorial/modules.html#intra-package-references "intra-package references"] instead of a congested library that contains all gungame-related commands. | ||
| Line 29: | Line 36: | ||
Now, we use separate [http://docs.python.org/tutorial/modules.html#packages Python Packages] and [http://docs.python.org/tutorial/modules.html Python Modules]</p> | Now, we use separate [http://docs.python.org/tutorial/modules.html#packages Python Packages] and [http://docs.python.org/tutorial/modules.html Python Modules]</p> | ||
| + | |||
| + | |||
| + | ==== MediaWiki==== | ||
| + | * [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list] | ||
| + | * [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ] | ||
| + | * [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] | ||
Current revision as of 04:31, 24 May 2012
Consult the User's Guide for information on using the wiki software.
Contents |
Getting started with GunGame
If you have a question, check out our FAQ.
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.
GunGame Addons:
Python Scripting For GunGame:
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
