Message Threads | The Odoo Community Association

Re: l10n-estonia status and proposing myself as PSC

What next steps do I need to take?

by "Alexey Pelykh" <alexey.pelykh@corphub.eu> - 09:25 - 23 Jun 2022

Re: l10n-estonia status and proposing myself as PSC

What next steps do I need to take?

On Mon, Jun 13, 2022 at 11:02 AM Enric Tobella Alomar <etobella@creublanca.es> wrote:

+1 From my side, it seems the Project is not used, so any contributor who wants to be a team member is good from my side.

Enric Tobella Alomar
Desarrollo
Av. J. V. Foix 63

08034 Barcelona

Tlf. 932 522 522 (Ext. 1621)

creublanca.es

From: "Alexey Pelykh" <alexey.pelykh@corphub.eu>
To: "Contributors" <contributors@odoo-community.org>
Date: Sat, 11 Jun 2022 05:22:34 -0000
Subject: l10n-estonia status and proposing myself as PSC

Dear all,

It seems that PSC for l10n-estonia is inactive entirely as it's been quite over a year since I've requested attention to https://github.com/OCA/l10n-estonia/pull/4 (https://github.com/OCA/l10n-estonia/pull/4#issuecomment-839124178).

Also, I'd like to apply for l10n-estonia PSC.

Kind regards,
Alexey

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

Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.

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

by Alexey Pelykh - 08:56 - 23 Jun 2022

Re: Translations done by a webservice

On 22/06/2022 11:12, Pedro M. Baeza (Tecnativa) wrote:

> Hi all,

> 

> Do you know any Odoo open source module that is able to translate user 

> generated content (product descriptions for example) in an integrated way?

> 

Hi,

I don't know a ready to use odoo addon for this but what about 
argos-translate ?

You can use it directly in your code as a python module,

Use it offline, set up your own server, use a public server using api, ...

Depending if you want use it offline from addon code(pure python, 
privacy, silent machine translation), or from the frontend (js using api 
(private or public), end user live double check)

For example it seems very fast and easy to just add an automated action 
to update translations with this tool.

https://github.com/argosopentech/argos-translate

You can try it online here :

https://libretranslate.com

https://github.com/LibreTranslate/LibreTranslate

-- 
Simon Maillard
simon@ogesta.fr

Parce que sinon ça rend la discussion incompréhensible.
 > Pourquoi ça ?
 >> Je préfère répondre en dessous.
 >>> Que faites-vous à la place ?
 >>>> Non.
 >>>>> Vous n'aimez pas répondre au-dessus ?

by simon - 02:56 - 22 Jun 2022

Re: Translations done by a webservice

Hi Pedro and community,

We looked for different possibilities with already existing Odoo modules. Finally, our last tests were oriented towards services like https://weglot.com

Have a nice day !

Bruno Joliveau - Président

NUMIGI SOLUTIONS INC.

bruno.joliveau@numigi.com

(514) 317-7944

Longueuil, Québec, Canada

http://www.numigi.com/

Le mer. 22 juin 2022 à 05:12, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :

Hi all,

Do you know any Odoo open source module that is able to translate user generated content (product descriptions for example) in an integrated way?

Thanks in advance.

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

by Bruno Joliveau - 02:25 - 22 Jun 2022

Translations done by a webservice

Hi all,

Do you know any Odoo open source module that is able to translate user generated content (product descriptions for example) in an integrated way?

Thanks in advance.

by Pedro M. Baeza - 11:11 - 22 Jun 2022

Re: New repos proposal

Hi Simone,

Alright, you've convinced me and it seems others as well! Let's just go 
with "web-api" and "pwa-builder" then and do our best on the README's to 
make clear how they differ from "connector" and "rest-framework". It's 
good enough and frankly I am super interested in the code so I hope 
you'll be able to push it soon!

-Tom

by Tom Blauwendraat - 05:50 - 21 Jun 2022

