This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
ivac2:firdef_intro [2015/06/07 19:16] splendor.bouman |
ivac2:firdef_intro [2017/06/01 00:23] (current) ian.beswick |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Introduction ====== | ====== Introduction ====== | ||
| - | This document describes the FIR Definition structure and file formats implemented in IVAC v2.xx and can be used for the development of new FIR Definitions. | + | This document is the starting point for creating IvAc FIR Definitions (aka FIRDEF). It describes the fundamental architecture behind the FIRDEF, including lots of samples provided by the original designers. This document also offers practical guidance to help you make better choices during your design and planning phase and guides you to the other documents in the SDK that contain more detailed information about how to address a specific task. |
| - | Similar to the MTL (Multiplayer Traffic Library), the FIR Definitions are maintained on a central IVAO server(s). On startup IVAC will query the central repository for new or updates to FIR Definitions and other data files used in IVAC. | + | === Every great FIR Definition starts with a great idea === |
| + | Translating that idea into actions requires some planning. Every FIRDEF relies heavily on design, and this design influences much of the XML code you need to write. So before you write any XML code, take the time to explore the possible techniques and technologies available for writing that code. Doing so can save you a lot of time and frustration. | ||
| + | |||
| + | |||
| + | === A Great User Experience Is Rooted in Your Attention to Detail === | ||
| + | It’s essential to keep the user experience uppermost in your mind as you design every aspect of your FIR Definition, from the way you define flight lists, to the colors used in your maps. Discover the guidelines that influence the look and behavior of your FIRDEF, in matters both general and specific. | ||
| + | |||
| + | === All data is centrally stored and updated === | ||
| + | |||
| + | Similar to the MTL (Multiplayer Traffic Library), the FIR Definitions are maintained on a central Terminal 2 server. On startup IVAC2 will query the central repository for new or updates to FIR Definitions and other data files used in IVAC2. | ||
| There are a lot of advantages: | There are a lot of advantages: | ||
| - | * Unordered List Itemcentral management of IVAC data (single source) | + | * central management of IVAC2 data (single source) |
| * users will always have the latest version available | * users will always have the latest version available | ||
| * local divisions are able to provide the latest and correct information | * local divisions are able to provide the latest and correct information | ||
| Line 15: | Line 24: | ||
| The user will be able to select a FIR and ATC position to use from the FIR definition. | The user will be able to select a FIR and ATC position to use from the FIR definition. | ||
| + | |||
| + | === Getting Started === | ||
| + | |||
| + | If you're new to IVAC 2 development start off by reading our [[ivac2:firdef_first_steps|First Steps]] guide. | ||
| ---- | ---- | ||