squirrelly | Image and text sharing from your clipboard or mobile device | Database library

Lots of different people have come up with lots of different conversions of JSON to XML. As already pointed out, the XPath 3.1 and the XSLT 3.0 spec have a loss-less, round-tripping conversion with json-to-xml and xml-to-json that can handle any JSON.

There are simpler conversions that handle limited sets of JSON, the main problem is how to represent property names of JSON that don't map to XML names e.g. { "prop 1" : "value" } is represented by json-to-xml as value while conversions trying to map the property name to an element or attribute name either fail to create well-formed XML (e.g. value) or have to escape the space in the element name (e.g. value or some hex representation of the Unicode of the space inserted).

In the end I guess you want to select the property foo in { "foo" : "value" } as foo which the simple conversion would give you; in XPath 3.1 you would need ?foo for the XDM map or fn:string[@key = 'foo'] for the json-to-xml result format.

With { "prop 1" : "value" } the latter kind of remains as fn:string[@key = 'prop 1'], the ? approach needs to be changed to ?('prop 1') or .('prop 1'). Any conversion that has escaped the space in an element name requires you to change the path to e.g. prop_1.

There is no ideal way for all kind of JSON I think, in the end it depends on the JSON formats you expect and the willingness or time of users to learn a new selection/querying approach.

Of course you can use other JSON to XML conversions than the json-to-xml and then use XPath 3.1 on any XML format; I think that is what the oXygen guys opted for, they had some JSON to XML conversion before XPath 3.1 provided one and are mainly sticking with it, so in oXygen you can write "path" expressions against JSON as under the hood the path is evaluated against an XML conversion of the JSON. I am not sure which effort it takes to indicate which JSON values in the original JSON have been selected by XPath path expressions in the XML format, that is probably not that easy and straightforward.

If is better to specifiy in a .gitattributes (as in here) a consistent eol policy for files with specific extensions: see this .gitattributes for instance, which uses LF.

VSCode has "auto" as its default file.eol, which should be enough: Git will do the conversion on checkout, and VSCode won't convert it.

Ok, I finally figured it out on my own. Here is the answer for my specific problem, just in case somebody runs into the same problem:

It seems that the addon NoScript was adding the blocking header entries after they get applied by script or in the tag of the HTML file. Disabling it fixed the issue :)

GUITexture is indeed deprecated just like GUIText . Since your hudCharge variable is a type of Texture2D, make chargeHudGUI to be type of RawImage instead of Image so that you can assign it directly with the texture property.

Go to GameObject ---> UI ---> RawImage and Unity will create a Canvas with a GameObject as a child. That child GameObject will have a RawImage component. You can learn more about the new UI system here.

So, replace

As @PaulAbbott says, the interface and its implementation does not match. Your interface is:

lappend $l1 $l2 appends the contents of l2 to the variable NAMED by the contents of l1. You want lappend l1 $l2, in much the same way that you set variables via set l1 whatever, rather than set $l1 whatever.