Buttons and Sections of the Project Organizer

Toggles between showing or hiding the folders in the Project Organizer.

Splits the Project Organizer into two halves. When you select a folder on the left side, the folders and files within it are shown on the right side. Also, you can select multiple files on the right side, which lets you perform the same action on all of them at the same time.

Expands all of the folders so that you can see all of the files under each one.

Collapses all of the folders so that you can no longer see all of the files under each one.

Lets you show or hide the small squares next to each folder and file, which are used to show colors representing condition tags that have been applied. See Applying Conditions to Content.

Moves up one folder in the hierarchy. This button becomes enabled if you use the Split View button and select a file or folder on the right side of the split view.

Creates a new custom folder, which you can use to organize your files.

Displays the color of condition tags that are associated with the file (if any). Condition tags are used to determine specific content or files to be included in some targets but not in others. See Conditions.

• Git and Subversion This indicates that the file has been modified. You can commit the file when you are ready. If your project is bound to Subversion, you can commit the file when you are ready (if you are the user who has modified it, or if you have stolen the lock on the file from another user).
• Perforce Helix Core This indicates that the file has been checked out from source control. You can submit the file when you are ready (if you are the user who has checked it out).
• TFS and VSS This indicates that the file has been checked out from source control. You can check in the file when you are ready (if you are the user who has checked it out).

See Checking In, Committing, and Submitting Source Control Files and Checking Out Source Control Files.

This indicates that you have a file in your project but have not yet added it to the integrated source control application. This might occur, for example, if you create a new topic and do not add the file to source control during the topic creation process. To resolve this, simply right-click on the file and select Source Control > Add.

See Adding Files to Source Control.

This indicates that the file is added to source control but is not currently checked out, which means that it contains a "Read Only" designation in its properties. In order to edit the file, you must check it out from source control.

You will see this icon if your project is bound to Microsoft Team Foundation Server or Perforce Helix Core.

See Checking Out Source Control Files.

This indicates that another user has locked the file. You will often see this icon in conjunction with the icon, indicating that another user is both using the file and has locked the file. You can make changes to this file even if another user has locked it.

If your project is bound to Subversion and you need to commit the file in while another user is working on it, you can steal their lock. To do this, right-click on the file and select Source Control > Lock. In the Lock dialog, select Steal the lock, then click Lock.

You will see this icon if your project is bound to Microsoft Team Foundation Server, Perforce Helix Core, or Subversion.

See Locking Files.

This indicates that you have locked the file. You will often see this icon in conjunction with the icon, indicating that you have both locked and modified the file. Other users can make changes to this file even if you have locked it.

If your project is bound to Subversion, other users can steal your lock.

If you are using Team Foundation Server, you can lock a file when you check it out.

You will see this icon if your project is bound to Microsoft Team Foundation Server, or Perforce Helix Core, or Subversion.

See Locking Files.

• Perforce Helix Core and Subversion This indicates that the file is currently being modified by another user. You will often see this icon in conjunction with the icon, indicating that another user is both using the file and has locked the file.
• TFS This indicates that the file is currently checked out to another user. You can send a request to the user, asking that person to check in the file so that you can check it out.

You will see this icon if your project is bound to Microsoft Team Foundation Server, Perforce Helix Core, or Subversion.

This indicates that the file is not current (i.e., the local copy of the file is older than the source control copy). This might happen if another user checks out the file, makes changes to it, and checks it back in to source control. If this occurs, you can check the file out or get the latest version of the file from source control.

You will see this icon if your project is bound to Microsoft Team Foundation Server, Perforce Helix Core, or Subversion.

See Checking Out Source Control Files or Updating or Getting the Latest Version of Source Control Files.

This indicates that a file has been renamed, but not modified in any other way. If you make any additional changes to the file, such as editing the text or adding a condition tag, the renamed icon is replaced by a icon.

You will see this icon if your project is bound to Subversion.

This indicates that the file is deleted from source control, but you still have a copy of the file on your local machine. If necessary, you can add the file to source control.

You will see this icon if your project is bound to Microsoft Team Foundation Server.

See Adding Files to Source Control and Deleting Files from Source Control.

Holds various types of files for different features. These include the following:

• Alias Files
• Creating Auto-Indexes
• Auto Suggestion
• Browse Sequences
• File Tags
• Header Files
• Creating Index Links
• Language Skins
• Meta Tags
• Relationship Tables
• Search Filter Sets
• Synonyms

Holds the condition tag sets that you add to the project. You can expand the condition tag sets to see the conditions within them, and you can drag those conditions to content in the XML Editor. See Conditions.

Holds the publishing destinations that you add to the project. See Creating Destinations.

Holds the glossaries that you add to the project. See Glossaries.

Holds export files that you add to the project. These are used to export your Flare project (or parts of it) to another location. See Adding an Export Project File.

Holds import files that you add to the project. See Importing.

Holds reports that you create in order to track information in your project. See Adding Report Files.

Holds the skins and skin components that you add to the project. See Skins.

Holds the targets that you add to the project. You can add as many targets to a project as you need. In addition to regular targets, you can add batch targets, which are used to generate multiple targets in one batch. See Step 4: Developing Targets.

Holds the tables of contents that you add to the project. See Tables of Contents.

Holds the variable sets that you add to the project. You can expand the variable sets to see the variables within them, and you can drag those variables to content in the XML Editor. See Variables.