[
https://issues.apache.org/jira/browse/OFBIZ-9138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732136#comment-15732136
]
Nicolas Malin commented on OFBIZ-9138:
--------------------------------------
I continue the work with :
* with move macro ftl on common-theme
* move uneeded properties from widget.properties commonWidget.properties
present on common-theme to keep on first properties file only property related
to widget model and not widget rendering
* review some code on FindAutocompleteOptions.groovy and MacroFormRenderer.java
to move rendering property use to FtlMacro or decorator screen
POC available on https://github.com/nmalin/ApacheOFBiz/tree/common-theme
> Create a common theme
> ---------------------
>
> Key: OFBIZ-9138
> URL: https://issues.apache.org/jira/browse/OFBIZ-9138
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
> Reporter: Nicolas Malin
> Assignee: Nicolas Malin
>
> A first task to UI Improvement would be create a common that receive the
> existent code.
> The benefice would be have a framework/common who list all screens that
> available for theme surcharge, so without technology information (css/html or
> something like that)
> Different task to do :
> * move all ftl template from framework/common to themes/common
> * move framework/images to themes/common (this directory contains unlogical
> element for theme but will be manage at a second time)
> * move default macro ftl template from framework/widget to themes/common
> After the realization on this task, all current themes call theme/common for
> html rendering instead of framework/common, framework/images and
> framework/widget. Just pave the way for the next
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