Re: New repos proposal

+1

Le mar. 21 juin 2022 à 11:37, Simone Orsi <simahawk@gmail.com> a écrit :

Hi,

On Thu, Jun 16, 2022 at 11:37 AM Tom Blauwendraat <tom@sunflowerweb.nl> wrote:

To make these scope statements more concrete:

1. web-api : collect modules to expose or deal with web api (eg: custom management for routes and endpoints, generic tools to handle calls to ext api, etc).

This description as a scope statement IMO should be better, it should be crystal clear why this is not part of "OCA/rest-framework". As it stands now, this text does not teach or convince me why it should be separate. Could we come up with a better text?

It's not about REST, it's about any kind of WEB related API that you might want to expose or call.
Examples:
* inbound - an endpoint to accept a file upload or to create a record
* outbound - configuration of an external web service to call + reusable tools or api to make this happen

In any case, the text I wrote in my first email was not intended to be the readme of the repo, was just to have an idea ;)

2. pwa-builder : collect modules that allow to create and manage standalone PWA apps. As many of you know I split the core of the shopfloor wms app some time ago and this core now allows you to create - potentially - any kind of PWA app w/ its backend (based on rest services) and frontend tools (VueJS based). This core is now in OCA/wms but that's not really the right place. The name is not adequate too (shopfloor_base) so I think I'm going to rename it to pwa_core or pwa_builder or something similar.

For this the reason to separate is much more clear. OCA/wms is definitely the wrong place, as you want to be able to use this framework for "any app".

Three questions though:

1. Why "builder" ? Does this actually build apps for you, or is it just a framework. A builder sounds to me as a tool that allows you to generate an app from building blocks. If a framework, "pwa", "pwa-core", "pwa-engine" or "pwa-framework" sounds more appropriate to me.

To be honest I don't care that much about this name, I'm open for suggestions ;) "builder" sounded in line with "mis-builder" and generic enough to not require another repo for additional modules. I mean, if we call it pwa-core (which I like more) then I won't put any other module there which is not for the "core" and then we'll need a new one like pwa-contribs (or any similar name). I don't dislike this option.
Hence, if everybody prefers `-framework` or another option, I can change its name. No problem.

2. Is this limited to be used as a PWA, or can it also just be used as a replacement for the Odoo web portal? In my view, a "PWA" is something that has a service worker and can be "installed" to your system. Otherwise something like "web-app-engine" would be more appropriate (analogous to reporting-engine: housing an alternative OCA reporting engine)
Potentially you can build any kind of PWA on top of it. Up to you. The backend is separated from the front, see below.
Keeping PWA in the name sounds a bit more in line with what you'll end up with: an installable app. If you use it also as a website is up to you but you don't need it for creating a website only.

3. Considering that it's based on VueJS, wouldn't a better name be "web-app-vuejs" or "pwa-vuejs", in order to separate it from efforts by any future OCA member companies who prefer Angular or React as their tool of choice, and want to open source their alternative engine?
No, it's not for VueJS only. There's a backend part and a frontend part. Today the front is based on VueJS but if you want to rewrite the front w/ ReactJS, you could.
The backend part - as far as possible - is conceived to provide configuration, routes and specific endpoints to retrieve core info for the app.

Hope is more clear now :)

Bests

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

--
Simone Orsi

Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

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

--

Raphaël Reverdy

Mobile +33 6 38 02 03 93

Fixe +33 4 82 53 84 60

by Raphaël Reverdy - 04:41 - 21 Jun 2022

Re: New repos proposal

Hi,

On Thu, Jun 16, 2022 at 11:37 AM Tom Blauwendraat <tom@sunflowerweb.nl> wrote:

To make these scope statements more concrete:

1. web-api : collect modules to expose or deal with web api (eg: custom management for routes and endpoints, generic tools to handle calls to ext api, etc).

