1.2 Define Pre-Processor macro with your project name

OFX_APP_NAME=MyApp

1.3 Create files for your Global Variables

OFX_APP_NAME + Globals.h

1.4 Make your ofApp class a subclass of ofxAppDelegate

By doing so, you are guaranteed to get some callbacks when certain things happen during the app launch.

---

2. ofxApp Functionality Coverage

_ofxApp_ covers a lot of areas, we will break them down in several sections. See table of contents.

2.1 The Configuration File - "ofxAppSettings.json"

_ofxApp_ contains lots of modules whose behaviors can be tweaked and configured. All those configurations are found in a single place, a JSON configuration file in data/configs/ofxAppSettings.json. This file is loaded when _ofxApp_ starts. There are a few main section within the config file:

 App: all configs related to the app
     framerate: int - the framerate at which _ofxApp_ (and your app) will operate
	 numAASamples: int [0..8] - the number of MultiSampling samples the window will be created with
	 showMouse: bool - if mouse cursor should be visible
	 enableMouse: bool - if mouse events should be enabled (useful to disable when TUIO is on to avoid double clicks)
	 maxThreads: int - the max number of CPU threads modules should spawn (should be <= the # of cores in your CPU)
     window
         windowMode: int - [0 .. 11] specifying a window mode for the window to start at. Some common values: [windowed=8, fullOneMonitor=1, fullAllMonitors=0]
         customWidth : int - window width (applies when windowMode is 8 (windowed))
         customHeight : int - window height (applies when windowMode is 8 (windowed))
         customWindowPosition : bool - if true, the default window position will be overriden with the fields below
         customPositionX : int - the x coord of the window position if customWindowPosition is true
         customPositionY : int - the y coord of the window position if customWindowPosition is true
     startupScreenViewport: 4 floats ["x", "y", "w", "h"] - normalized coords of where to constrain the startup loading screen within the window, will be { "x":0.0, "y":0.0, "w":1.0, "h":1.0 } in most cases.
     renderSize: float {"width", "height"} - a target render size value for your convenience. Retrieve it from _ofxApp_ with ofxApp::get().getRenderSize();. It doesn't do anything internally, just for your convenience.
     mullions: { "numX", "numY", "visibleAtStartup"} - define a bezels layout for your videowall. This is useful during development to overlay the bezels on your project, so you can design around them. Press 'M' to toggle them.
     MaintenanceMode: read more about this in 2.8 Maintenance Mode
     ErrorScreen : read more about this in 2.9 Error Handling.
     TimeSampleOfxApp: bool - internal profiler for _ofxApp_ performance - usually set to false.

 StateMachine: this section holds configs for the State Machine that controls the startup phases
     onErrorRetryCount: int - if an error ensues (ie can't download JSON), how many times do we retry before failing?
     onErrorWaitTimeSec: int - if an error ensues, how long do we hold the error message on screen before we retry?

 Fonts: font loading - see section [2.5 Fonts] for more info on this.
 StaticAssets:
     textures: string - the location of your static textures (ie icons) - see section 2.4 Static Textures loading Automation
 RemoteUI: various configurations for ofxRemoteUI.
 TimeMeasurements: various configurations for ofxTimeMeasurements.
 TextureLoader: Params that control texture loading performance. Read more about these in 2.7 Dynamic Texture Loading.
 Logging: configs for logging; read more about those in 2.13 Logging.
 ErrorReporting: setup CMS error reports, read more in 2.10 CMS Error Reporting.
 GoogleAnalytics: configure the GoogleAnalytics client. Readm more in 2.11 Analytics.
 TUIO: configure the TUIO server. If you have a touch overlay in your project, enable it and set the port to make _ofxApp_ forward multitouch events. Read more in 2.14 TUIO - Multitouch Events.
 Downloads: This section configures the http client used throughout _ofxApp_, to download assets and content JSON, to send analytics, etc. Read more about the options in 2.15 Http Downloads.
 Content: All configs related to the content used in your _ofxApp_ project.
     JsonSources: This section holds the Content Sources your app will fetch every time its launched.
     AssetDownloadPolicy: policies regarding when to download assets. Read more in 2.2.4.5 Content Use Policies.
     AssetUsagePolicy: policies regarding when to use assets. Read more in 2.2.4.5 Content Use Policies.
     ObjectUsagePolicy: policies regarding when to use or reject a content object. Read more in 2.2.4.5 Content Use Policies.


Those are the fields that MUST be present in your data/configs/ofxAppSettings.json file for ofxApp to operate. You will notice that _ofxApp_ will automatically terminate if any of those are missing or the JSON is malformed. It will show an error on the logs (and on screen) pointing at the field that is missing, or the line in which there's an error in the JSON syntax. You can always go look at the config files supplied with the examples if you can't figure out how to write yours, the most important lines are documented within the JSON.

This file is meant to be used to simplify your project's settings too. _ofxApp_ relies on two pillars to handle project settings; the most immutable settings (things like window size, fonts to load, logging, etc) usually end up going into this file, as it's mostly read at startup and the values it holds usually not change during the app's execution. Other settings that are more prone to being tweaked as _ofxApp_ runs (like debug booleans, runtime stats, and your own project's parameters) are better off being defined as globals using ofxRemoteUI, as that allows you to easily change their values as the app runs, save and load presets for them, and their state can be saved across launches. Read More about Globals and ofxRemoteUI in 2.6 Globals and Parameter Tweaking.

You can (and should) add any sections you need to this file to hold your settings, and then query the values you need using the following methods

To get a Boolean:

To get an Integer:

To get an Integer:

To get a string:

To get an ofColor:

To check if a value is defined in the JSON:

Also be aware that you can live-edit this file and re-load it while _ofxApp_ is running by pressing R on the keyboard.

2.2 ofxApp and Content

One of the goals of _ofxApp_ is to abstract content ingestion and sync with a remote CMS for you, lets see how it handles it.

2.2.1 How does ofxApp Handle Content?

_ofxApp_ allows you to go from a JSON sitting on an API endpoint, to a filtered