Those are some nice answers: Can we have it on the wiki?
Also in terms of comparison with Open ERP, i think its important and would be a sure question. I would love to draft differences in the following scope: 1. Python - Tryton being more pythonic... tryton as module to modules in pypy 2. Standards of Code & Project Quality 3. Project Organisation - Community/Drivers/ (eg. Contribution acceptance to main stream version bundles) My 800 EUR ;) 4. Features & Usability 5. Future goals & objectives. I think we have several differences in the two projects in the above grounds. I am sure it will be good to maintain a wiki on these fronts, because this is one common question I hear everyday! Thanks, On Thu, May 13, 2010 at 12:58 PM, Cédric Krier <[email protected]>wrote: > On 13/05/10 13:19 +0200, Udo Spallek wrote: > > Hey Sharoon, > > > > Am Mittwoch, den 12.05.2010, 21:20 +0100 schrieb Sharoon Thomas: > > > I have been informed by the organisers of Europython 2010 that a talk > > > I had submitted representing Tryton has been accepted. > > > I am sure this is good news for all of us > > Yes, thats really good news! > > > > > and we are looking forward to your valuable suggestions and ideas for > > > the same. (No guarantees that everything can be included but the final > > > choice will be made by the tryton-dev group). > > > From the initial brainstorming, I propose that a module be built > > > onstage which could simply demonstrate most of our framework and > > > approach. > > Yes, since in the last posts were clear-out, that the audience are > > mostly developers, I promote to follow your path with showing a small > > module. In the following I collect some unsorted suggestions: > > > > I would start with a half-finish module where you can explain the main > > aspects of programming Tryton (What is Module, Model, Field, View, > > Report,...). > > Then extend this module with some changes to show Trytons RAD abilities. > > But make the 'live-hacking' as less as possible. > > You can use a mercurial repository with commit at each step. > And then you replay the dev with "hg update -r xxx" > > > When audience is 'Python developers' and the topic is 'a framework for > > business applications', you'll need to tell the developers in some > > sentences ideas how to make business with Tryton. > > Here is some possible answers > > > Count with at least one the following questions: > > * Why not using Django or another RAD framework? Differences? > > We want thin client (faster encoding, faster communication) and not web > only. > We did not find other framework that allow Tryton extension of models like > we > do. > > > * Why not using Open-ERP? Differences? > > http://www.b2ck.com/~ced/Tryton_vs_OpenERP.txt (no more up to date but > some > part are still valide) > And your own thoughts :-) > > > * Why not using Report Markup Language (Report Labs)? Differences? > > relatorio use Ooo as template. Allow easy customization and guarantee the > layout of the output (WYSIWYG) > > > * Why not using SQL-Alchemy/Storm for ORM? Differences? > > Reuse OpenERP one. > domains are Python independant which allow to expose CRUD function to other > programing languages. > ensure some behavior for business application like: transaction, Decimal > > > * Why not using QT/wx-widgets for the client? > > Except that I prefer GTK, I have no argument. > > -- > Cédric Krier > > B2CK SPRL > Rue de Rotterdam, 4 > 4000 Liège > Belgium > Tel: +32 472 54 46 59 > Email/Jabber: [email protected] > Website: http://www.b2ck.com/ > -- Sharoon Thomas Business Analyst & Open Source ERP Consultant CEO @ http://openlabs.co.in -- [email protected] mailing list
