I begin by configuring the application name as well as the name (1) of the standalone executable file (2) on disk. I don't need to put .exe or .app at the end of the standalone name. I just use the same name that I plan on using when I build your standalone executable.

I now set the version number for the application (1). I can also specify the stage of development that the application is at (2).

Next I move down and set the application data folder that the application will store information in (1). I make sure and check the User checkbox (2). I need to configure this path and check this box if a) the application plans on working with data in the user application data folder or b) I plan on using preferences on Windows.

I provide a name for the preference file on OS X (3). I just need to provide the file name as the framework will take care of storing the file in the proper location on OS X.

I provide a relative path for the Windows preferences file (4). The path is relative to the Windows user application data folder. Notice that I am storing the Windows preferences file inside of the folder I am using for this applications user data (5).

Note: This particular application does not have a splash stack. If you would like more information on displaying a splash stack when your application launches please see the splash stack lesson in the manual.

I save the changes I have made by clicking the Save Settings button in the plugin. This saves the application stack to disk. The application stack is where all configuration information is stored.