This description as a scope statement IMO should be better, it should be crystal clear why this is not part of "OCA/rest-framework". As it stands now, this text does not teach or convince me why it should be separate. Could we come up with a better text?

It's not about REST, it's about any kind of WEB related API that you might want to expose or call.

Examples:

* inbound - an endpoint to accept a file upload or to create a record

* outbound - configuration of an external web service to call + reusable tools or api to make this happen

In any case, the text I wrote in my first email was not intended to be the readme of the repo, was just to have an idea ;)

2. pwa-builder : collect modules that allow to create and manage standalone PWA apps. As many of you know I split the core of the shopfloor wms app some time ago and this core now allows you to create - potentially - any kind of PWA app w/ its backend (based on rest services) and frontend tools (VueJS based). This core is now in OCA/wms but that's not really the right place. The name is not adequate too (shopfloor_base) so I think I'm going to rename it to pwa_core or pwa_builder or something similar.

For this the reason to separate is much more clear. OCA/wms is definitely the wrong place, as you want to be able to use this framework for "any app".

Three questions though:

1. Why "builder" ? Does this actually build apps for you, or is it just a framework. A builder sounds to me as a tool that allows you to generate an app from building blocks. If a framework, "pwa", "pwa-core", "pwa-engine" or "pwa-framework" sounds more appropriate to me.

To be honest I don't care that much about this name, I'm open for suggestions ;) "builder" sounded in line with "mis-builder" and generic enough to not require another repo for additional modules. I mean, if we call it pwa-core (which I like more) then I won't put any other module there which is not for the "core" and then we'll need a new one like pwa-contribs (or any similar name). I don't dislike this option.

Hence, if everybody prefers `-framework` or another option, I can change its name. No problem.

2. Is this limited to be used as a PWA, or can it also just be used as a replacement for the Odoo web portal? In my view, a "PWA" is something that has a service worker and can be "installed" to your system. Otherwise something like "web-app-engine" would be more appropriate (analogous to reporting-engine: housing an alternative OCA reporting engine)

Potentially you can build any kind of PWA on top of it. Up to you. The backend is separated from the front, see below.

Keeping PWA in the name sounds a bit more in line with what you'll end up with: an installable app. If you use it also as a website is up to you but you don't need it for creating a website only.

3. Considering that it's based on VueJS, wouldn't a better name be "web-app-vuejs" or "pwa-vuejs", in order to separate it from efforts by any future OCA member companies who prefer Angular or React as their tool of choice, and want to open source their alternative engine?

No, it's not for VueJS only. There's a backend part and a frontend part. Today the front is based on VueJS but if you want to rewrite the front w/ ReactJS, you could.

The backend part - as far as possible - is conceived to provide configuration, routes and specific endpoints to retrieve core info for the app.

Hope is more clear now :)

Bests

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

--

Simone Orsi

Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

by Simone Orsi - 11:36 - 21 Jun 2022

Re: Creation of Wallet repository

Could you just init it as I don't have write access ?

With 14.0 branch first.

Thanks

On Tue, Jun 21, 2022 at 11:21 AM Roussel, Denis <denis.roussel@acsone.eu> wrote:

Great, thanks !

On Tue, Jun 21, 2022 at 11:17 AM Simone Orsi <simahawk@gmail.com> wrote:
Ciao,

done https://github.com/OCA/wallet

Cheers

On Fri, Jun 17, 2022 at 2:52 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
Hi @Board,

We had a meeting with all people interested in (Grap/Akretion/CoopITEasy/Acsone).

So, we agree that we need it.

Could you create a 'wallet' one ?

Many thanks

On Wed, Jun 8, 2022 at 2:54 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
Of course, we have done it in 8/10/14, the current version is there:

https://github.com/acsone/acsone-addons/tree/14.0/account_wallet

On Wed, Jun 8, 2022 at 2:46 PM Sylvain LE GAL <sylvain.legal@grap.coop> wrote:
Hi Denis,

Thanks for the information.

