Hi there, come on now it aint that hard to change the rml code. I dont think 
you plan on making a new report. The corporate_rml_header is a good one to 
start experimenting.
Some basics:
-Each tag has to be closed again. This can be done in two ways.
  For a single tag like pagenumber you open with a '<' and close with '/>' 
  For a tag which contains more tags you start with example : 
<drawCentredString x="10.5cm" y="0.8cm"> and end with </drawCentredString> 
(watch the slashes '/', they are important).
-calls to database fields are between double brackets [[ and]] . You can 
experiment with moving fields to different locations and disabling fields by 
putting for example : <!--> in front of the tag and <--> after the tag. I would 
recommend using at text tool which understands the code like gedit in ubuntu. 
Maybe textpad in windows, didn't try yet.
-read for the style tags in the rml manual. They're not that difficult, play 
around a bit. You dont need to restart the tiny server or client while editing 
rml. If he hangs just open a new client, eventually the hanging client will 
give an error and revive (in ubuntu that is, dont know in win since i dont 
develop there). If you run the server instead of the service (in win: stop 
service in and start server manually, in ubuntu: stop server and run 
tinyerp-server command) when an error occurs you can now see the line-number 
where to look in your rml-file for the error. 

Here's some code :

<!--pagenumber-->
<drawCentredString x="10.5cm" y="0.8cm"> Pagina 
<pageNumber/></drawCentredString>
<!--commenting blocks of code-->
<!--><drawRightString x="19.9cm" y="27.8cm">&#91;&#91; 
company.partner_id.website &#93;&#93;</drawRightString><-->

This should get going for the basics. 

Greets




-------------------- m2f --------------------

--
http://www.openerp.com/forum/viewtopic.php?p=25195#25195

-------------------- m2f --------------------


_______________________________________________
Tinyerp-users mailing list
http://tiny.be/mailman/listinfo/tinyerp-users

Reply via email to