Thanks for your quick reply! how shell one contribute to the docs? Is there a wiki? Or is the only way to provide rst files / patches? What editor / eclipse plugin do you use for them? Where to send patches? Maybe a documentation page for that?
I am a litte spoiled from django and its documentation... They have always trunk docs, too. Is there a chance to build them automatically nightly (e.g using ant or whatever...) for www.tryton.org, too (and add dev docs there)? And add the full PDF that one seems to be able to build out of the docs? sorry for bothering again - is there something about: - when and how to prevent opening new windows (e.g. on new in party - address) - what happens on cancel in a new window? I get a sequence error after hitting that... - is there action documentation anywhere besides the pure xml notation? regards Henrik >reply to message: >date: 12.04.2012 10:41:21 >from: "Cédric Krier" <[email protected]> >to: [email protected] >subject: [<tryton-dev.googlegroups.com>] Re: [tryton-dev] developer >documentation > >On 12/04/12 00:57 -0700, Henrik Genssen wrote: >> Hi, >> >> is there more documentation available than: >> http://doc.tryton.org/2.2/ >> http://code.google.com/p/tryton/wiki/ > >Almost, there is also >https://docs.google.com/document/d/1wPjdd965wy0_WlQCu8nCw1zl9GJ9xa2jQHQflpiBx98/edit?authkey=CLK6q9gK >We should find a way to integrate it in www.tryton.org > >> do we have something like this: >> OpenERP_Technical_Memento_v0.6.3.pdf<http://www.openerp.com/download/OpenERP_Technical_Memento_v0.6.3.pdf> > >Not really. > >> How shell I understand the docs? Look up the links above - everything I do >> not find look up at OpenERP? > >This is less and less possible. >It is more if you don't find look at the code. > >> There are so many things, I am missing: >> - rights management > >Yeps, this should be added to the trytond doc. > >> - sequence generation > >Idem. > >> - wizards (single and multi-page) > >It is in trunk. > >> - examples > >In topics section, we try to put examples. > >> I do not think that reengeneering the code is an option for many people. >> I feel tryton is really powerful - but the reengeneering part eats the >> time, you could save using tryton to develope your processes... > >We try now each time something is reviewed, refactored etc. to write the >documentation about it. But any help/patch is welcome. > >-- >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/ > -- [email protected] mailing list
