Creating, Migrating, Saving, Opening, and Closing Projects

Managing Projects : Creating, Migrating, Saving, Opening, and Closing Projects

Creating, Migrating, Saving, Opening, and Closing Projects

This section discusses the basic functionality of ePublisher Pro – such as creating, opening, and saving a project. If you are an existing WebWorks Publisher user and need to migrate a legacy project, this section will walk you through the migration process.

Creating a Project

A project in ePublisher Pro is the .wep file that you use to define style behaviors and look and feel. To your project, you can add source documents, groups, style definitions, project customizations, and user files. The goal of any ePublisher Pro project is to deploy a stationery which will be used by the other components of the ePublisher platform.

The following steps will guide you through creating a new project.

To create a new project:

1.	Choose File > New Project.

2.	In the Project name field, type in the name of your project, which will become the name of your project file.

In the Location field, click on the folder icon to browse to the location where you would like to store your ePublisher Pro project. By default, projects are stored in C:\Documents and Settings\username\My Documents\ePublisher Pro Projects, where username is the name you use to sign on to your computer.

4.	If you want to base your project on one of the default ePublisher Pro formats, click on the Use Format radio button, or if you want to base your project on stationery, click on the Use Stationery button.

If you choose to use a default ePublisher Pro format, you will need to select a format from the drop-down list of default formats.

If you chose to use stationery, you will need to browse to the location of the .wsp file.

5.	Click Next.

6.	This next screen allows you to add source documents.

Click the Add button to add source documents.

Click the Finish button if you do not want to add source documents. If you choose to add source documents later, skip steps 7-10. For information on manually adding source documents, see “Adding Source Documents to a Project” on page 6.

7.	Using the Open dialog, browse to the location of the source document.

8.	Select the source documents that will be added.

9.	Click the Open button to add the source documents to your project.

10.	Click the Finish button to create the project.

Migrating Legacy Projects

In ePublisher Pro, the migration tool will allow you to migrate existing WebWorks Publisher projects into ePublisher Pro. When you migrate a legacy project to ePublisher Pro, you are basically updating your existing project so that it is compatible with ePublisher Pro. Although the migration tool will pull style and formatting information from your legacy project into ePublisher Pro, you will still need to work within ePublisher Pro in order to tweak and re-create some of the customizations you have made to your legacy project.

In order to view a WebWorks Publisher project in ePublisher Pro, the legacy project must be migrated. You cannot open a .wwp, .wfp, or .wdt file with ePublisher Pro because each application is based on a different technology; whereas ePublisher Pro is based on XML, legacy WebWorks Publisher projects were based on a proprietary macro language. When you migrate a WebWorks Publisher project, the migration tool is converting your .wwp, .wfp, or .wdt file into XML. Once the project has been coverted into XML, the style information found in the XML file will be pulled over into ePublisher Pro.

Of course, you do not have to migrate your legacy projects if those existing projects function well and produce the output that you want. You can either continue to use the older project to produce output or you can create a new ePublisher Pro project.

Based on market research and experience we have found that creating a new ePublisher Pro project is less time consuming than migrating WWP projects and gives you all of the powerful functionally of the ePublisher Platform with less effort.

Migrating Legacy WebWorks Publisher Projects

When you migrate a WebWorks Publisher project, only certain components of your legacy project will be imported into your ePublisher Pro project. Customized features like breadcrumbs and mini-TOCs will not import into your ePublisher Pro project; however, these features can be easily re-created within ePublisher Pro.

When your legacy project is migrated into ePublisher Pro, it is bringing over most of the information from the Style Designer, except for building blocks, user macros, and char maps. Any information, except for macros, that you have explicitly set for a paragraph, character, table, graphic, or marker style will be migrated into your ePublisher Pro project.

For example, in WebWorks Publisher, if you have defined font properties for a paragraph style in the Style Designer, then all the font properties that you have specified will be migrated into your ePublisher Pro project. If any fields are left blank, then this information will be left blank in the Style Designer in ePublisher Pro.

Items that will be migrated from legacy WebWorks Publisher projects:

Cross-reference formatting

Marker styles

Language encoding

Locale

Items that will not migrate from legacy WebWorks Publisher projects:

Modifications to the navigation pane

Custom .asp files – such as Normal.asp

To migrate an existing WebWorks Publisher Project:

1.	Make a complete backup copy of the WebWorks Publisher project you plan to migrate. Be sure to make backup copies of the project file and the Support directory. It is not necessary to make backup copies of the Temp and Output directories.

In ePublisher Pro, create a new project. When you create a new project, you need to specify a name for the project file (.wep), add any additional source documents that are not already included in the legacy project, and specify a format for the project. If the source documents that you want to add to the project are already associated with your legacy project, do not add any source documents; when your legacy project is migrated, your source documents will be added to the project.

3.	From the main menu, choose File > Migrate > WebWorks Publisher Project.

4.	In the WebWorks Publisher Project field, click on the Open button to browse to the location of your WebWorks Publisher project, the .wwp, .wfp, or .wdt file.

5.	Click the Open button to populate the WebWorks Publisher Project field with the path to the .wwp, .wfp, or .wdt file.

6.	Under the Target Information section, you can choose to merge the legacy project using an existing target or choose to create a new target for the migrated project.

