I was actually just testing the XML tree with the library but I personally have most of my music in Spotify so that would require DB which is another Feature Request anyway. The funny thing is when you open all those PLISTS with Text Edit you get a binary like thing, but with a spacebar hit you actually see all those plist structured as XML even with the XML name at the top of it so that disturbed me )īut yeah if the iTunes library is the only XML Plist I would personally NOT put a constant extra port on the Make XML Tree node for that case only would you ? Don't know. Ok yeah as you said, I travelled the computer a bit and the iTunes library pretty much seems like the only xml property list, its icon also says XML where most other say PLIST. But usually macOS stores property lists in a binary format. Good question - I meant that Make Tree from XML would handle property lists stored as XML text, like the iTunes file. UPDATE: I think this is covered by the request 'Dictionary Support', however I believe it may have low votes due to assumption that this feature request would encapsulate the other? I don't know how useful a list generated from XML would be without its dictionary. In the above example, bar could be the key for the x,y position of a layer, so then I could add multiple values for bar- and simply move through them via indexes! If an index does not contain a 'bar' key then '.key' wouldn't spit out anything. (I already do this for controlling compositions in QC- so I really would love to be able to rebuild my work in Vuo!) This way one can use Index & Keys to control certain aspects of complex compositions. Would output if using a '.key' node (yet to be created): One question for loading structured data: will we have the ability to use Keys to access data? And if so can the data be output in correct Vuo parlance? (if formatted correctly)? Just playing with the new 1.2 A4, great job guys!

Uninstall kineme filetools