Open topic with navigation

Importing a Project from Source Control

The first step in developing a project after you launch Flare is to start a project. You can start a project in one of several ways:

• Create a new project from scratch
• Import a RoboHelp project
• Import an HTML Help project
• Create a project by importing Microsoft Word documents
• Create a project by importing Adobe FrameMaker documents
• Import a Flare project from source control
• Open an existing project

This topic focuses on importing a Flare project from source control. You might use this method, for example, if you are working on a multi-author project and another member of the team has placed the Flare project in a source control tool such as Microsoft Visual SourceSafe or Microsoft Team Foundation Server. For more information, see About Source Control and Multi-Authoring.

Following are the steps for importing a project from source control.

How to import a project from source control

1. Select File>Import Project>Import From Source Control. The Import Project From Source Control Wizard opens.
2. Follow one of these sets of steps, depending on the source control application being used:

   If using Visual SourceSafe:

   1. Click Visual Source Safe.
   2. Next to the Database field, click Browse.
   3. Find the appropriate SourceSafe database and double-click the INI file.

   If using Team Foundation Server:

   1. Click Team Foundation Server.
   2. In the Server field, enter the name of the computer or the IP address of the server.
   3. In the Team Project field, click the Browse button. Then locate and select the team project on the server.

   If using another source control application:

   1. Click Source Code Control Plug-in.
   2. In the Provider field, select the appropriate source control program from the list.
   3. (Optional) You might be able to click the Advanced button to enter more options. This depends on whether the provider has enabled advanced options; if not, the button is disabled. The advanced options available to you are different for each provider.
3. Click Next.

4. Next to the Project file field, click Browse.

5. Find and click on the Flare project file (FLPRJ) that you want to import.
6. Click OK.
7. Click Next.
8. In the Project name field, the name of the project being imported is displayed. It is recommended that you leave the name as it is, especially if you are working with other authors on the project. However, you can enter a different project name if you want.
9. In the Project folder field, either accept the default location for the new project or click to browse for and select a folder.
10. (Optional) Select Check Out Project Files if you want to immediately check out all files from the source control project so that you can edit them.

    Note: Keep in mind that others might already have some files checked out.

11. Click Finish. The project is imported and loaded into Flare.

WHAT'S NEXT?

You can perform any of the other source control tasks, such as checking in and checking out files. See About Source Control and Multi-Authoring.

You can also move on to any of the other basic steps:

• Step 2 - Add "Stuff" to the Project

• Step 3 - Make It Look Good

• Step 4 - Develop One or More Outputs

• Step 5 - Build the Final Output

• Step 6 - Distribute the Output to End Users

Note: You do not necessarily need to follow all of the above steps (and their substeps) in the exact order given. For example, as you add topics to a project (Step 2), you may want to start applying styles and formatting to them right away (Step 3), before adding other "stuff" to the project, such as a glossary (Step 2). However, the above sequence probably makes the most overall logical sense. For example, you must start a project before adding "stuff" (topics, content, cross-references, etc.) to it. And of course, you cannot distribute output to your end users (Step 6) until you build the final output (Step 5).

See Also

Open topic with navigation