Hi Lindon,
long time no see
The internal JSON list will indeed be accessible only via the UI elements. However when you save them / load them it will be stored directly in the XML element (I've played around and this is much more versatile as it allows sharing of modules without having to rely on another JSON file like David suggested).
This is an example script with one Knob that has it's max property set to 40:
<Processor Type="ScriptProcessor" ID="Interface" Bypassed="0" Script="Content.makeFrontInterface(600, 500); const var Knob = Content.addKnob("Knob", 37, 20); // [JSON Knob] Content.setPropertiesFromJSON("Knob", { "max": 40 }); // [/JSON Knob]function onNoteOn() { 	 } function onNoteOff() { 	 } function onController() { 	 } function onTimer() { 	 } function onControl(number, value) { 	 } ">
<EditorStates BodyShown="1" Visible="1" Solo="0" contentShown="1" onInitOpen="1"
Folded="1"/>
<ChildProcessors/>
<Content>
<Control type="ScriptSlider" id="Knob" value="0"/>
</Content>
</Processor>
As you can see, it stored the JSON data in the script with some weird white space replacements that are terrible to the human eyes
Now it looks like this:
<Processor Type="ScriptProcessor" ID="Interface" Bypassed="0" Script="Content.makeFrontInterface(600, 500); const var Knob = Content.addKnob("Knob", 31, 19); function onNoteOn() { 	 } function onNoteOff() { 	 } function onController() { 	 } function onTimer() { 	 } function onControl(number, value) { 	 } ">
<EditorStates BodyShown="1" Visible="1" Solo="0" contentShown="1" onInitOpen="1"
Folded="1"/>
<ChildProcessors/>
<Content>
<Control type="ScriptSlider" id="Knob" value="0"/>
</Content>
<ContentProperties>
<Knob type="ScriptSlider" max="40"/>
</ContentProperties>
</Processor>
Now there's just another child element called ContentProperties which contains all non-default values. No more weird JSON comments / autogenerated boilerplate stuff in the script.
Basically, this adds another data layer before the script code. If you don't need it, it won't change anything for you (you can still set the properties using Javascript). The problem was that the UI widgets (the property list, the dragger, etc) had no own data model so they kept interfering with the script which was a theoretically nice idea, but very error prone.
I will also add some functions that update / change the "global" UI data object using a JSON from Javascript. I'll also think about some handy migrating tools in case you want to switch your UI to the new scheme. In fact, I think this scheme will be even better for important any kind of autogenerated data.
The only breaking change so far is that if your interface was creating only by using the autogenerated JSON data from the property list, it will become some sort of "read-only", which means that it still loads the correct properties, but the property lists (and the UI dragger) will not change the JSON code anymore, because their property changes get overwritten by the already existing JSON data.
