# what can be customized with XML files

**URL:** https://discourse.paraview.org/t/what-can-be-customized-with-xml-files/470
**Category:** Development
**Created:** [August 24, 2018, 1:25pm UTC](https://discourse.paraview.org/t/what-can-be-customized-with-xml-files/470 "2018-08-24T13:25:49Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![embeddedmz](https://discourse.paraview.org/user_avatar/discourse.paraview.org/embeddedmz/32/142_2.png) [@embeddedmz](https://discourse.paraview.org/u/embeddedmz)
#### Post date: [August 24, 2018, 1:25pm UTC](https://discourse.paraview.org/t/what-can-be-customized-with-xml-files/470/1 "2018-08-24T13:25:49Z")

</div>

Hi,

I am still lost in the XML/Proxy jungle of PV and I want to know what can be customized in an XML file describing a plugin. For example, If I create a custom view that inherits vtkPVRenderView, in the XML file (under the RenderViewProxy tag) is it possible to set new default values of some “views” properties like “InteractionMode” and “representations” properties such as “Scale” ?

Is there a good documentation describing the tags that can be used and what can fetched from the vtkSMProxies ?

What’s the difference between ProxyProperty and SubProxy tags ??? (look at views\_and\_representations.xml)

Any techniques related to XML debugging is also welcomed !

Another question : is it vtkSMSessionManager who parses all the XML files in order to create vtkSMProxies ? any information related to the XML subject is welcome !

Thanks.