[
https://issues.apache.org/jira/browse/OFBIZ-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659891#action_12659891
]
Jacques Le Roux commented on OFBIZ-2106:
----------------------------------------
I agree that we should has much as possible keep the 2 themes types as closer
as possible. But I'm not as point-blank as Adrian, if there are good reasons to
"split them". I can't see any for now, but I guess that an e-commerce theme,
even a demo theme, could need more sophistication than a backend theme...
> Visual Themes for Ecommerce
> ---------------------------
>
> Key: OFBIZ-2106
> URL: https://issues.apache.org/jira/browse/OFBIZ-2106
> Project: OFBiz
> Issue Type: New Feature
> Components: ecommerce
> Affects Versions: SVN trunk
> Reporter: Bruno Busco
> Attachments: bin.zip, BrowseCategoryCSS.patch,
> EcommerceVisualTheme.patch, EcommerceVisualTheme.patch, screenshot.JPG,
> vt_multiflex.zip
>
>
> Hi,
> in the attached patch a simple implementation of selectable visual themes for
> the ecommerce application.
> I have added the "visualThemeId" to the ProductStore entity. The user can
> select one of the available themes in the EditProductStore screen.
> I have defined the actual ecommerce theme as the default theme that is
> "EC_DEFAULT".
> I have followed for the ecommerce main-decorator screen a pattern similar to
> what done for the back-end.
> One thing that we could think to do (but I would like to hear someone about)
> is to add a "typeId" field or similar to the VisualTheme entity that could be
> used to distinguish between the themes for the back-end and for the ecommerce.
> Right now it is possible to select all of the available themes for bost
> application and this results in a mess if, for example, a theme for ecommerce
> is selected for the back-end and viceversa.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
