Hello, As I continue to investigate Tryton, I'm starting to look through the code. I've read through the documentation, and it seems to me like the best place to get started in understanding how the code is put together is to try creating a simple module. In the documentation: http://tryton-documentation.readthedocs.org/en/latest/developer_guide/getting_started.html there is a tutorial on creating a simple module, "library". And at first it looks great!
I've gone through the steps on that page, created the menu, created the report, but there's nothing on there about actually creating the form to input and view the Library Books. The next page: http://tryton-documentation.readthedocs.org/en/latest/developer_guide/basic_concepts.html talks about validating fields, and there is a brief section on views, but this does not seem to be a complete example. Am I missing something, or was this document just not finished? I also viewed this older document: http://code.google.com/p/tryton/wiki/HelloWorld which has a "Hello World" module development. However, the code for the view looks like: ---------- <record model="ir.ui.view" id="hello_view_tree"> <field name="model">hello.hello</field> <field name="type">tree</field> <field name="arch" type="xml"> <![CDATA[ <tree string="Hello World"> <field name="name"/> <field name="greeting"/> </tree> ]]> </field> </record> --------- when I looked at the code of other modules, it doesn't seem like this CDATA xml structure is common, so I'm wondering if this documentation is referring to an older way of writing modules? I'd like to walk through the steps of doing a complete, simple, module so I can see how it is done and understand better how the different pieces of Tryton fit together. Is there a guide that someone can recommend to me? Or a good, simple, module to look at that uses best practices? Perhaps a reference exists that I'm just not finding. I am a programmer who in the past was a technical documentation writer. It seems to be rare in this field, but I actually somewhat enjoy writing documentation and would be glad to contribute to Tryton by writing or updating some tutorials, if I can figure out how this all works, so any assistance would be appreciated. Thanks, Nick
