A Diumenge, 18 de desembre de 2011 00:08:36, Cédric Krier va escriure:
> On 17/12/11 23:55 +0100, Albert Cervera i Areny wrote:
> > > Also such module (using a product for kit) will not be compatible with
> > > account_stock_* modules.
> >
> > Have taken a look at those modules but can't figure ou
A Diumenge, 18 de desembre de 2011 00:05:25, Cédric Krier va escriure:
> > I don't think I explained correctly. I want users to be able to create
> > and upload their own reports. They can do that by creating a new
> > ir.action.report record, but there's nothing in that record that
> > indicates
On 17/12/11 23:55 +0100, Albert Cervera i Areny wrote:
> > Also such module (using a product for kit) will not be compatible with
> > account_stock_* modules.
>
> Have taken a look at those modules but can't figure out why it should not be
> compatible. If for a given use case, "Kit A" does not h
On 17/12/11 23:36 +0100, Albert Cervera i Areny wrote:
> A Dissabte, 17 de desembre de 2011 18:28:30, Cédric Krier va escriure:
> > On 17/12/11 16:59 +0100, Albert Cervera i Areny wrote:
> > > * Engine *
> > >
> > > We miss an 'engine' field in ir.action.report for both translations and
> > > also
A Dissabte, 17 de desembre de 2011 23:22:25, Cédric Krier va escriure:
> > In some cases it could be a small production as you say but in others it
> > is not. Simply those products must be added to the picking. We've had
> > some cases in which the company wanted to have those products exploded
>
Reviewers: ,
Please review this at http://codereview.tryton.org/211001/
Affected files:
M proteus/config.py
Index: proteus/config.py
===
--- a/proteus/config.py
+++ b/proteus/config.py
@@ -13,9 +13,10 @@
def dump_decimal(s
A Dissabte, 17 de desembre de 2011 18:28:30, Cédric Krier va escriure:
> On 17/12/11 16:59 +0100, Albert Cervera i Areny wrote:
> > * Engine *
> >
> > We miss an 'engine' field in ir.action.report for both translations and
> > also to make jasper_reports first class citizens. In order to use jaspe
On 17/12/11 23:13 +0100, Albert Cervera i Areny wrote:
> If the user had to select at the moment he's introducing the order wether
> that
> line is a kit or not, we're forcing him to know that the code the customer
> has
> given (for example) is a kit or a product. So I think it's clear that it
A Dissabte, 17 de desembre de 2011 21:19:32, Cédric Krier va escriure:
> On 17/12/11 19:33 +0100, Jordi Esteve wrote:
> > En/na Cédric Krier ha escrit:
> > >On 17/12/11 15:52 +0100, Albert Cervera i Areny wrote:
> > >>At the same time, there are some use cases in which a kit can be
> > >>used to in
On 17/12/11 23:02 +0100, lists.jc.mic...@symetrie.com wrote:
> Hi,
>
> Le 17 déc. 2011 à 21:19, Cédric Krier a écrit :
> > I think that in some cases it is a production but a very simple
> > production like just put products together. This kind of production
> > could be managed in background for
Hi,
Le 17 déc. 2011 à 21:19, Cédric Krier a écrit :
> I think that in some cases it is a production but a very simple
> production like just put products together. This kind of production
> could be managed in background for the user if needed.
>
> But in most cases, I think a kit is just a marke
On 17/12/11 19:33 +0100, Jordi Esteve wrote:
> En/na Cédric Krier ha escrit:
> >On 17/12/11 15:52 +0100, Albert Cervera i Areny wrote:
> >>At the same time, there are some use cases in which a kit can be
> >>used to include another product automatically, while the "kit
> >>product" has a meaning as
En/na Cédric Krier ha escrit:
On 17/12/11 15:52 +0100, Albert Cervera i Areny wrote:
At the same time, there are some use cases in which a kit can be used to
include another product automatically, while the "kit product" has a meaning
as a product too.
I think it is wrong to have the
On 17/12/11 16:59 +0100, Albert Cervera i Areny wrote:
> * Engine *
>
> We miss an 'engine' field in ir.action.report for both translations and also
> to
> make jasper_reports first class citizens. In order to use jasper reports we
> must declar the action in the XML but *also* we must add a cl
On 17/12/11 15:52 +0100, Albert Cervera i Areny wrote:
> At the same time, there are some use cases in which a kit can be used to
> include another product automatically, while the "kit product" has a meaning
> as a product too.
I think it is wrong to have the kit meaning a product. In this case
We've got the port of our OpenERP module jasper_reports running on Tryton
already but we want integration to be better and we found some issues I'd like
to discuss:
* Translations *
The first one has been in ir.translation. We inherit the wizard that extracts
the strings from reports but in or
A Divendres, 16 de desembre de 2011 12:47:37, Mathias Behrle va escriure:
> > At the same time it's possible to decide how product price and stock are
> > calculated. The price of the kit can be set in the kit product or
> > calculated as the sum of its components. The stock can be calculated as
>
A Divendres, 16 de desembre de 2011 13:59:25, Cédric Krier va escriure:
> On 16/12/11 08:16 +0100, Albert Cervera i Areny wrote:
> > The idea is adding a new tab in the product (see product-kit.png) to
> > indicate what products the kit contains and what quantity. Then, when
> > the user will creat
18 matches
Mail list logo