FYI, we worked with coop it easy on a implementation of wallet for account & pos.

the current code for V12 is available here :
- https://github.com/coopiteasy/addons/tree/12.0/account_customer_wallet
- https://github.com/coopiteasy/addons/tree/12.0/pos_customer_wallet

Could be great to benchmark various implementation to choose the better one (or a mix of feature from various implementations)

Could you send the url of the repo with your current work ?

kind regards.

CC : Carmen / Catherine from coop it easy.

Sylvain LE GAL - Twitter
GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)
Site Web | FramaSphere | Facebook
3 Grande rue des Feuillants, 69001 Lyon
Standard : (+33) 09.72.32.33.17
Service Informatique : (+33) 09.73.79.64.40
Astreinte Informatique : (+33) 06.81.85.61.43
Member of the OCA (Odoo Community Association)
Web Site | Twitter

Le mer. 8 juin 2022 à 14:36, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
Hi all,

As some people are requesting wallet functionalities (aka Financial Reserve), I request the creation of 'wallet' repository under the umbrella of Accounting PSC.

As soon as it is created, we are going to propose PR's with our current work.

So, see you there!

Many thanks.

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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

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

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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

--
Simone Orsi

Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

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

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium

Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium

Zone industrielle 22 | L-8287 Kehlen | Luxembourg

by Denis Roussel - 11:26 - 21 Jun 2022

Re: Creation of Wallet repository

Great, thanks !

On Tue, Jun 21, 2022 at 11:17 AM Simone Orsi <simahawk@gmail.com> wrote:

Ciao,

done https://github.com/OCA/wallet

Cheers

On Fri, Jun 17, 2022 at 2:52 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
Hi @Board,

We had a meeting with all people interested in (Grap/Akretion/CoopITEasy/Acsone).

So, we agree that we need it.

Could you create a 'wallet' one ?

Many thanks

On Wed, Jun 8, 2022 at 2:54 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
Of course, we have done it in 8/10/14, the current version is there:

https://github.com/acsone/acsone-addons/tree/14.0/account_wallet

On Wed, Jun 8, 2022 at 2:46 PM Sylvain LE GAL <sylvain.legal@grap.coop> wrote:
Hi Denis,

Thanks for the information.

FYI, we worked with coop it easy on a implementation of wallet for account & pos.

the current code for V12 is available here :
- https://github.com/coopiteasy/addons/tree/12.0/account_customer_wallet
- https://github.com/coopiteasy/addons/tree/12.0/pos_customer_wallet

Could be great to benchmark various implementation to choose the better one (or a mix of feature from various implementations)

Could you send the url of the repo with your current work ?

kind regards.

CC : Carmen / Catherine from coop it easy.

Sylvain LE GAL - Twitter
GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)
Site Web | FramaSphere | Facebook
3 Grande rue des Feuillants, 69001 Lyon
Standard : (+33) 09.72.32.33.17
Service Informatique : (+33) 09.73.79.64.40
Astreinte Informatique : (+33) 06.81.85.61.43
Member of the OCA (Odoo Community Association)
Web Site | Twitter

Le mer. 8 juin 2022 à 14:36, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
Hi all,

As some people are requesting wallet functionalities (aka Financial Reserve), I request the creation of 'wallet' repository under the umbrella of Accounting PSC.

As soon as it is created, we are going to propose PR's with our current work.

So, see you there!

Many thanks.

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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

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

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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

--
Simone Orsi

Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

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

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium

Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium

Zone industrielle 22 | L-8287 Kehlen | Luxembourg

by Denis Roussel - 11:26 - 21 Jun 2022

Re: Creation of Wallet repository

Ciao,

done https://github.com/OCA/wallet

Cheers

On Fri, Jun 17, 2022 at 2:52 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:

Hi @Board,

We had a meeting with all people interested in (Grap/Akretion/CoopITEasy/Acsone).

So, we agree that we need it.

Could you create a 'wallet' one ?

