18.4. RFRS Considerations

The "Feature Branding" section of the RFRS Requirements includes one requirement and four best practices dealing with branding issues.

18.4.1. Do not override product branding (RFRS 3.1.8)

Requirement #1 states:

Product branding and launch points are limited to the Product installation that has included the Eclipse platform. Extension installations may not override the existing product branding by overwriting the existing product configuration. Extension installations may not create shortcuts to launch the platform with an alternative configuration. If an Extension wants to launch the Eclipse platform, they must install their own copy.

To pass this test, show that your feature does not override any of the existing product branding (either by replacing any files or by using the feature startup option).

18.4.2. Branded feature visibility (RFRS 5.3.1.9)

Best Practice #2 states:

At least one branded feature must be visible in the About product_name and About product_name Features dialogs when the Extension has been installed and is enabled. Business Partners should consider providing feature branding for at least one feature and include appropriate documentation for each plug-in referenced by any installed feature. The feature branding content, when provided, must be complete and correct.

Open the Eclipse About dialog and show that your feature icon appears above the pushbuttons. Next, open the About Eclipse SDK Features dialog, select your feature in the list, and show that your feature details are displayed (see Figure 18-15 on page 633 for an example).

18.4.3. Include attribution information (RFRS 5.3.1.10)

Best Practice #3 states:

A Business Partner's features and plug-ins must include appropriate attribution information (company name, version id, name) in the attribution dialogs started using the Feature Details... and Plug-in Details... buttons found on the About product_name dialog.

Show that the about text for your feature (see Figure 18-15 on page 633) includes your company name, the feature version ID, and so on.

18.4.4. about.html file contents (RFRS 5.3.1.11)

Best Practice #4 states:

The plug-in must include an about.html file in the plug-in install directory. At a minimum it must contain:

a. The Eclipse attribution, using the following text:

"Company_Name Software_Name offering includes Eclipse plug-ins that can be installed and used with other Eclipse (x.y)-based offerings."

b. Any attribution required by any dependent technology used by the plug-in (as defined by the provider of that technology)

c. Any other legal information that the provider is mandated to provide

Show that each of your plug-ins includes an about.html file that properly mentions the use of the Eclipse technology (see Figure 18-13 on page 631) as well as any other relevant legal information.

18.4.5. Splash screen restrictions (RFRS 5.3.1.12)

Best Practice #5 states:

The display of a splash image for a feature is permitted only when the software is installed in an evaluation or demonstration mode. The display of the splash image may not interfere with the user or require a special action to disappear. Once a license is purchased, the software must be automatically modified during the application of the license to remove the display of any feature-specific splash images.

For this test, show that your feature either does not have its own splash screen or that it properly deactivates its own splash screen after the evaluation period has expired.