Master table of contents In most situations, you will have one TOC that you use for a particular output (target). In that case, you simply associate the appropriate TOC with the target. If you have multiple TOCs that you want to include in the same project or output target, the TOC that you associate with the project or target serves as the "master" TOC. In your master TOC, you have the option of creating links to the other TOC that you want to include in the output. If you do not select a TOC, Flare will use the first one in the project (if there is more than one). If you have specified a master TOC at the project level and another at a target level, the TOC at the target will take precedence.
Click in the field and select a table of contents (TOC) from your project to use as the "master." If you click the Edit button, the selected TOC opens in the TOC Editor.
Master page layout After you create a page layout and configure its frames and settings as necessary, you need to associate the page layout with the appropriate content. In most cases, you will probably want to associate different page layouts with various entries in your "outline TOC" (so that different page layouts can be used for different parts or "chapters" in a manual). Otherwise, you would associate a single "master" page layout with an entire target or project; in that case, the same page layout will be applied to all topics in that target or project. Whenever you associate a page layout with a TOC entry, you must first create a chapter break in order to do so.
Click in the field and select a page layout from your project to use as the "master." If you click the Edit button, the selected page layout opens in the Page Layout Editor.
Master stylesheet When you want to use styles in your content, the style sheet needs to be made available for the content in question. In Flare, you can associate style sheets with a single topic
You can associate a master style sheet with an entire project. The styles will therefore be used for the content in the project. If you have specified a master style sheet at the project level and another at a target level, the style sheet at the target will take precedence. If you are using different master style sheets for different targets, the style sheet associated with the primary target determines what you see in the XML Editor. You can set the target-level master style sheet on the General tab of the Target Editor.
Click in the field and select a style sheet from your project to use as the "master." If you click the Edit button, the selected style sheet opens in the Stylesheet Editor.
-
Bind project If you have a Flare project open, you can "bind" (i.e., connect) it to a source control application.
Binding a project to source control allows you to take advantage of the many multi-author features available through source control integration. This includes automatic check-in, check-out; instant messaging to request other users to check in files; viewing differences between source control and local copies of the project files; and more.
- Unbind project You can remove the connection between the Flare project and the source control application.
- Check in files When you are finished editing files, you can check them in to source control. Checking in a file overwrites the old copy of the file in the source control database with the new one from your local machine. So even if others will not be working on that file, it is a good idea to periodically check in files so that you have a backup in source control.
- Check out files When you need to work on any of the Flare project files, you can check them out. Checking out files means to copy the latest source control files to your local Flare project and remove the "Read Only" designation from them so that you can edit the files. A red check mark
is displayed next to each file that is checked out. - Get latest version After you bind a Flare project to a source control application, you can get the latest version of any of the source control files. When you do this, you are copying the most current files stored in the source control application to your local Flare project without necessarily checking out the files. This means that the "Read Only" designation will remain associated with the files until you check them out.
- Undo check out If you have files checked out from source control but do not want them checked out anymore, you can use the "Undo Check Out" option instead of checking in the files.
- View differences One of the benefits of Flare's integrated source control is that you can view the history and differences for a particular file.
- View history One of the benefits of Flare's integrated source control is that you can view the history for a particular file, including who checked in the file and when it was checked in. You can also view differences between different versions of the file and roll back to an older version if necessary.
- Request check in If you discover that another user already has that file checked out, you can automatically send a request to that user to check in the file. This is a completely automated process involving instant messaging or email. Not only are the messages sent to the appropriate individuals automatically, but the mechanisms for checking in and checking out the necessary files are built in to those messages. This means that you and the other authors on your team do not need to hunt down the correct files manually.
Note: If you are working with a source control application other than those directly supported in Flare (i.e., Microsoft Visual SourceSafe, Microsoft Team Foundation Server, Apache Subversion), you can use the Microsoft Source Code Control API (SCC API) to integrate that application with your Flare project.