Many thanks

On Wed, Jun 8, 2022 at 2:54 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
Of course, we have done it in 8/10/14, the current version is there:

https://github.com/acsone/acsone-addons/tree/14.0/account_wallet

On Wed, Jun 8, 2022 at 2:46 PM Sylvain LE GAL <sylvain.legal@grap.coop> wrote:
Hi Denis,

Thanks for the information.

FYI, we worked with coop it easy on a implementation of wallet for account & pos.

the current code for V12 is available here :
- https://github.com/coopiteasy/addons/tree/12.0/account_customer_wallet
- https://github.com/coopiteasy/addons/tree/12.0/pos_customer_wallet

Could be great to benchmark various implementation to choose the better one (or a mix of feature from various implementations)

Could you send the url of the repo with your current work ?

kind regards.

CC : Carmen / Catherine from coop it easy.

Sylvain LE GAL - Twitter
GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)
Site Web | FramaSphere | Facebook
3 Grande rue des Feuillants, 69001 Lyon
Standard : (+33) 09.72.32.33.17
Service Informatique : (+33) 09.73.79.64.40
Astreinte Informatique : (+33) 06.81.85.61.43
Member of the OCA (Odoo Community Association)
Web Site | Twitter

Le mer. 8 juin 2022 à 14:36, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
Hi all,

As some people are requesting wallet functionalities (aka Financial Reserve), I request the creation of 'wallet' repository under the umbrella of Accounting PSC.

As soon as it is created, we are going to propose PR's with our current work.

So, see you there!

Many thanks.

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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

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

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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

--

Simone Orsi

Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

by Simone Orsi - 11:15 - 21 Jun 2022

Re: Split of contract/agreement

Done https://github.com/OCA/agreement

On Tue, Jun 21, 2022 at 6:42 AM Kitti U. <kittiu@ecosoft.co.th> wrote:

+1

On Mon, Jun 20, 2022 at 9:47 PM Bruno Joliveau <bruno.joliveau@numigi.com> wrote:
+1
Bruno Joliveau - Président
NUMIGI SOLUTIONS INC.
bruno.joliveau@numigi.com
(514) 317-7944

Longueuil, Québec, Canada
http://www.numigi.com/

Le lun. 20 juin 2022 à 02:42, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
Hi all,

Before merging the first agreement module to v15, and after some discussions I've had about overloaded repositories, I want to create a new one for those related.

The PR for agreement is here, where I've already suggested it: https://github.com/OCA/contract/pull/795

Thanks for your feedback on this

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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

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

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

--

Simone Orsi

Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

by Simone Orsi - 11:15 - 21 Jun 2022

Re: Split of contract/agreement

+1

On Mon, Jun 20, 2022 at 9:47 PM Bruno Joliveau <bruno.joliveau@numigi.com> wrote:

+1
Bruno Joliveau - Président
NUMIGI SOLUTIONS INC.
bruno.joliveau@numigi.com
(514) 317-7944

Longueuil, Québec, Canada
http://www.numigi.com/

Le lun. 20 juin 2022 à 02:42, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
Hi all,

Before merging the first agreement module to v15, and after some discussions I've had about overloaded repositories, I want to create a new one for those related.

The PR for agreement is here, where I've already suggested it: https://github.com/OCA/contract/pull/795

Thanks for your feedback on this

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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

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

by Kitti Upariphutthiphong - 06:41 - 21 Jun 2022

Re: Split of contract/agreement

+1

Bruno Joliveau - Président

NUMIGI SOLUTIONS INC.

bruno.joliveau@numigi.com

(514) 317-7944

Longueuil, Québec, Canada

http://www.numigi.com/

Le lun. 20 juin 2022 à 02:42, Roussel, Denis <denis.roussel@acsone.eu> a écrit :

Hi all,

Before merging the first agreement module to v15, and after some discussions I've had about overloaded repositories, I want to create a new one for those related.

