Planning and Installing ePublisher : Upgrading from Previous Versions : Upgrading Implementations with Advanced Customizations : Upgrading Advanced Customizations of WebWorks Reverb Skin
Upgrading Advanced Customizations of WebWorks Reverb Skin
The WebWorks Reverb output format is highly customizable and chances are you may have made advanced customizations to this format. If you are upgrading from a prior release, then you will want to understand what files are most likely to be customized and how this is affected when you change the Skin Target Setting.
If you have or plan to customize any of the WebWorks Reverb skins, then most likely you will have to modify one or more of the following files.
Table 5: Commonly Customized Reverb Files
The display area or items affected by this file
Content panel styling only. Includes the styling of the MiniTOC, RelatedTopics, Social Buttons.
Styling of TOC, Index, Toolbar, and Breadcrumbs. All icons used in the skin.png sprite file are managed here. Styling of content that appears above the Toolbar, such as the company information.
Styling of the search results page.
skin.png (derived from skin.Fireworks.png)
PNG file with alpha channel that stores all of the Reverb icons.
Used to manage the button placement in the toolbar. Also manages the TOC/Index/Search panel title for the Corporate skin.
Manages basic structure of the entry-point file generated from the connect.asp template file.
When working with alternate skins, you need to be aware of which files are most likely affected as a result of changing the skin type. If you have Advanced Customizations in any of these files, then you need to re-examine the diffs of these files after you switch the skin type. Most likely you will see significant changes. Here are some basic steps you can follow to make sure you translate those changes to the new skin properly.
Basic steps for setting an alternate skin type when Advanced customizations are present
1. Check your Advanced Customizations for files listed in “Commonly Customized Reverb Files”.
2. Make sure any of these commonly customized files are implemented as Target Overrides as opposed to Format Overrides. Setting an alternate skin type will create an implicit target override that will have priority over any format overrides of the same name.
3. Before changing the skin type you will need to record any existing file differences. On the Advanced menu click Manage Target Customizations. Now use the procedure discussed in “Managing Format/Target Overrides” to record these file differences. These file differences will be used later after the skin type has been changed.
4. On the Target menu, click Target Settings.
5. In the WebWorks Reverb category, select the right column of the Skin entry to display the file picker button.
6. Click the file picker button to bring up an Open file dialog which will display a list of skin plugin files. Each skin plugin file is identifiable by a .weplugin extension.
7. Browse to the plugin file that you wish to use and double-click it to set the skin to that value.
8. At this point, you need to consider either removing your existing customizations and then re-implementing them using the information from your previously recorded file differences. Or managing the differences directly by comparing the differences using the procedure discussed in “Managing Format/Target Overrides”. Either method will work.