Select Merge into existing target if you would like to use a preexisting target. For example, if you have created target formats within your ePublisher Pro project, these target formats will be available from the Target drop-down list.

Select Create a new target if you would like to create a new target for the migrated project. The target that you create will be based on the format that your original WebWorks Publisher project was based on. For example, if the project that you are migrating is based on Dynamic HTML, then the target that you create will be based on Dynamic HTML.

7.	Under Migration Options, you have four choices: migrate project settings, create new styles, apply style properties and options, and migrate cross-references.

Select Migrate project settings if you would like to migrate project options from the WebWorks Publisher project. The project options are located under Project > Options in your WebWorks Publisher project.

Select Create new styles if you would like to migrate the styles from your legacy project into ePublisher Pro. If this option is not selected, then the styles from your legacy project will not be migrated.

For example, you may choose to deselect this option if you do not wish to import any style information from your legacy project and want to use the style information in your existing ePublisher Pro project instead.

Keep in mind that if you select this option, any style names from the legacy project that match the style names in the ePublisher Pro project will not be migrated over. Only the style names that are unique to the legacy project will migrate to the new project.

Select Apply style properties and options if you would like the style information from your legacy project to override the existing style information in your ePublisher Pro project. For example, if in your ePublisher Pro project you have a Heading 1, and you have Heading 1 in your legacy project, selecting Apply style properties and options will override Heading 1’s existing style information and replace it with the style information from your legacy project.

If this option is not selected, and you are migrating a legacy style that has the same name as an existing style in your ePublisher Pro project, then only the style information for the existing style will be available in the Style Designer.

Select Migrate cross-references if you would like to migrate the cross-reference formatting from your legacy project. This is the formatting information you have specified on the XREFs tab under Project > Mappings in your WebWorks Publisher project.

8.	Click on the Migrate button.

After ePublisher Pro finishes migrating the WebWorks Publisher project file, it will create a new group in the Document Manager that contains the source documents associated with the WebWorks Publisher project file. The name of the group is based on the name of the legacy project, and every project that is imported into ePublisher Pro will have its own group.

Migrated Styles

Once the migration has completed, all of the imported styles from your WebWorks Publisher project will be listed in ePublisher Pro’s Style Designer. In the Style Designer, the WebWorks styles will become the parent styles and the source styles will become the child styles. For example, in your legacy WebWorks Publisher project, if your source style TitleHeading is mapped to the WebWorks style Heading1 then TitleHeading will be the child of Heading1.

However, if in your legacy WebWorks Publisher project, you have a source style mapped to a WebWorks style of the same exact name, then only the WebWorks style will appear in the Style Designer. For example, if your source style Heading2 is mapped to the WebWorks style Heading2 then Heading2 will appear as the parent style, with no child styles.

If you have migrated marker styles, then you will need to assign a marker behavior for each marker style. By default, when marker styles are migrated, their behaviors are unassigned. For example, if you have filename markers in your source document, you will need to assign a filename behavior to the filename marker style.

After Migrating a WebWorks Publisher Project

After you have migrated your WebWorks Publisher project in ePublisher Pro, you should generate output for the project file so that you can see how the styles and formatting information from your legacy project have been transformed in ePublisher Pro.

After you have previewed the output from the migrated project, you can determine what modifications will need to be made so that your Help set will look and function the way you need.

If you had customized macros in your legacy project for features such as breadcrumbs and mini-TOCs, these features will no longer appear in the output, since macros are not imported into ePublisher Pro. Many of the features that previously had to be implemented through the use of macros can now be done directly through the user interface. For example, you no longer have to create custom macros in order to implement breadcrumbs; breadcrumbs can be done directly through the user interface through the Style Designer.

Opening a Project

There are two ways to access a project; you can either open a project directly from the user interface or you can open the project file from its stored location. When you create new projects or open existing projects, ePublisher Pro will open a separate instance of the program for each project. Each project will have its own window, including its own Document Manager, Style Designer, Document Designer, and so forth.

For example, if you already have an opened project, and you decide to create a new project, then ePublisher Pro will open up a new instance of itself for the new project; therefore, you will have two project windows open concurrently.

To open an existing project:

1.	Choose File > Open.

2.	An Open File dialog box will display. Select the project (.wep) file for the project you want to open.

3.	Click Open.

Saving a Project

In case of any unforeseen circumstances, you should periodically save your project to ensure that you do not lose any changes that you have made to your project. By saving your project, you can make certain that the information in your project is stored and will be available for you the next time you open your project.

To save a project:

▪	Choose File > Save.

Exit your project by selecting File > Exit or using the Close button. ePublisher Pro prompts you to save any changes to the project that you have not already saved. Click Yes to save changes, click No to exit the project without saving your changes, or click Cancel to exit the dialog prompt.

Closing a Project

When you finish working with a project, you can close it. As long as you have saved any changes to your project, closing the project will not cause you to lose any project settings. When you close your project, ePublisher Pro will prompt you to save any changes to your project that you have not already saved. Click Yes to save your changes, click No to exit your project without saving your changes, or click Cancel if you do not want to exit your project.

To close a project:

▪	Choose File > Close Project.

In order to insert conditions in your Microsoft Word document, you will need to utilize the WebWorks Transit menu that is installed in the menu of Microsoft Word.

XHTML 1.0 CSS WAI-A