1. Mailing Lists
  2. Contributors
  3. Re: Proposal: split of some website modules in _backend and _frontend

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Proposal: split of some website modules in _backend and _frontend

Proposal: split of some website modules in _backend and _frontend

Avatar

Re: Proposal: split of some website modules in _backend and _frontend

by
Gianluca Milano
- 07/12/2016 16:43:12
+1

With an option, in the website settings, to install the frontend part.


Gianluca Milano / business integrator +39 335 6010512 /

gianlucamilano
Office: +39 081 19465159 / Fax: +39 081 19465159
Via Trepiccioni, 39 - 80078 Pozzuoli (NA) - ITALY
http://www.gianlucamilano.com



On 7 dic 2016, 16:38 +0100, Leonardo Donelli <learts92@gmail.com>, wrote:
Hello all,

There are some website/ecommerce related modules that would be useful
if split between the "backend" part and the UI/view/frontend part.

Some examples:
* website_recently_viewed_products: (a module I made) it would be
useful to have the "backend" (models, controllers, etc) without
forcing the templates and the popover view currently present in the
module to the users; as they could prefer to implement the view part
in another way (e.g. specific page, or only backend view, ..)
* website_sale_wishlist: same thing. For some use cases it would be
useful to have all the models and controllers (to add/remove things
from the wishlist) but leave the UI implementation free for the user

Therefore I would like to propose a standard to write these kind of
modules: split them in _backend and _frontend (o similar, better
names). Maybe an options to automatically install the frontend
counterpart in the backend settings?

What do you think?

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe

Reference