Hi guys, I recently did a relatively small piece of software based on OpenERP and my experiences were full of such hurt that I ended up raging about it here: http://www.reddit.com/r/Python/comments/cfycv/has_anyone_here_used_openerp_are_your_experiences/
In any case, I delivered. As shaky and full of duct tape as it might be, it works. Now I'm about to embark on a huge project that will likely end up taking the rest of the year to complete, train, and deploy with several years of additions and support later. And I don't want to go back to OpenERP for fear of developing chronic depression or other such maladies. As you can see from my ragepost up there, I had some rather specific pains with OpenERP and I'm wondering if Tryton has fixed these or not. So here's a bunch of questions to the Tryton community. In exchange for your helpful reply, and provided we all get along, I will certainly be using this opportunity to contribute back to Tryton to the best of my ability -- my client is Open Source friendly in that regard. 1. When I mess up XML somewhere, does Tryton also give me obscure errors from the bowels of the core or does it do XML validation beforehand for that not to happen? (I love the sweet way Genshi handles my XML problems.) 2. When I change the definition of some object via OpenERP's ORM, then its automagical data migrator sometimes messes up badly. What does Tryton provide to help me find a saner way of migrating data to a new schema? 3. OpenERP's GUI client doesn't do pagination in its one-to-many and many-to-many fields, so if your object has a relationship with 20k other objects, you're gonna sit there for half an hour with a frozen screen until the GUI downloads and renders everything. Is Tryton more sane in this regard? 4. I would like to start using Python 3 soon. What are your plans regarding this? 5. Bonus question: What did you absolutely hate about OpenERP and what has Tryton done to fix it for you? Many thanks in advance for your replies. Best, Elver -- [email protected] mailing list
