A Dijous, 16 de juny de 2011 16:28:37, zodman va escriure: > i think manage another software with different technology its more > complicated than make a e-commerce solution with tryton > > For experience on others cases make a middleware between two software will > be dificult and maintain synced too. > > The best in my opinion it is make application what comunicate with tryton > and tryton core will be the heart of all. > For it exists proteus and proteus.js Only needed make a webapp what use > proteus.
Although the solution is not trivial I agree. We suffer daily the problems originated by Magento and osCommerce connectors for OpenERP and I think an integrated solution would be better (even if commercially a little bit more difficult to sell). Maybe Sharoon can provide us with feedback if this approach worked for them with Callisto. > > On Thu, Jun 16, 2011 at 9:32 AM, Rob Martin <[email protected]> wrote: > > Sharoon, and the Tryton community, > > > > I've paid only a little attention to the Magento Connectors projects for > > both Tryton and OpenERP, mostly noticing that the interest is strong and > > activity seems pretty vibrant. The thing is, I don't understand why, and > > I wonder if anyone might be willing to provide me feedback as to why > > they think it's important or valuable to connect Tryton to Magento? I > > know that Magento has features that Tryton does not, but it also seems > > there is significant overlap. What makes Magento bring to the project? > > > > Rob > > > > > > > > On Jun 16, 2011, at 8:23 AM, Sharoon Thomas <[email protected]> > > wrote: > > > > Hello Everyone, > > > > Some of us at Openlabs has been planning and working on the Magento > > connector for Tryton from the past 9 months. From our initial research > > and lessons learnt from building magentoerpconnect [1] for OpenERP, we > > had identified key issues that needed solutions before we attempted to > > build a > > > > tryton connector and they were: > > 1. Clean transformation of EAV [2] in magento to Tryton: In OpenERP we > > dynamically create new fields and extend the product table. However, > > this seemed to work well for small customers, but larger > > implementation of magento started meeting roadblocks. An example of > > the same was an implementation hitting the max col size of 1600 in > > the product table [3]. We addressed this with an object/document > > datastore backend for tryton - Mongo DB [4]. > > 2. The second issue was a clean API to connect to magento rather than > > raw XML RPC calls in between module code. This was also implemented in > > the magento python module [5]. > > > > And now we think its time to start working on the module and we request > > interested community members to participate in the project to build > > blueprints, write code, documentation and test the features. If you dont > > write code, you could still contribute with ideas, and manual testing. We > > have chosen github for project hosting [6] and the empty space (as of > > this writing) has been created. (For the mercurial fan boys : you can > > still push from hg to the git repo [7].) > > > > For Team Openlabs > > > > Sharoon Thomas > > > > [1] <http://launchpad.net/magentoerpconnect> > > http://launchpad.net/magentoerpconnect > > > > [2] <http://en.wikipedia.org/wiki/Entity-attribute-value_model> > > http://en.wikipedia.org/wiki/Entity-attribute-value_model > > > > [3] <https://bugs.launchpad.net/magentoerpconnect/+bug/648667> > > https://bugs.launchpad.net/magentoerpconnect/+bug/648667 > > > > [4] <https://bitbucket.org/sharoonthomas/trytond-mongodb> > > https://bitbucket.org/sharoonthomas/trytond-mongodb > > > > [5] <https://github.com/openlabs/magento> > > https://github.com/openlabs/magento > > > > [6] <https://github.com/openlabs/trytond-magento> > > https://github.com/openlabs/trytond-magento > > > > [7] <http://hg-git.github.com/>http://hg-git.github.com/ > > > > -- > > [email protected] mailing list > > > > -- > > > > [email protected] mailing list -- Albert Cervera i Areny http://www.NaN-tic.com OpenERP Partners Tel: +34 93 553 18 03 http://twitter.com/albertnan http://www.nan-tic.com/blog Advertència Legal: aquest missatge i, en el seu cas, els fitxers adjunts poden contenir informació privada i/o confidencial. Si vostè no és el destinatari del missatge, si us plau, elimini i notifiqui'ns-ho immediatament, no el reenvii ni copi el seu contingut. Si us plau, avisi'ns d'immediat si vostè o la seva empresa no admeten la utilització del correu electrònic via internet per a missatges d'aquest tipus. NaN Projectes de Programari Lliure, S.L. no garanteix la confidencialitat, integritat, rapidesa o correcte recepció del present correu, ni es responsabilitza de possibles perjudicis derivats de la captura, incorporacions de virus o qualsevol altre manipulació efectuada per tercers. No s'autoritza la utilització amb finalitats comercials o per a la seva incorporació a fitxers automatitzats de les direccions de l'emissor o del destinatari. La informació continguda en aquest missatge de correu electrònic és confidencial i pot revestir el caràcter de reservada. Està dirigida exclusivament a la persona destinatària. L'accés o qualsevol us per part de qualsevol altra persona, no estan autoritzats i poden esdevenir il•legals. Si vostè no és la persona destinatària, li preguem que procedeixi a esborrar-lo i a no fer-ne cap us ni transmetre'l a tercers. Si ho considera oportú pot avisar al remitent que el missatge ha arribat a un destí no desitjat. Advertencia Legal: este mensaje y, en su caso, los ficheros anexos pueden contener información privilegiada y/o confidencial. Si usted no es el destinatario del mensaje, por favor, bórrelo y notifíquenoslo inmediatamente, no lo reenvíe ni copie su contenido. Por favor, avísenos de inmediato si usted o su empresa no admite la utilización del correo electrónico vía internet para mensajes de este tipo. Nan Projectes de Programari Lliure, S.L. no garantiza la confidencialidad, integridad, rapidez o correcta recepción del presente correo, ni se responsabiliza de posibles perjuicios derivados de la captura, incorporaciones de virus o cualesquiera otras manipulaciones efectuadas por terceros. No se autoriza la utilización con fines comerciales o para su incorporación a ficheros automatizados de las direcciones del emisor o del destinatario. La información contenida en este mensaje de correo electrónico es confidencial y puede revestir el carácter de reservada. Está dirigida exclusivamente a la persona destinataria. El acceso o cualquier uso por parte de cualquier otra persona, no están autorizados y pueden llegar a ser ilegales. Si usted no es la persona destinataria, le rogamos que proceda a borrarlo y no hacer ningún uso de él ni transmitirlo a terceros. Si lo considera oportuno puede avisar al remitente que el mensaje ha llegado a un destino no deseado. -- [email protected] mailing list
