X

Proactive insights, news and tips from Oracle Fusion Middleware Support. Learn Oracle from Oracle.

Oracle Forms 12c - Using customcolorscheme To Create A Customized Runtime Color Palette

Alexandra David
Principal Technical Support Engineer

Oracle Forms 12c includes many new features compared to its predecessor (11gR2).  One of those new features is the ability to create your own runtime color scheme.

By default, all Forms versions 10.1.2 and newer include the following nine color schemes: Blue, Khaki, Olive, Purple, Red, Teal, Titanium, BLAF, SWAN. These color schemes are not modifiable.

The colors of a chosen color scheme are consumed by Forms objects that do not have a color (background or foreground) selected at design-time or runtime (e.g. in PL/SQL).  
In other words, in the Builder's Property Palette, the Background or Foreground color value would appear as <UNSPECIFIED>.  
When set to <UNSPECIFIED>, the color scheme colors will be used to paint the object.  The exact color chosen for each object is hard coded within the scheme and this cannot be changed.
To use one of the provided color schemes, set the applet parameter "colorScheme" to the desired value from the list provided earlier.

It is now possible(12c) to create custom color schemes.  The desired values of the custom color scheme are set in the Forms Font and Icons Mapping configuration (Registry.dat).  
This is accessible in Fusion Middleware Control.  An example named “sample” is provided in the installation, but not likely appropriate for a production deployment.  
To enable this example, simply set the Web Configuration parameter customColorScheme=sample

For more examples and detailed steps on how to create and use a customColorScheme, consult:

  • Note Oracle Forms 12c - Using customcolorscheme To Create A Customized Runtime Color Palette (Doc ID 2367517.1)
  • the New features white paper

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.