Split v4p xml definition

since the current v4p files and any subversion system are not so close friends yet, just had the idea the current xml definition into a functional and a visual part could help:
the ‘code’ part would just contain nodename, id, pinname and values, and the links.
the visual part would hold the top, left, width, height attributes, linkpoints etc…

and… in addition. to make patch parsing easier it would be lovely to store input pin data into childelements of each pin element (maybe “slice”)…

in terms of subversioning of v4p files… what we need is a visual diff tool for vvvv patches. indeed, the splitup would help alot already though.

Rescued this from the old wiki (anno 2006):

that would be so great!