The PR for agreement is here, where I've already suggested it: https://github.com/OCA/contract/pull/795

Thanks for your feedback on this

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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

by Bruno Joliveau - 04:46 - 20 Jun 2022

Re: Split of contract/agreement

+ 1

Marcel Savegnago

Escodoo

Em seg., 20 de jun. de 2022 às 03:53, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> escreveu:

OK for me.

Regards.

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

by Marcel Savegnago - 04:36 - 20 Jun 2022

Re: Split of contract/agreement

OK for me.

Regards.

by Pedro M. Baeza - 08:51 - 20 Jun 2022

Split of contract/agreement

Hi all,

Before merging the first agreement module to v15, and after some discussions I've had about overloaded repositories, I want to create a new one for those related.

The PR for agreement is here, where I've already suggested it: https://github.com/OCA/contract/pull/795

Thanks for your feedback on this

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium

Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium

Zone industrielle 22 | L-8287 Kehlen | Luxembourg

by Denis Roussel - 08:41 - 20 Jun 2022

Re: Module loading priority and inheritance

Richard, I understand your concern about the priority number, but having it in our toolbox could still be extremely useful.

As a first step, I made a PR that implements both:

https://github.com/odoo/odoo/pull/93928

Contrary to my original proposal, I don't alter the SQL query, the sorting is done in python like the dependency loading by using the manifest attributes (not stored in the DB)

by Yann Papouin - 03:21 - 17 Jun 2022

Re: Creation of Wallet repository

Hi @Board,

We had a meeting with all people interested in (Grap/Akretion/CoopITEasy/Acsone).

So, we agree that we need it.

Could you create a 'wallet' one ?

Many thanks

On Wed, Jun 8, 2022 at 2:54 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:

Of course, we have done it in 8/10/14, the current version is there:

https://github.com/acsone/acsone-addons/tree/14.0/account_wallet

On Wed, Jun 8, 2022 at 2:46 PM Sylvain LE GAL <sylvain.legal@grap.coop> wrote:
Hi Denis,

Thanks for the information.

FYI, we worked with coop it easy on a implementation of wallet for account & pos.

the current code for V12 is available here :
- https://github.com/coopiteasy/addons/tree/12.0/account_customer_wallet
- https://github.com/coopiteasy/addons/tree/12.0/pos_customer_wallet

Could be great to benchmark various implementation to choose the better one (or a mix of feature from various implementations)

Could you send the url of the repo with your current work ?

kind regards.

CC : Carmen / Catherine from coop it easy.

Sylvain LE GAL - Twitter
GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)
Site Web | FramaSphere | Facebook
3 Grande rue des Feuillants, 69001 Lyon
Standard : (+33) 09.72.32.33.17
Service Informatique : (+33) 09.73.79.64.40
Astreinte Informatique : (+33) 06.81.85.61.43
Member of the OCA (Odoo Community Association)
Web Site | Twitter

Le mer. 8 juin 2022 à 14:36, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
Hi all,

As some people are requesting wallet functionalities (aka Financial Reserve), I request the creation of 'wallet' repository under the umbrella of Accounting PSC.

As soon as it is created, we are going to propose PR's with our current work.

So, see you there!

Many thanks.

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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

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

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium

Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium

Zone industrielle 22 | L-8287 Kehlen | Luxembourg

by Denis Roussel - 02:51 - 17 Jun 2022

Re: Module loading priority and inheritance

Yann,

Yes, we too have occasionally encountered such issues. Bridging modules are sometimes required to ensure correct execution, but then, that is still for modules all within our control.

We often find the issue worst when using a third-party app, where there is a complete method overwrite (and maybe justifiably so).

https://www.odoo.com/it_IT/forum/assistenza-1/modules-order-of-dependencies-159563

Under your proposal, though, one would need to know about the modules causing the issue - which generally, I guess, is feasable.

I do wonder, though, if implementing a "soft_depends" as opposed to a loading priority, is better.

