Techniques to Reduce Complexity in Game Programming [closed]
-
23-09-2019 - |
문제
In my spare time I program games as a hobby, different sorts of things and currently nothing very complex. Things likes 2d shooters, Tile-Based games, Puzzle Games, etc...
However as the development of these games goes on I find it becomes hard to manage the complexity of different subsystems within the games, things like Interface, World View/Model, Event Handling, States (Menu's, Pause, etc...), Special Effects and so on.
I attempt to keep the connections to a minimum and reduce coupling however many of these systems need to talk in one way or another that doesn't require holding your entire code-base in your head at one time.
Currently I try to delegate different subsystems and subsystem functions to different objects that are aggregated together however I haven't found a communication strategy that is decoupled enough.
What sort of techniques can I use to help me juggle all of these different subsystems and handle the complexity of an ever increasing system that needs to be modular enough to facilitate rapid requirements change?
I often find myself asking the same questions:
- How do objects communicate with each other?
- Where should the code that handles specific subsystems go?
- How much of my code base should I have to think about at one time?
- How can I reduce coupling between game entities?
해결책
예, SharePoint가 CSS를 덮어 쓸 수 있기 때문에 기본 부트 스트랩이 SharePoint에서 실행되지 않습니다. http://bootstrapsharepoint.codeplex.com 를 확인하십시오.