[
https://issues.apache.org/jira/browse/OFBIZ-9138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16144869#comment-16144869
]
Jacques Le Roux commented on OFBIZ-9138:
----------------------------------------
Hi Wei Zhang,
If you are sure it's a bug introduced by this new feature (you need to prove
it), it's better to create a new Jira issue, to mark it as broken by the
current one (OFBIZ-9138) and maybe to notice here (done already if you can
prove it ;)).
Else we will have few follow-ups mixed here. For instance, it's maybe the same
for OFBIZ-9645 (unsure, I was not able to revert just before the switch to
common-theme to check it was working just before) and it's possible that we
will notice some others.
Thanks
> 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
> Fix For: Upcoming Release
>
> Attachments: common-theme-macro.svg, common-theme-screen.svg
>
>
> 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.4.14#64029)
