Get the Software Developers Kit

Question: How Can I Get the FalconView™ Software Developers Kit?

Answer: Get it here.

Background

The FalconView Software Developers Kit (SDK) is a collection of documents and sample code to aid developers in writing tools that either run inside of FalconView or use FalconView or its components in their tools.

Note: Possible Issue Reading Compiled HTML (CHM) Documents

Some machines may have a problem opening compiled HTML ("chm" extension) files like those found in the SDK. It appears that a service patch on Windows XP, Vista, and Windows Server 2003, has defaulted to blocking the reading of "chm" files that originated on other computers. Do the following to open these files:

  1. Make certain the "chm" file resides on a local directory (e.g., your desktop).
  2. Right-click the file.
  3. Select "Properties" in the pop-up menu.
  4. Uncheck "Read Only" if it is checked.
  5. Press the "Unblock" button, and then press "OK."

More details are available here:  http://blog.crowe.co.nz/archive/2007/04/13/719.aspx.

The SDK

Since getting access to the developer website is a lengthy process, we have attached the final FalconView 4.0 and 4.1, and beta 4.2 and 4.2.1 SDKs here:

  • FVW400_final_SDK.zip Download The Final Version of the 4.0.x Software Developers Kit
  • FVW410_final_SDK.zip Download The Final Version of the 4.1.x Software Developers Kit
  • FVW420_R1_v3_SDK.zip Download The "first" final version of the 4.2.x Software Developers Kit. Extensive changes were made to the DAFIF and Map Server interface control documents. Read the interface change notices or the "Version Changes" topic in the interface control document. The DAFIF sample code was updated.
  • FVW421_beta6_SDK.zip Download The beta version of the 4.2.1 Software Developers Kit. Updated the FalconView ICD (PFPS421FalconViewICD.chm) with the addition of ILayer5::BringFvToForeground?. Updated the FalconView Data Services ICD (FalconViewDataServicesICD.chm) with the addition of IFvDataSource::Connect.

The SDK does not contain the source code to FalconView or the FalconView executable so you will still need access to the developers web site at Eglin or at least a working version of FalconView. See below.

Contents

Interface Control Documents (ICDs)

  • FalconView ICD - This document describes all of the COM Programmers interfaces to FalconView
    • IMap - allows you to get map data and control its display.
    • ILayer - allows you to draw geo-referenced points, lines, and areas on the map and to get "callbacks" when the user manipulates your objects.
    • ILayerEditor - allows you to hook into FalconView as a seamless editor of your layer.
    • IGPS - allows you to hook into the MovingMap functionality of FalconView.
    • ThreatFeed - allows interaction with threat overlay data.
  • Other File Format ICDs
    • Drawing File ICD - provides details on the database field formats and data of drawing files.
    • CHUM File ICD
    • DAFIF Database ICD - interfaces to the DAFIF DLL (non-COM). The DAFIF DLL provides functions to extract DAFIF information without accessing the Database directly.
    • Threat Database ICD
    • Threat File Format and Parametrics ICD
    • Shape File Preference File ICD
    • Point Export ICD (you should avoid Point Export unless you really need it)
    • External Application Usage ICD - how to provide access to a maximum of 20 "external" applications through the use of buttons added to a "Custom Toolbar" and menu options added to the Tools menu.
    • Overlay Element ICD

Interface Change Notifications (ICNs)

These documents detail the changes between ICD versions.

Sample Code

Samples in Visual C++ and VB that show how to exercise the interfaces.

Miscellaneous Documents

  • SkyView ICD - describes COM interfaces of interest in SkyView 3.3 and NG.
  • Overlay and Tool Startup Exclusion - lists the overlays and tools that you can exclude from startup (e.g., so ground users would not see options for MTRs).
  • NITF TRE SQL Script - a sample script file to provide a decoder for custom, tagged record extensions (TREs) to National Imagery Transmission Format (NITF) files. This file is self-documented. Be certain you read the comments at the beginning before you modify it.
  • Threat Feed IDL - the interface definition language (IDL) for threat feeds.
  • Terrain Mask ICD - describes the tactical graphics and general masking interface.
  • FalconView Data Services ICD

Where to Download Beta PFPS Versions

The official SDK and Beta Versions of PFPS are available at the  ESC Mission Planning Central website. This is also where you can get SDKs for other parts of PFPS such as the RouteServer.

Mission Planning Central Access

The next question is how to get access to Mission Planning Central.

The first step in obtaining access to the PFPS Tools on Mission Planning Central ( https://portal.mission-planning.org) is to obtain an account on one of these three service portals:

The PFPS Platform Manager cannot help in getting one of these accounts. Please see your chain of command or your contract’s Government point of contact.

The second step is to go to Mission Planning Central ( https://portal.mission-planning.org) and log in, using one of the three types of accounts above. The process is different depending on which portal you use.

If you are using either the Air Force Portal or Army Knowledge Online, going to request to  https://portal.mission-planning.org will redirect you to the service portal sign-in page, and once you sign in, you will be directed back to  https://portal.mission-planning.org. If you use NKO, you must FIRST log on to NKO, and join the NKO Mission Planning Community. That community’s page has a link to  https://portal.mission-planning.org, and you will already be authenticated when you get there.

Once you are logged in to  https://portal.mission-planning.org, request to join the Mission Planning Community by selecting the “About MPC” link and requesting access to the mission planning community by selecting the link under “How to access MPC information”. This will send an email to the MPC help desk requesting membership in the Mission Planning Community.

The third step is to go to  https://portal.mission-planning.org/mpc-sites/SoftwareRepository/pfps/default.aspx and request access to the particular PFPS tools that you require. You may submit the request form electronically. You must have your commander, government point of contact (a civil servant or military member) or contract representative (a civil servant or military member) information so we may verify the request. This is critical. The most common reason for rejection of an application is that the applicant did not provide valid contact information for the commander, government point of contact, or contract point of contact. Contractors must bear in mind that this person cannot be an employee of their own company, but rather is an employee of the Federal Government. The person listed may be asked to describe the program being worked on or provide other justification for the access before it is granted.

You are here: GetTheSdk > FVDev > WebHome

Attachments