Pages: 1
Print
Author Topic: Modifying print_local.xml  (Read 399 times)
gcrews
Member

Posts: 189


« on: January 18, 2011, 11:49:08 AM »

I am looking to modify the print_local.xml file in renditions folder so that everyone will have the same output options (I know  the  user file will need to be deleted).  Is there any guide on what id to use on instruction elements?  If I make some changes to my settings and go look at the print_local.xml in the appdata folder I can see the change. The things I’m wondering about is some of the instructions change from id=”200” to id=”100” between the application file and the user file. Is it ok to change the renditions\print_local.xml file using id=”100”?

Example: I add ANT_PARAM_dita.temp.dir=c:\temp in the Xmetal interface. The following is added to the user print_local file:
<instruction id="100">
       <name xm_cmd="0">ANT_PARAM_dita.temp.dir</name><value>c:\temp</value>
</instruction>

Another example: I change ANT_OPTS to ANT_OPTS= -Xms512m -Xmx756m following is added to the user print_local file:
 <instruction id="100">
         <name xm_cmd="0">ANT_OPTS</name> <value>-Xms512m -Xmx756m</value
</instruction>
However the renditions\print_local.xml file has id=200”

Can I just put those into the application print_local file with  id=”100” or should the id be changed to 200?

It could help if I know what the difference is (if any) between id 200 and 100.

Thanks in advanced.

« Last Edit: January 18, 2011, 12:00:13 PM by gcrews » Logged
Derek Read
Program Manager (XMetaL)
Administrator
Member

Posts: 1546



WWW
« Reply #1 on: January 18, 2011, 06:27:50 PM »

Your new ("end user") instructions should be marked as follows:
Use 200 (exactly) if the instructions are inside a <globals> container.
Use 100 (exactly) if the instructions are inside a <config> container.

Note that you may see other values and these should be considered "internal use only". The @name "id" may be a little misleading as the values are not unique, however, we don't plan on altering this at this point in order to keep backwards compatibility with previous versions.
« Last Edit: January 18, 2011, 06:31:17 PM by Derek Read » Logged
Pages: 1
Print
Jump to: