[plugin] JSON (import/export/generate/edit/inspect/...)

var count = 0;
for (var p in myObject) {
    if(myObject.hasOwnProperty(p) {
         count++;
    }
}[/code:1eqcbou2]
I could implement that, but I'm not sure if it's a good idea to blend the boundaries between array and object. If the user can get the property count (which shouldn't really be called length) they might be tempted to believe they could loop through properties using indices... well still thinking about it.

Hmm, yeah I might add that as well as "isEmpty" and "Clear" function for array and object. We'll see. Maybe renaming "Length" to "ElementCount" or something more general to cover array and objects with the same function... 
Hmm according to json.org, objects contain "members" whereas arrays contain "elements"... not sure how far I should stick to the vocabulary.
Hmm... "Size" might be better then.

"Star1": {
    "name": "somename",
    "size": "somesize"
      }
"Star2": {
    "name": "somename2",
    "size": "somesize2"
     }[/code:s40yz6be]

I would like to change "Star2" (or any property)  name to something else. I'v been using a workaround simply creating new object  ie. "Star5" and setting it's all properties to "Star2" and deleteting "Star2". but it gets more complicated if I have more properties, objects and arrays belonging to Key I want to rename.

// this creates an empty object
// and put its reference in the variable root
var root = {};

// this creates an object with "name" and "size"
// and  put its reference in the "Star1" property of root
root["Star1"] = {"name":"somename","size":"somesize"};

// "Star1" and "Star2" properties point to the same exact object
root["Star2"] = root["Star1"];

// for example:
root["Star1"]["name"] = "plop";
root["Star2"]["name"] == "plop"; // this will return true ("==" means "is equal?")

// then to finish things up, in javascript you would do:
delete root["Star1"];[/code:3clgjt1x]

Now, the closest thing you can do with the current JSON plugin is:[code:3clgjt1x]-> JSON: Set Value at root["Star1"] to "{""name"":""somename"",""size"":""somesize""}"
-> JSON: Load JSON JSON.ToJson(0,"Star1") at root["Star2"] // the copy
-> JSON: delete root["Star1"][/code:3clgjt1x]
as you notice it's almost the same
The only difference is that after the copy (and before the delete) if you modify the object in "Star1", the one in "Star2" will be left untouched because it's not a reference but a copy.

Modifying the key this way is totally fine, but you have to be carefull because copy is slower than just passing references. And going from an object to a JSON string to a new object is even slower than if you just copied each properties one by one. But it's a lot simpler (:

JSON.ToJson(0,"Star1")[/code:2v4ltxd4]in javascript I in fact do[code:2v4ltxd4]JSON.stringify(this.root["Star1"]);[/code:2v4ltxd4](well not exactly since I loop through the arguments provided to go through the path, but in a nutshell that's what I do)

So yeah, if you already have the JSON string as a template, instead of copying one object into another with that[code:2v4ltxd4]-> JSON: Load JSON at root["Star2"] to JSON.ToJson(0,"Star1")[/code:2v4ltxd4]Doing that:[code:2v4ltxd4]-> JSON: Load JSON at root["Star2"] to myTemplate[/code:2v4ltxd4] (with myTemplate containing the JSON string for your... template) 
would be slightly more efficient but you still will do a javascript JSON.parse(myTemplate) which can potentially be a bit slow as well (meaning slower than just passing references in javascript)

If I rename the Length property I would probably not use ObjectSize but just Size, so you could use it for arrays or objects. (Note that your projects using Length will break when I'll make this change... or I can just set it to deprecated for a while to give you the opportunity to change it)

Not sure I get your thing about ID. If you want to reference a JSON object using some kind of numbering, an array seems ok, you just need that numbering to be consecutive. (well in theory, javascript allows non consecutive indexing but when generating a JSON from that, in chrome at least, you get an array with the holes filled with null)
For example you could do:[code:2v4ltxd4]-> JSON: Create new array at root[]
-> JSON: Create new object at root[2]
-> JSON: Create new object at root[4][/code:2v4ltxd4]but then if you want to get back the JSON you'll get something like[code:2v4ltxd4][null,null,{},null,{}][/code:2v4ltxd4]The other possibility would be to reference them in an object using the ID as a key.

{ "Wizard": {
      "stats":{
         "hp":100,
         "mp":80,
         "int":120,
         "dex":20,
         "str": 10
      },
      "buffs": {
         "hp":10,
         "mp":15,
         "int":10,
         "dex":3,
         "str": 2
      }
   }
}[/code:2xof0hjw]

Let say we want to loop through all the property and display their stats + buffs. It could be done like that:
[code:2xof0hjw]
-> System: set Current Path to root["Wizard","stats"]
+ JSON: foreach current[]  // using foreach root["Wizard","stats"] is broken
  Local text property = ""
  Local number value = 0
  -> System: set property to JSON.CurrentKey
  -> System: set value to JSON.Value(1,CurrentKey)
  -> System: set Current Path to root["Wizard","buffs"] // here you are modifying the looping path
  -> Text: Set text to property & ":" & value& " + " & JSON.Value(1) & " = " & value+ JSON.Value(1)[/code:2xof0hjw]

Here is what will be output in the text object:
[code:2xof0hjw]hp:100 + 10 = 110
mp:15 + 15 = 30
int:10 + 10 = 20
dex:3 + 3 = 6
str:2 + 2 = 4[/code:2xof0hjw]
As you can see, after the first iteration, the loop is in fact looking into the buffs path
and if you doesn't have the same properties in the two path you'll get some NaN or undefined values.

I see two possible solutions to this problem:
 1. have a separated Current Path and Loop Path. As much as it makes sense now, I think it's a very confusing solution. What would be the current[]  in this situation? or maybe I should have root/current/loop... And what happens with nested loops? should I name those path like it's done with for loops and loopindex?... So yeah I'm not too sure about this idea
 2. have the loop reset the Current Path to the original path after each iterations. Good thing is, it's simple and straightforward to implement and use. Bad thing is, any change to the current path you do inside a loop will be lost at the end of the iteration (cannot be saved for later). But I think it's a very specific case and I can easily find a work around using an array in C2 and making a "savePath" and "buildPath" function.[code:2xof0hjw]// Function.Call("loadPath")
+ Function: On "loadPath"
   -> JSON: Set Current Path to root[]
   + Array: For each X element
      -> JSON: Set Current Path to current[Array.CurValue][/code:2xof0hjw][code:2xof0hjw]// Function.Call("savePath","path","you","want","to","save",...)
+ Function: On "savePath"
   -> Array: Set size to (0,1,1)
   + System: Repeat Function.ParamCount times
      -> Array: Push back Function.Param(loopindex) on X axis[/code:2xof0hjw]
Though one weakness is that you can't dynamically save the path because you have no way, during a foreach loop, to know the entire path, you just know the CurrentKey. If you are recursively inspecting an entire unknown JSON it's harder to save a spacific path (probably doable if you save the path constantly during the recursion...)
Maybe I could add a "foreach Node in the path"condition you could call in savePath instead of passing parameters.

Anyway, now, for the real interesting stuff I discovered thanks to your capx:
1. The list of parameters you pass in set Current Path to root["template","folder"], which is internally an array, is in fact built just once, and the same array object is passed over and over each time C2 reaches this action (at least during a given tick).
And the plugin was using this very same array as a current path, and this array was modified when going through your two first foreach.
That's why when you execute the run function a second time, you are already at root["template","folder","object1","path"] instead of root["template","folder"]. The array of argument was modified during the previous run.
Hopefully this is easily solvable by using a copy of this array.
2. A the end you logged properties (0, 1, 2, 3, 4 ,5 ,6)  that didn't really make sense since there were no array in your JSON. And the reason for that is that, in the second run, your first foreach was looping through the value at ["template","folder","object1","path"] which was actually the string "folder2". Javascript often consider strings as arrays of character, so you where looping through the 7 letters and was logging their indices. (which is more an unexpected feature than a bug )