...
The Powered by frevvo™ logo can be customized via the frevvo.poweredby.markup branding parameter. If this branding parameter is the empty string no logo will appear on any form. The logo can still be turned of on any given form via the Show Logo form property.Refer to Installation Tasks for the steps to repackage frevvo.war after parameters in web.xml have been edited
Hiding Palette Controls
...
OEM partners can use the context parameter, frevvo.oem.branding.class to name a css class that will be placed onto the body of the ui the UI pages (form designer, etc.). Set the context parameter, frevvo.oem.branding.class to oem in the web.xml file. The web.xml file is located in <frevvo-home>\WEB-INF\web.xml after the <frevvo-home>\tomcat\webapps\frevvo.war file is unzipped to a temporary directory. Refer to Installation Tasks for the steps to unzip and repackage frevvo.war after parameters in web.xml and any other files have been edited.
| Code Block |
|---|
<context-param>
<param-name>frevvo.oem.branding.class</param-name>
<param-value>oem</param-value>
<description>This css class will be placed onto the body of the frevvo ui pages. OEMs can then create their own private CSS file(s) with rules based on the body having the oem branding class in
order to customize the frevvo app.</description>
</context-param> |
The oem-branding-.css file is located in <\tmp>\css-XXXXX, where XXXXX=version number\oem. Rezip the frevvo.war file after editing is completed. See Installation Tasks for more information.
CSS file(s) with rules based on the body having the oem branding class can be created in order to customize the application.
If you do not wish to create css files from scratch, the CSS file(s) with rules based on the body having the oem branding class can be created in order to customize the application. If you do not wish to create css files from scratch, the default oem-branding.css file is a good place to start.. Any aspect of this file can be changed. The context parameter “frevvo.oem.branding.class” must be set to “oem". Unzip the frevvo.war file to a temporary directoryplace to start..Any aspect of this file can be changed. The oem-branding-.css file is located in <\tmp>\css-XXXXX, where XXXXX=version number\themes\oem. Rezip the frevvo.war file after editing is completed. See Installation Tasks for more information.
OEM partners are responsible for creating the CSS file(s) and putting them into the WAR file. To do this, edit /css<\tmp>\css-XXXXX\/form.pac.css (in the exploded WAR) and add one or more lines like the following: @IMPORT url(“oem_branding.css”); where oem_branding.css is the name of the css file containing the specific oem rules. XXXXX=the version number.set (in web.xml)
.