Hi,
Thanks for the kind words
if the following is tltr: update datamaker, you have now Name() as a property query
----- now onto the explanation
I think you are mistaken with the structure and the content. It's not a good practice that your node represent the data itself, the node name is the structure of your data.
it doesn't take away this request and I agree it's useful, but I think you could end up in trouble down the road by doing so, it's not how xml was designed to be used. the data structure must be known, and the data itself should indicate what's coming next.
so it's perfectly fine and recommended to add attributes to define the content like you did, but it should not be the "name" of the node, but rather something specific to your data semantic meaning. if the node is a prop in your scene then you should have
<prop type="furniture>content expect to be formatted to describe a furniture</prop>
instead of <node name="nodename"> which confuse structure and data.
let's take the example of a human holding a tool. you don't know what his holding, could be food, could be anything. One way would be to do like you did, creating a node inside the right hand node and get the name of the name to know what it is.
<hand><food>Apple</food></hand>
with the above, you need to tap into the structure itself mixing it up with the data itself in order to know what's going on.
but what if I create a generic prop node instead.
<hand><prop type="food">Apple</prop></hand>
this second approach is far more powerful and flexible both to represent data and to work with it for programming, it's powerfull because the structure is expected, a Hand can only have a Prop as a child node, and the content of the Prop node is known via its structural attribute type, which lets your program know what to expected inside that prop node. Likely it will be more detailed:
<hand>
<prop type="food">
<food>
<name>Apple></name>
<sort>Granny smith</sort>
</food>
</prop>
</hand>
Does that make sense? while I also agree that it doesn't help when you don't know what's coming up should you have not followed that structure paradigm I just explained. Html being the example, where within a div, you don't know what you will get. However, as I said earlier, you a re opening a can of worm with this approach even if it feels at first a very elegant one.
long story short, I have added this possibility right within xpath, allowing you to query the name of a node like this: "Name()" which is a valid xpath query.
for XML Save In Proxy and save xml as string, the proxy component itself has a "Store in memory: property, so you can use that. Is that not working on your end?
Please update it from the ecosystem, note that it's now distributed starting from 5.6, not 4.x anymore. and soon, 2017 will be the new starting point, Unity is going to move away from supporting 5.x in july.
Bye,
Jean