If randomly, in a manifest, there is a loading priority, then you sort of need to know and set all the other loading priorities, even in the third party modules, which may have their own issues.

A soft depends, at least, it is clear that "this module has a conflict with that module which is now resolved by this dependency", as a priority number just gets lost (like sequences on views when you have many modules extending views)

I would love to see something in this area...

Richard

Kind Regards

A close up of a sign

Description automatically generated

Richard deMeester

Senior Development Analyst

www.willdooit.com

richard.demeester@willdooit.com

T: (03) 9135 1900 | M: 0403 76 76 76 | A: Bld 10/435 Williamstown Road, Port Melbourne, 3207

A picture containing monitor, screen, holding, person

Description automatically generated

MAKING GROWTH THROUGH TECHNOLOGY EASY

Notice: This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, you may not disclose or use the information in this email in any way. If you have received this email in error please notify the sender. Although reasonable precautions have been taken to ensure no viruses are present in this email, no responsibility is accepted by WilldooIT Pty Ltd or its related entities for any loss or damage arising from the use of this email or attachments. Any views expressed in this email or file attachments are those of the individual sender only, unless expressly stated to be those of WilldooIT Pty Ltd  ABN 85 006 073 052 or any of its related entities.

From: Yann Papouin <ypa@decgroupe.com>
Sent: Friday, 17 June 2022 7:02 PM
To: Contributors <contributors@odoo-community.org>
Subject: Re: Module loading priority and inheritance

After investigation, the sequence field is only used for the kanban view to display applications in a specific order.

Module list is fetched from database in odoo/odoo/modules/loading.py::load_marked_modules with this query

cr.execute("SELECT name from ir_module_module WHERE state IN %s" ,(tuple(states),))

So, the module loading order actually depends on 4 params:

PostgreSQL database collation
Module name
Datetime of the creation of the ir_module_module row (since no ORDER BY is defined in the query)
The dependencies

That's a terrible loading implementation as the parameter 3 is based on an internal postgreSQL data, it also depends on the list order of your addons_path and also depends on when odoo/addons/base/models/ir_module.py::update_list is called.

Example for this last assertion:

On the development database:

You add the module account_extra, that depends on account and override method update_something, in your main addons path
update_list()
Two weeks later, you add the module account_best , that also depends on account and also override the method update_something, in your main addons path
update_list()
Module account_extra will be loaded before account_best

Three weeks later, on the production database:

You add modules account_extra and account_best in your main addons path
update_list()
Module account_best will be loaded before account_extra

And there I'm not talking about other cases like:

Multiple addons_path
Manual module deletion from odoo module list followed by a module list update
Manual module installation from UI whereas the server is already started with loaded modules

So, I agree that most cases would be solved by the depends attribute but a fix could still be:

Add a loading_priority manifest key:

default value is 0 if not set, could be positive (load before) or negative (load after)
add an ORDER BY loading_priority, name in all SQL query of the loading.py

Add a soft_depends manifest key:

a list of modules that we depends on, only if they exists and are installed

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

by "Richard deMeester" <richard.demeester@willdooit.com> - 02:46 - 17 Jun 2022

5 attachments 5 attachments

Archives

Contributors

Re: l10n-estonia status and proposing myself as PSC

Re: l10n-estonia status and proposing myself as PSC

Re: Translations done by a webservice

Re: Translations done by a webservice

Translations done by a webservice

Re: New repos proposal

Re: New repos proposal

Re: New repos proposal

Re: Creation of Wallet repository

Re: Creation of Wallet repository

Re: Creation of Wallet repository

Re: Split of contract/agreement

Re: Split of contract/agreement

Re: Split of contract/agreement

Re: Split of contract/agreement

Re: Split of contract/agreement

Split of contract/agreement

Re: Module loading priority and inheritance

Re: Creation of Wallet repository

Re: Module loading priority and inheritance

Follow us