...
You will need to install a client library in order to use the API. Please contact us for assistance.
Branding
We have create a new OEM Partners can use the context parameter called , “frevvo.oem.branding.class” that OEMs can be set (in web.xml) to name a css class. This css class will be placed onto the body of the frevvo ui ui pages (form designer, etc.). OEMs can then create their own private a CSS file(s) with rules based on the body having the oem branding class in order to customize the frevvo app app.
In addition to the context parameter being placed into web.xml, OEMs (or frevvo acting for the OEM) would be responsible for creating the CSS file(s) and putting them into the WAR file. To do this, the OEMs would also have to edit /css/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.
...
The frevvo.war file contains a web.xml with branding parameters. In the frevvo-tomcat bundle, frevvo.war is located in: <frevvo-home>\frevvo\tomcat\webapps - when the war file is unzipped, the web.xml file will be found in <frevvo-home>\WEB-INF. Refer to Installation Tasks for the steps to repackage frevvo.war after parameters in web.xml have been editied.
...
| Parameter | Description | Default |
|---|---|---|
| frevvo.home.url | Home page for the Company Logo link | ${context.path} |
| frevvo.logo.url | URL to the Company Logo image | ${context.path}/images/bright/TransparentLogo-NoBeta.png |
| frevvo.help.url | URL to the Help page | ${context.path}${servlet.path}/static/help/designer |
| frevvo.docs.url | URL to the Documentation | http://docs.frevvo.com/docs/index.php/V4_Main_Page |
| frevvo.forum.url | URL to the Forum | http://http://forum.frevvo.com/forum/ |
| frevvo.blog.url | URL to the blog | http://blog.frevvo.com |
| frevvo.product.name | The Product Name | Live Forms |
| frevvo.copyright | Product Copyright One-Liner | Copyright 2006-2012 frevvo Inc. All rights reserved. |
| frevvo.license.url | URL to License Agreement | ${context.path}${servlet.path}/static/termsDL |
| frevvo.contact.menu | Show Contact menu item | true |
| frevvo.downloads.menu | Show Downloads menu item | true |
| frevvo.gallery.menu | Show Gallery (Examples) menu item | true |
| frevvo.templates.menu | Show Templates menu item | true |
| frevvo.contact.email | Contact Us email address | mailto:info@frevvo.com |
| frevvo.css.url | Custom Stylesheet URL | |
| frevvo.poweredby.markup | Logo in form footer when the Logo property set | Powered by Live Forms™ |
| frevvo.page.title | HTML title prefix for all pages | frevvo |
| frevvo.menu.bar | Prefix in page title of any Live Forms page | true |
Branding External Urls
Notice that several of the parameters use Url templates. For example, frevvo.help.url references a help file named designer.xsl that is part of frevvo.war and is located in the directory <frevvo-home>\WEB-INF\xsl\main\help after the war file has been unzipped . You may wish to bundle up a replacement help file and store your replacement file in that same directory. In that case you will keep the templates ${context.path}${servlet.path}/static that are part of the default path and append your own help file name. It can be an html file, myAppHelp.html. Or if your help is an external file you can replace the entire default value ${context.path}${servlet.path}/static/help/designer with a Url such has http://mycompany/myapp/help.html. Refer to Installation Tasks for the steps to repackage frevvo.war after parameters in designer.xsl have been editied.
...