OFBiz › OFBiz - Commits

svn commit: r1814177 - /ofbiz/tools/wiki-files/themes/README.md.html

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

1 message

jleroux@apache.org

svn commit: r1814177 - /ofbiz/tools/wiki-files/themes/README.md.html

Author: jleroux
Date: Fri Nov 3 12:56:26 2017
New Revision: 1814177

URL: http://svn.apache.org/viewvc?rev=1814177&view=rev
Log:
Puts right wiki file in themes sub folder

Modified:
ofbiz/tools/wiki-files/themes/README.md.html

Modified: ofbiz/tools/wiki-files/themes/README.md.html
URL: http://svn.apache.org/viewvc/ofbiz/tools/wiki-files/themes/README.md.html?rev=1814177&r1=1814176&r2=1814177&view=diff
==============================================================================
--- ofbiz/tools/wiki-files/themes/README.md.html (original)
+++ ofbiz/tools/wiki-files/themes/README.md.html Fri Nov 3 12:56:26 2017
@@ -6,43 +6,281 @@
<meta name="generator" content="pandoc" />
<title></title>
<style type="text/css">code{white-space: pre;}</style>
+ <style type="text/css">
+div.sourceCode { overflow-x: auto; }
+table.sourceCode, tr.sourceCode, td.lineNumbers, td.sourceCode {
+ margin: 0; padding: 0; vertical-align: baseline; border: none; }
+table.sourceCode { width: 100%; line-height: 100%; }
+td.lineNumbers { text-align: right; padding-right: 4px; padding-left: 4px; color: #aaaaaa; border-right: 1px solid #aaaaaa; }
+td.sourceCode { padding-left: 5px; }
+code > span.kw { color: #007020; font-weight: bold; } /* Keyword */
+code > span.dt { color: #902000; } /* DataType */
+code > span.dv { color: #40a070; } /* DecVal */
+code > span.bn { color: #40a070; } /* BaseN */
+code > span.fl { color: #40a070; } /* Float */
+code > span.ch { color: #4070a0; } /* Char */
+code > span.st { color: #4070a0; } /* String */
+code > span.co { color: #60a0b0; font-style: italic; } /* Comment */
+code > span.ot { color: #007020; } /* Other */
+code > span.al { color: #ff0000; font-weight: bold; } /* Alert */
+code > span.fu { color: #06287e; } /* Function */
+code > span.er { color: #ff0000; font-weight: bold; } /* Error */
+code > span.wa { color: #60a0b0; font-weight: bold; font-style: italic; } /* Warning */
+code > span.cn { color: #880000; } /* Constant */
+code > span.sc { color: #4070a0; } /* SpecialChar */
+code > span.vs { color: #4070a0; } /* VerbatimString */
+code > span.ss { color: #bb6688; } /* SpecialString */
+code > span.im { } /* Import */
+code > span.va { color: #19177c; } /* Variable */
+code > span.cf { color: #007020; font-weight: bold; } /* ControlFlow */
+code > span.op { color: #666666; } /* Operator */
+code > span.bu { } /* BuiltIn */
+code > span.ex { } /* Extension */
+code > span.pp { color: #bc7a00; } /* Preprocessor */
+code > span.at { color: #7d9029; } /* Attribute */
+code > span.do { color: #ba2121; font-style: italic; } /* Documentation */
+code > span.an { color: #60a0b0; font-weight: bold; font-style: italic; } /* Annotation */
+code > span.cv { color: #60a0b0; font-weight: bold; font-style: italic; } /* CommentVar */
+code > span.in { color: #60a0b0; font-weight: bold; font-style: italic; } /* Information */
+ </style>
</head>
<body>
-Three instances of OFBiz run on the OFBiz demo VM2 at https://ofbiz-vm2.apache.org.
-<ul>
-<li>trunk: the trunk version</li>
-<li>stable: the last stable version (currently 16.11)</li>
-<li>old: the previous stable version (currently 13.07)</li>
-</ul>
-This is the second instance of VM we use hence the 2 in its domain name. The root of https://ofbiz-vm2.apache.org is the so called bigfiles directory which is actually at /home/ofbizDemo/big-files
-We own 3 Apache sub domains
+
+<h1 id="apache-ofbiz-themes">Apache OFBizÂ® Themes</h1>
+<h1 id="what-is-a-theme">What is a theme</h1>
+A Theme is an ofbiz component that defines all elements necessary to render all information generated by the screen engine through an embedded technology. Currently themes presents in Apache OFBiz use html5/jquery/css to do that.
+To realize this, a theme can define some properties that can be necessary, can define its own ftl macro to render the different modelScreen elements and can define its own screen decorator to prepare the final user screen structure for the technology used by the theme. # How to define it A theme is a standard component, present in the directory themes or plugins with a file definition present on widget/Theme.xml and support the <a href="http://ofbiz.apache.org/dtds/widget-theme.xsd">widget-theme.xsd</a>
+To offer the possibility for end users to select the theme through the "Select Theme Screen", the theme need to load the entity VisualTheme and one or more entries related to this theme.
+<h1 id="structure-of-theme.xml">Structure of Theme.xml</h1>
+The theme definition file help OFBiz to know what specific rendering the Theme want to use. It's composed by two definition elements and four optional blocks
+<h2 id="main-definition">Main definition</h2>
+The First mandatory element is one or several visualThemeId related to the theme Defined like that
+<div class="sourceCode"><pre class="sourceCode xml"><code class="sourceCode xml"> <visual-themes>
+ <visual-theme id="MY_THEME"/>
+ </visual-themes></code></pre></div>
+You need to define in the database an entry in VisualTheme Entity for each visual-theme id defined.
+<div class="sourceCode"><pre class="sourceCode xml"><code class="sourceCode xml"><entity-engine-xml>
+ <VisualTheme visualThemeId="MY_THEME" visualThemeSetId="BACKOFFICE" description="My theme - Example (based on flatgrey)"/>
+</entity-engine-xml></code></pre></div>
+<blockquote>
+Note: a theme component can load one or more visual theme id. Usually only one is present.
+</blockquote>
+The second important (but not mandatory) element is implements
+<div class="sourceCode"><pre class="sourceCode xml"><code class="sourceCode xml"> <extends location="component://common-theme/widget/Theme.xml"/></code></pre></div>
+This element indicates that your theme copies from the extend theme all information not present in its file definition. If this element isn't present in your theme, you will need to define all information present in common-theme to be sure that OFBiz misses nothing for a correct run. Otherwise some functionnalities can be broken... >Note: It's highly recommended to extend the common-theme to be sure that your theme works correctly and to surcharge only what you need.
+The four following blocks are optionnal if you define an extends theme ## General properties This block contains all properties that the screen engine can use to prepare the rendering and that the theme can implement
+<div class="sourceCode"><pre class="sourceCode xml"><code class="sourceCode xml"> <widget-properties>
+ <default-view-size value="20"/>
+ <autocompleter
+ default-view-size="10"
+ default-min-lenght="2"
+ default-delay="300"
+ display-return-field="true"/>
+ <lookup
+ position="topleft"
+ width="640"
+ height="500"/>
+ <layered-modal
+ width="800"
+ height="600"/>
+ </widget-properties></code></pre></div>
+<h2 id="themes-specific-properties">Theme's specific properties</h2>
+This block contains all properties specific to this theme. In general these are some properties present on ftl template, that are initialized by the theme and can be surchaged by another theme through the extends elements.
+<div class="sourceCode"><pre class="sourceCode xml"><code class="sourceCode xml"> <property name="jgrowlPosition" value="center" type="String"/>
+ <property name="jgrowlWidth" value="800" type="Integer"/>
+ <property name="jgrowlHeight" value="" type="Integer"/>
+ <property name="jgrowlSpeed" value="100" type="Integer"/></code></pre></div>
+<h2 id="ftl-macro-library">Ftl macro library</h2>
+This block defines for each technology implemented by the screen engine where it can find the macro library for each model (Screen, Form, Tree, Menu)
+<div class="sourceCode"><pre class="sourceCode xml"><code class="sourceCode xml"> <templates>
+ <template name="screen" type="html" content-type="UTF-8" encoding="none" encoder="html" compress="false">
+ <template-file widget="screen" location="component://common-theme/template/macro/HtmlScreenMacroLibrary.ftl"/>
+ <template-file widget="form" location="component://common-theme/template/macro/HtmlFormMacroLibrary.ftl"/>
+ <template-file widget="tree" location="component://common-theme/template/macro/HtmlTreeMacroLibrary.ftl"/>
+ <template-file widget="menu" location="component://common-theme/template/macro/HtmlMenuMacroLibrary.ftl"/>
+ </template>
+ ...
+ </templates></code></pre></div>
+<blockquote>
+Note: If you want surcharge some macros, you can just create the desired macros and import the others from common-theme (at the top of file) like that : <code><#include "component://common-theme/template/macro/HtmlFormMacroLibrary.ftl"/></code>
+</blockquote>
+<h2 id="screen-library">Screen library</h2>
+This block defines where OFBiz can find all official screens definitions in framework/common
+Normally, you don't need to change this file except if you need to define a default screen style that doesn't exist OOTB. If you need to extend an existing one, you have to do it in the theme directory.
+To define a new default screen style, you have to add it in this file, and point to the screen decorator in common-theme to define your default screen style as the default one.
+<div class="sourceCode"><pre class="sourceCode xml"><code class="sourceCode xml"> <common-screens>
+ <structural-decorator default-location="component://common-theme/widget/CommonScreens.xml">
+ <screen name="GlobalDecorator"/>
+ ...
+ </structural-decorator>
+ <embed-decorator default-location="component://common-theme/widget/CommonScreens.xml">
+ <screen name="FindScreenDecorator"/>
+ </embed-decorator>
+ <general-screen default-location="component://common-theme/widget/CommonScreens.xml">
+ <screen name="geoChart"/>
+ ...
+ </general-screen>
+ </common-screens></code></pre></div>
+Screens are separated in three types : * structural-decorator : contains all decorators that organise the screens structures * embed-decorator : decorator used only on sub screens * general-screen : list all generic inter applications screens # The common-theme This is the root theme that contains all information to ensure a good basic theme for OFBiz. Currently it keeps all old themes system for backward compatibility with ftl template managed by the entity VisualThemeResource
+<h1 id="create-your-own-theme">Create your own theme</h1>
+As a theme is a component, you can create a new theme like a plugin.
+After creating a component, you can add the two minimal information : * Theme.xml file in plugins/my-theme/widget/ with minimal information :
+<div class="sourceCode"><pre class="sourceCode xml"><code class="sourceCode xml"><theme name="my-theme"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/widget-theme.xsd">
+ <visual-themes>
+ <visual-theme id="MY_THEME" display-name="My Theme"/>
+ </visual-themes>
+</theme></code></pre></div>
<ul>
-<li>https://demo-trunk.ofbiz.apache.org</li>
-<li>https://demo-stable.ofbiz.apache.org</li>
-<li>https://demo-old.ofbiz.apache.org</li>
+<li>your data file to add your visual theme in plugins/my-theme/data/
+<div class="sourceCode"><pre class="sourceCode xml"><code class="sourceCode xml"><entity-engine-xml>
+<VisualTheme visualThemeId="MY_THEME" visualThemeSetId="BACKOFFICE"/>
+</entity-engine-xml></code></pre></div>
+The presence of VisualTheme entity helps to indicate which theme is available in your instance, specially helpful for tenant installations.</li>
</ul>
-All demos use a Let's Encrypt certificate. There is currently a bug which prevents Let's Encrypt certificate to renew every 3 months. So we need to do it by hand and you need to have a root access for that. This is how: <a href="http://markmail.org/message/7c3rxrqkn4kkm6dm" class="uri">http://markmail.org/message/7c3rxrqkn4kkm6dm</a>
-The Puppet configuration is at https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/ofbiz-vm2.apache.org.yaml
+To display your theme in OFBiz theme library, you can complete the information on each visual theme like
+<pre><code><theme name="my-theme"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/widget-theme.xsd">
+ <visual-themes>
+ <visual-theme id="MY_THEME" display-name="My Theme">
+ <description>My new funny theme under nice tecnno</description>
+ <screenshot location="/mytheme/screenshot1.png"/>
+ <screenshot location="/mytheme/screenshot2.png"/>
+ </visual-theme>
+ </visual-themes>
+</theme></code></pre>
<blockquote>
-Note: Only run the ofbiz demos using the 'ofbizDemo' user, never run as root.
+Note: display-name and description support the flexibleStringExpander syntax
</blockquote>
-<pre><code>To do this sudo to the ofbizDemo user:
-
-sudo -s -u ofbizDemo -H
+<h2 id="extends-common-theme">extends common-theme</h2>
+This is a first step to understand how the theme system works. With your new theme, you can try to surchage different elements. To start, extends the common-theme :
+<div class="sourceCode"><pre class="sourceCode xml"><code class="sourceCode xml"><theme name="my-theme"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/widget-theme.xsd">
+ <visual-themes>
+ <visual-theme id="MY_THEME" display-name="My Theme">
+ <description>My new funny theme under nice tecnno</description>
+ <screenshot location="/mytheme/screenshot1.png"/>
+ </visual-theme>
+ </visual-themes>
+ <extends location="component://common-theme/widget/Theme.xml"/>
+</theme></code></pre></div>
+Now your theme should be operational, but without particularity.
+You can surcharge a ftl macro, to do this create your own ftl macro file in plugins/my-theme/templates/macro/HtmlFormMacroLibrary.ftl with
+<pre class="ftl"><code><#include "component://common-theme/template/macro/HtmlFormMacroLibrary.ftl"/>

-sudo uses OTP (One Time Password), so you not only need to be registered as a sudoer (ask Infra) but also to use a tool like Donkey on Ubuntu (jleroux: I use that) to generate the OTP
-Then you can start/stop as required.
+<#macro renderDisplayField type imageLocation idName description title class alert inPlaceEditorUrl="" inPlaceEditorParams="">
+ <#if description?has_content>
+ *###*${description?replace("\n", " ")}**<#t/>
+ <#else>
+ *#&nbsp;#*<#t/>
+ </#if>
+</#macro></code></pre>
+Now indicate to your theme that you want use this library
+<div class="sourceCode"><pre class="sourceCode xml"><code class="sourceCode xml"><theme name="my-theme"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/widget-theme.xsd">
+ <visual-themes>
+ <visual-theme id="MY_THEME" display-name="My Theme">
+ <description>My new funny theme under nice tecnno</description>
+ <screenshot location="/mytheme/screenshot1.png"/>
+ </visual-theme>
+ </visual-themes>
+ <extends location="component://common-theme/widget/Theme.xml"/>
+ <templates>
+ <template name="screen" type="html" content-type="UTF-8" encoding="none" encoder="html" compress="false">
+ <template-file widget="form" location="component://my-theme/template/macro/HtmlFormMacroLibrary.ftl"/>
+ </template>
+ </templates>
+</theme></code></pre></div>
+and check the result when you select your theme. The result isn't really interesting but it's to understand how it works.
+<h2 id="create-from-scratch">create from scratch</h2>
+TODO
+<h1 id="backware-compatibility-with-ofbiz-16.11-and-above">Backware compatibility with OFBiz 16.11 and above</h1>
+<h2 id="how-themes-worked-before">How themes worked before</h2>
+Before the theme management by model definition, all configurations have been present in the database through entity VisualTheme and VisualThemeRessource. These ressources were loaded in a layoutProperties variable and used directly by decorator screens and ftl templates.
+<h2 id="now-with-the-common-theme">Now with the common-theme</h2>
+All this logic is still present in the common-theme template to keep backward compatibility, but the VisualThemeRessource is now useless and properties have been migrated to the Theme definition in the part theme-properties ### Example with BlueLight The blue light theme has been these properties in VisualThemeRessource :
+<div class="sourceCode"><pre class="sourceCode xml"><code class="sourceCode xml"> <VisualTheme visualThemeId="BLUELIGHT" visualThemeSetId="BACKOFFICE" description="BlueLight Theme: breadcrumbs, drop-down menus and rounded corners"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_NAME" resourceValue="BLUELIGHT" sequenceId="01"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_IMAGE_URL" resourceValue="/images/ofbiz_logo.gif" sequenceId="01"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_SHORTCUT_ICON" resourceValue="/images/ofbiz.ico" sequenceId="01"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_SCREENSHOT" resourceValue="/bluelight/screenshot.jpg" sequenceId="01"/>

-To check if the demos are being run as the ofbizDemo user:
+ 
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_STYLESHEET" resourceValue="/bluelight/style.css" sequenceId="01"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HELPSTYLESHEET" resourceValue="/bluelight/help.css" sequenceId="01"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_DOCBOOKSTYLESHEET" resourceValue="/bluelight/webapp/bluelight/docbook.css" sequenceId="01"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_STYLESHEET" resourceValue="/common/js/jquery/plugins/asmselect/jquery.asmselect-1.0.4a-beta.css" sequenceId="02"/>

-ps aux | grep ofbizDemo
+ 
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/common/js/jquery/jquery-1.11.0.min.js" sequenceId="01"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/common/js/jquery/jquery-migrate-1.2.1.js" sequenceId="02"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/common/js/jquery/ui/js/jquery-ui-1.10.3.min.js" sequenceId="03"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/common/js/jquery/plugins/asmselect/jquery.asmselect-1.0.4a-beta.js" sequenceId="05"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/common/js/jquery/plugins/datetimepicker/jquery-ui-timepicker-addon.min-1.4.3.js" sequenceId="07"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/common/js/jquery/plugins/fjTimer/jquerytimer-min.js" sequenceId="09"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/common/js/jquery/plugins/jquery.maskedinput-1.3.1.min.js" sequenceId="10"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/common/js/jquery/plugins/jeditable/jquery.jeditable.js" sequenceId="11"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/common/js/jquery/plugins/validate/jquery.validate.min.js" sequenceId="12"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/images/OpenLayers-2.13.1.js" sequenceId="13"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/common/js/util/OfbizUtil.js" sequenceId="15"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/common/js/util/fieldlookup.js" sequenceId="16"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/common/js/plugins/date/date.format-1.2.3-min.js" sequenceId="17"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/common/js/plugins/date/date.timezone-min.js" sequenceId="18"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/common/js/util/miscAjaxFunctions.js" sequenceId="19"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/common/js/util/selectMultipleRelatedValues.js" sequenceId="20"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/common/js/util/util.js" sequenceId="21"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/common/js/plugins/date/FromThruDateCheck.js" sequenceId="22"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/bluelight/dropdown.js" sequenceId="30"/>

-The first column on the left tell you the username the demo is
-being run as - it should say ofbizDemo (UID) or 9997 (GID) !
-
-Type 'exit' to exit the ofbizDemo user and return to your normal user.</code></pre>
-Also note that the demos are usually updated and started/stopped automatically using the check-svn-update.sh script in this directory, it is run by an ofbiz cron job every 24 hours at 3 AM. You should therefore only need to start/stop manually if there is a problem.
-If you want to restart only a single instance you can respectively use
-trunk-manual-nicely.sh stable-manual-nicely.sh old-manual-nicely.sh
+ 
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_HDR_TMPLT_LOC" resourceValue="component://bluelight/template/Header.ftl" sequenceId="01"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_FTR_TMPLT_LOC" resourceValue="component://bluelight/template/Footer.ftl" sequenceId="01"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_NAV_OPEN_TMPLT" resourceValue="component://bluelight/template/AppBarOpen.ftl" sequenceId="01"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_NAV_CLOSE_TMPLT" resourceValue="component://bluelight/template/AppBarClose.ftl" sequenceId="01"/>
+ <VisualThemeResource visualThemeId="BLUELIGHT" resourceTypeEnumId="VT_MSG_TMPLT_LOC" resourceValue="component://bluelight/template/Messages.ftl" sequenceId="01"/></code></pre></div>
+Now it's just
+<div class="sourceCode"><pre class="sourceCode xml"><code class="sourceCode xml"> <VisualTheme visualThemeId="BLUELIGHT" visualThemeSetId="BACKOFFICE"/></code></pre></div>
+And on theme definition
+<div class="sourceCode"><pre class="sourceCode xml"><code class="sourceCode xml"> <theme-properties>
+ 
+ <property name="VT_HDR_JAVASCRIPT['add']" value="/bluelight/dropdown.js" sequenceId="30"/>
+ 
+ <property name="VT_STYLESHEET['add']" value="/bluelight/style.css"/>
+ <property name="VT_HELPSTYLESHEET['add']" value="/bluelight/help.css"/>
+ <property name="VT_DOCBOOKSTYLESHEET['add']" value="/bluelight/webapp/bluelight/docbook.css"/>
+ 
+ <property name="VT_HDR_TMPLT_LOC" value="component://bluelight/template/Header.ftl"/>
+ <property name="VT_FTR_TMPLT_LOC" value="component://bluelight/template/Footer.ftl"/>
+ <property name="VT_NAV_OPEN_TMPLT" value="component://bluelight/template/AppBarOpen.ftl"/>
+ <property name="VT_NAV_CLOSE_TMPLT" value="component://bluelight/template/AppBarClose.ftl"/>
+ <property name="VT_MSG_TMPLT_LOC" value="component://bluelight/template/Messages.ftl"/>
+ </theme-properties></code></pre></div>
+Values with /images/... have been moved to the common-theme that bluelight extends, the theme definition keeps only what the theme adds to the extended theme.
+<blockquote>
+Note property name supports the FlexibleMapAccessor syntax, so you can continue to populate a list (VT_STYLESHEET['add']), reset a list (VT_STYLESHEET[]) or add an element on the top list (VT_STYLESHEET[+0]) because some time the order libraries loading is important
+</blockquote>
+<h3 id="migrate-you-own-theme">Migrate you own theme</h3>
+Easily, create you Theme.xml and move your VisualThemeResource in theme-properties like in the BlueLight example above. Maybe you will need to update your template because the modelTheme return ressources not always as list. So : <code><property name="VT_HDR_TMPLT_LOC" value="component://bluelight/template/Header.ftl"/></code> -> return a String with <code>component://bluelight/template/Header.ftl</code> <code><property name="VT_STYLESHEET['add'] value="..."</code> -> return a List<String>
</body>
</html>