Difference between revisions of "Underlying Assumptions and Concepts"
From gdp3
(Created page with "== Assumptions == === It is possible to name re-usable gameplay design concepts === This assumptions builds on similar assumptions from other design disciplines, most specifical...") |
|||
| Line 2: | Line 2: | ||
=== It is possible to name re-usable gameplay design concepts === | === It is possible to name re-usable gameplay design concepts === | ||
| − | This assumptions builds on similar assumptions from other design disciplines, most specifically the design pattern approach introduced in Architecture<ref name="Alexander"> and commonly used in object-oriented programming<ref name="Gamma"/>. | + | This assumptions builds on similar assumptions from other design disciplines, most specifically the design pattern approach introduced in Architecture<ref name="Alexander"/> and commonly used in object-oriented programming<ref name="Gamma"/>. |
Revision as of 09:43, 19 November 2010
Contents
Assumptions
It is possible to name re-usable gameplay design concepts
This assumptions builds on similar assumptions from other design disciplines, most specifically the design pattern approach introduced in Architecture[1] and commonly used in object-oriented programming[2].
Concepts
References
- ↑ Cite error: Invalid
<ref>tag; no text was provided for refs namedAlexander - ↑ Erich Gamma (Author), Richard Helm (Author), Ralph Johnson (Author), John M. Vlissides Design Patterns: Elements of Reusable Object-Oriented Software.
Cite error: <ref> tag defined in <references> with name "Alexander" has no content.
Cite error: <ref> tag with name "Bjork_.26_Holopainen_2004" defined in <references> is not used in prior text.
