> It is really bad attitude. You must see Tryton as a tool and not as a > product. >
I personally consider that tryton as a framework (which is a tool) is different than tryton as an ERP (which is more of a product). The framework part (that would be server + client + core modules) must provide a complete documentation fully developer-oriented. The modules which makes it an ERP (sales, stock, party etc...) should come with a user documentation, as they are supposed to be used "as is" with little to no extra developments. At Coopengo, we use the tryton framework so the technical doc suits us pretty well. We plan to use some of the accounting modules soon but here we would like both dev and user doc. We got people who do not have the time / knowledge to read the code but we need their advice on how tryton fare as an accounting software, and right now they just cannot use it until we dev can write down the how-tos. That being said, we do not want (and I do not think anyone here wants) to go down OpenERP path and sacrifice the stability of the framework for better sales. My 2 cents Jean CAVALLO Coopengo
