some doubts

[ixdi]

Some doubts,

Do you think JSON-Stat is suitable to save stats created dinamically ?

It seems to me that create dinamically data in JSON-stat is a bit cryptic and I think that there's no library to do that, isn't it ?
Do you think is better to create my own type of data and then transform it or directly represent data in JSON-stat ?

I imagine that later is easy to get some datasets together and plot data. I need to save an object instead of a Number in each value to have more information. For example, in same data position, save timestamp when there's a value addition. I know that I'll have to map returned data. Is there a downside to that ??

Thanks!

[badosa]

Do you think JSON-Stat is suitable to save stats created dinamically ? It seems to me that create dinamically data in JSON-stat is a bit cryptic and I think that there's no library to do that, isn't it ?

I think the difficulty of dynamically saving stats in JSON-stat depends on the structure of your data: if you have some sort of tabular/cubic structure it's probably not too complicated. The suitability of JSON-stat for such a task has to do I think with what you want to do with the data and whether you can benefit from the JSON-stat Javascript Toolkit or not.

I imagine that later is easy to get some datasets together and plot data. I need to save an object instead of a Number in each value to have more information.

JSON-stat supports two properties for each cell: "value" and "status". Both are type-agnostic: "value" doesn't have to be a number; "status" doesn't have to a string. Both can be objects. In your case, you can probably choose between putting your object in the "value" property or just putting the number alone and storing the rest in the "status" property. See this post for more info.

BTW, the JSON-stat Google Group is probably the best place to discuss this issue, as the JSON-stat GitHub repo is dedicated to the JSON-stat Javascript Toolkit.