Fulltext results:
- developer_guidelines
- project manager for answers, which may then be added to this document. ===== Code conventions ===== ... ration in predicates, this practice should be avoided wherever possible. If the need for this is appar... s! // Erroneous field reuse should be avoided at all costs } // do more with thing... n't do the above either, // If a field is needed outside the scope of the // conditional expre
- player_controls
- * Periodic position, velocity, and direction information from the players (these don't have to have... n could be sent less frequently). This is generic information that cannot be modified by games. * Imp... y that the old concept of ticcmds is no longer needed in this system. We are focusing on providing a ... f the local players. The server will respect this information and apply necessary safeguards against che
- roadmap
- ====== Project roadmap ====== See: [[http://tracker.dengine.net/projects/deng/roadmap|Project roadmap]] ===== Conventions ===== Doomsday's release cycle is designed around stable relea... ork, productization, and bug fixing. This is intended to result in high-quality code and a decreasing k
- file_system
- s anywhere in the tree. It also contains semantic information about the structure and content of the tre... central role in [[libdeng2]]. It is not simply a mapping of the native file system contents to a porta... ystem occurs via ''de::FS''. The folder ///home// maps to the user's runtime folder and has write acces... e source data has not changed. Repopulation is needed for instance when native files get deleted in the
- libcore
- o see the [[api_documentation]] for more in-depth information.}} [[libcore]] is the name of the shared ... or talking with servers. Generic UI components needed by the Shell apps and the UI framework. ===== G... fore C++ was taken into use. This library is intended to eventually become obsolete as more and more co... em]] * [[doomsday_script]] * [[plugin_factory]] * [[packaging_resources]] * [[roadmap]]
