Community mailing list archives
Re: New OCA repository to suggestby
Your remark of the dependencies is a good one, but it these could be solved within the code.
Normally I would program the general code which could be the connector for which we can load the module specific code. In Java this is called the decorating pattern. I just starting using Python but there there are a lot of possibilities to decorate a function. So it would be no problem to design a general solution which can be made more specific for each module. In that case you have a good split and you're could only use the parts which are activited within ODOO. I currently don't know exactly how to get this information within ODOO but it should be possible because ODOO self knows which modules are installed.
'connector-interfaces' sounds to me more generic (IMO, connector-import-export is a bit too long). But I don't remember if it was proposed during the discussion on the mailing list.
On Fri, Sep 19, 2014 at 2:42 PM, Markus Schneider <firstname.lastname@example.org> wrote:
Hi, we have a discussion on the connector mailing list about the "names" of this repositories. But we find no final conclusion because everyone has a different point of view. What i can summarize is: 1) The new repositories should be related to "connector" so modules without "connector" are need some other home. 2) From our point "connector-file" fells not right, because we have some modules where we export data, and send it at the end by email. My suggest is "connector-import-export" was the best option to have a repository for modules to import and export data with the connector framework without related to a special backend. Kind Regards Markus On 19.09.2014 10:53, Joël Grand-Guillaume wrote: > Dear community, > > > I want to suggest a new repository/project to include within the OCA > under the connector-maintainers team responsibilities. I would call it > "connector-interfaces". > > The purpose to this new project would be to host generic connector among > various interfaces to collect and updates data in Odoo. As example, I > already have 2 candidates modules: > > * connector_file : Which provide necessary tools and methods to deal > with the importation of huge files using the connector (see : > https://github.com/camptocamp/connector-file) > > * connector-odbc : Which provide necessary tools and method to access, > load and update data from an ODBC source (not publicly release yet, but > this is the purpose of this mail) > > I can see also in the future other connector among other interfaces : > EDI,... > > Do you agree on such a new project ? > > > Regards, > > > Joël > > > -- > > > *camptocamp* > INNOVATIVE SOLUTIONS > BY OPEN SOURCE EXPERTS > > *Joël Grand-Guillaume* > Division Manager > Business Solutions > > +41 21 619 10 28 > www.camptocamp.com > > > _______________________________________________ > Mailing-List: https://www.odoo.com/groups/community-59 > Post to: mailto:email@example.com > Unsubscribe: https://www.odoo.com/groups?unsubscribe > -- Dipl.-Comp.-Math. Markus Schneider Softwareentwickler initOS GmbH & Co. KG An der Eisenbahn 1 21224 Rosengarten Mobil: +49 (0)172 2303699 Phone: +49 (0)4105 5615613 Fax: +49 (0)4105 5615610 Email: firstname.lastname@example.org Web: http://www.initos.com Geschäftsführung: Dipl. Wirt.-Inf. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Haftende Gesellschafterin: initOS Verwaltungs GmbH Sitz der Gesellschaft: Rosengarten – Klecken Amtsgericht Tostedt, HRA 201840 USt-IdNr: DE 275698169 Steuer-Nr: 15/205/21402
Post to: mailto:email@example.com