[
https://issues.apache.org/jira/browse/OFBIZ-9138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840280#comment-15840280 ]
Nicolas Malin edited comment on OFBIZ-9138 at 1/26/17 7:34 PM:
---------------------------------------------------------------
Hi Deepak sorry for the latency, my concentration move on an other task :)
After sharing with Taher, Julien and Gil on the apachecon eu , we oriented own mind to move all rendering system out framework and keep only the model on the framework.
But if you have some arguments to defend your idea, I'm yours
was (Author: soledad):
Hi Deepak sorry for the latency, my concentration move on an other task :)
After sharing with Taher, Julien and Gil on the apachecon eu , we oriented own mind to move all rendering system out framework and keep only the model on the framework.
But if you have some arguments to defend you idea, I'm yours
> 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)
Locked
