reqs.h

Go to the documentation of this file.
00001 /*
00002  * reqs.h
00003  *
00004  * Bogus header file for Doxygen documentation.  Don't use this file!
00005  */
00006 
00007 /// \ingroup aesop_lib
00008 /// \defgroup reqs AESOP Requirements and Features
00009 ///
00010 /// This lists the functional requirements for the Framework.
00011 ///
00012 /// \n
00013 /// \section reqs_what What is a Game Framework?
00014 ///
00015 /// If you do a web search for "game framework" or "3d game engine", you'll get
00016 /// a lot of hits.  Many of the results aren't what I would consider a real
00017 /// game framework.  Some are just 3D graphics libraries, and even those with
00018 /// more functionality (physics, or even AI) often don't support networked mode,
00019 /// or are tightly coupled to particular graphics libraries.
00020 ///
00021 /// Partly that is just a matter of semantics.  What is a Framework?  Wiki has
00022 /// a decent definition: http://en.wikipedia.org/wiki/Software_framework
00023 ///
00024 /// But just to make it clear, here are the requirements that I have laid out.
00025 ///
00026 /// \n
00027 /// \section reqs_reqs Multiplayer Networked 3D Game Framework Requirements
00028 ///
00029 /// - Must provide a working networked game out-of-the-box.
00030 /// - Must allow for all of the following to be extended or replaced easily:
00031 ///  - graphics (both the rendering libraries and formats)
00032 ///  - audio
00033 ///  - physics
00034 ///  - artificial intelligence
00035 ///  - game logic
00036