Plist files are more and more ubiquitous. Apple uses them for its configuration files and we use them to describe exercise content. They aren’t very pleasant to read for humans, but that doesn’t mean computers dislike reading them. So I wrote a little javascript to parse a plist file to an object. Hope you like it.<\/p>\n
<\/p>\n
<script language="javascript" runat="server">\r\nXMLUtil = function() {\r\n \/\/ nothing\r\n}\r\n\r\nXMLUtil.createXmlDom = function(xmlFile, xslFile){\r\n var result = null;\r\n try{\r\n result = new ActiveXObject("Msxml2.DOMDocument.6.0");\r\n result.validateOnParse = false;\r\n result.setProperty("AllowDocumentFunction", true);\r\n result.setProperty("AllowXsltScript", true);\r\n result.setProperty("ProhibitDTD", false);\r\n }catch(e){\r\n try{\r\n result = new ActiveXObject("MSXML2.DOMDocument.3.0");\r\n }catch(e){\r\n try{\r\n result = new ActiveXObject("Microsoft.XMLDOM");\r\n }catch(e){\r\n Response.Write("ERROR MSXML is not installed.");\r\n result = null;\r\n }\r\n }\r\n }\r\n if(typeof result == "object"){\r\n \/\/ "XSLPattern" in 3.0. "XPath" in 4.0, 5.0, 6.0\r\n result.setProperty("SelectionLanguage", "XPath");\r\n result.async = false;\r\n if(typeof xmlFile == "string"){\r\n if(xmlFile.indexOf(":") == -1){\r\n xmlFile = Server.MapPath(xmlFile);\r\n }\r\n result.load(xmlFile);\r\n }\r\n if (result.parseError.errorCode != 0) {\r\n Response.Write("ERROR " + result.parseError.reason);\r\n result = null;\r\n }else{\r\n if(typeof xslFile != "undefined"){\r\n if(typeof xslFile == "string"){\r\n xslFile = XMLUtil.createXmlDom(xslFile);\r\n }\r\n if(xslFile.parseError.errorCode != 0){\r\n Response.Write("ERROR " + xslFile.parseError.reason);\r\n result = null;\r\n }else{\r\n var transformedFile = XMLUtil.createXmlDom();\r\n result.transformNodeToObject(xslFile, transformedFile);\r\n result = transformedFile;\r\n }\r\n }\r\n }\r\n }\r\n return result;\r\n}\r\n\r\nXMLUtil.parsePlistDict = function(dictNode){\r\n var result = new Object();\r\n var keyNodes = dictNode.selectNodes("key");\r\n for(var i = 0, n = keyNodes.length; i < n; i++){\r\n var key = keyNodes[i].firstChild.nodeValue;\r\n var val = XMLUtil.parsePlistValue(keyNodes[i].nextSibling);\r\n result[key] = val;\r\n }\r\n return result;\r\n}\r\n\r\nXMLUtil.parsePlistValue = function(valueNode){\r\n var result = null;\r\n switch(valueNode.nodeName){\r\n case "true":\r\n result = true;\r\n break;\r\n case "false":\r\n result = false;\r\n break;\r\n case "string":\r\n if(valueNode.firstChild != undefined){\r\n result = valueNode.firstChild.nodeValue;\r\n \/\/ result = unescape(result);\r\n \/\/ result = result.replace(\/\\+\/g, " ");\r\n }\r\n break;\r\n case "dict":\r\n result = XMLUtil.parsePlistDict(valueNode);\r\n break;\r\n case "array":\r\n result = [];\r\n for(var i = 0, n = valueNode.childNodes.length; i < n; i++){\r\n result.push(XMLUtil.parsePlistValue(valueNode.childNodes[i]));\r\n }\r\n break;\r\n default:\r\n Response.Write("ERROR can't parse "+valueNode.nodeName);\r\n }\r\n return result;\r\n}\r\n\r\n\/\/ usage:\r\nvar plistXml = XMLUtil.createXmlDom("c:\\\\example.plist");\r\nvar obj = XMLUtil.parsePlistDict(plistXml.firstChild.firstChild);\r\n<\/script><\/pre>\n","protected":false},"excerpt":{"rendered":"Plist files are more and more ubiquitous. Apple uses them for its configuration files and we use them to describe exercise content. They aren’t very pleasant to read for humans, but that doesn’t mean computers dislike reading them. So I … Continue reading