On Monday, 6 March 2017 13:46:52 UTC+1, Dominique Chabord wrote:
>
> 2017-03-06 13:33 GMT+01:00 E. Boer <[email protected] <javascript:>>: 
>
> > 
> > it's not confusing, the words are right, but the implementation is not. 
> In 
> > my proposal, all the product-fields are in product.product. When you 
> create 
> > a template, you enter a name for the template, add some fields from the 
> > product.product and enter different values to it. That's all. Creating a 
> > product, you select the template and it will add the values to the 
> product. 
>
> So how will it be different from the crrent ? 
>

Current design: You create a new variant, add a template -> you CANNOT 
change e.g. listprice or costprice or add an extra category. Those are all 
defined on the template

Proposed design: You create a new variant, add a template -> you CAN change 
listprice or costprice or whatever.

In the current design a template is *required*, in proposed design a 
template is *optional*. When you want to use templates, you can, but it's 
not necessary. See it as templates in office or other programs. It's a base 
you can start with, but you can change everything. And as I said earlier, 
you can lock fields on the template to not be editable in the variant.

How the implementation will be? I don't know yet. It's just singing around 
in my head. But the very basic idea is:
- All fields in one database table
- Decouple templates from variants, variants do not require a template 
anymore, eventually it should be possible to drop templates and move them 
to a new module
- Variants become products which are used throughout the system (which is 
the case now already)
- Template become like an attribute-set with pre-filled variant (product) 
fields and a boolean to lock the field from editing as attributes 
(one2many?) (you almost get the current situation back)

-- 
You received this message because you are subscribed to the Google Groups 
"tryton" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tryton/0ab2f206-a8c9-44d8-9fa3-446c0df6f0b4%40googlegroups.com.

Reply via email to