BenTrem/Sandbox – User
Jump to navigation
Jump to search
mNo edit summary |
(a bit of text about FSM) |
||
Line 6: | Line 6: | ||
* [[ArmA_2_Terrain_Tutorial|ArmA2 Terrain Tutorial including Tools Setup in detail]] | * [[ArmA_2_Terrain_Tutorial|ArmA2 Terrain Tutorial including Tools Setup in detail]] | ||
* [http://www.flashpoint1985.com/cgi-bin/ikonboard311/ikonboard.cgi?;act=ST;f=64;t=63971 "Collection of Undocumented/Lesser-Known Features" at FlashPoint 1985.com] | * [http://www.flashpoint1985.com/cgi-bin/ikonboard311/ikonboard.cgi?;act=ST;f=64;t=63971 "Collection of Undocumented/Lesser-Known Features" at FlashPoint 1985.com] | ||
---- | |||
Pieter Hintjens on FSM, from [http://legacy.imatix.com/html/libero/lrintr.htm the Libero documentation]: | |||
: "ETK provides an interactive editor that you use to describe the logic of the program as a FSM. This approach encourages you to think about the complete problem. You describe everything that can happen, and how the program should react. The end- result looks a little like a flow-chart, but has more arrows, and fewer different kinds of boxes. The value of this approach is that you can abstract a complex problem using the restricted semantics of a FSM. In the same way that a While statement is less powerful but more useful than a Goto, a FSM is less powerful but more useful than a structured programming approach for describing complex problems. Leif Svalgaard once said: "the issue is not one of power, but coping with the human difficulty in understanding complex structures". | |||
---- | ---- | ||
[[Category:Sandbox]] | [[Category:Sandbox]] |
Revision as of 20:45, 5 April 2012
- Transport helicopter Role
- ComRef
- ArmA Tournament sites
- Category:Hints & Tips
- Mapfact:Dynamic_AI_Creator
- ArmA2 Terrain Tutorial including Tools Setup in detail
- "Collection of Undocumented/Lesser-Known Features" at FlashPoint 1985.com
Pieter Hintjens on FSM, from the Libero documentation:
- "ETK provides an interactive editor that you use to describe the logic of the program as a FSM. This approach encourages you to think about the complete problem. You describe everything that can happen, and how the program should react. The end- result looks a little like a flow-chart, but has more arrows, and fewer different kinds of boxes. The value of this approach is that you can abstract a complex problem using the restricted semantics of a FSM. In the same way that a While statement is less powerful but more useful than a Goto, a FSM is less powerful but more useful than a structured programming approach for describing complex problems. Leif Svalgaard once said: "the issue is not one of power, but coping with the human difficulty in understanding complex structures".