# Syncing Custom Component Palettes **URL:** \ **Category:** Ignition\ **Created:** [August 27, 2020, 7:06pm UTC](https://forum.inductiveautomation.com/t/syncing-custom-component-palettes/38140 "2020-08-27T19:06:43Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [August 27, 2020, 10:41pm UTC](https://forum.inductiveautomation.com/t/syncing-custom-component-palettes/38140/4 "2020-08-27T22:41:03Z")
It would be nice if a _little_ effort could be made towards better source control compatibility on the Vision side.... like these recommendations I made earlier this year so the resource on disk could be the XML from the shift-right-click menu: > [@Meta-programming a window?](http://forum.inductiveautomation.com/t/meta-programming-a-window/32769/6): > > If you want the Vision Window XML to be friendlier, I recommend changing the handler for the window itself to save encoding the InteractionController for last. You may also want to encode the root container first, or nearly first. Almost all of the misery in the existing file format is due to the ‘i’ of the interaction controller coming before the ‘r’ of the root container. (I suspect field serialization is alphabetical.) This one change should cause VisionComponent serialization to approxim… --- _[View the full topic](https://forum.inductiveautomation.com/t/syncing-custom-component-palettes/38140)._