<div>(from Sébastien:) </div><blockquote class="gmail_quote" style>We were thinking that a simple JSON file would save a lot of trouble :<br>- it has a nested structure, which allows for much clearer, even human-readable format. ex :<br>
[<br> {"class": "obj", "id": 0, "type": "osc~", "args": [440]},<br> {"class": "obj", "id": 1, "type": "dac~"},<br>
{"class": "connect", "from": [0, 0], "to": [1, 0]},<br> {"class": "connect", "from": [0, 0], "to": [1, 1]}<br>]<br><br>- it allows putting custom attributes (for a GUI for example) :<br>
[<br> {"class": "obj", "id": 0, "type": "osc~", "args": [440],<br> "myGui": {"x": 123, "y": 78}<br> }<br>]<br><br></blockquote>
<div style><br></div><div style>Strict json has a dictionary as it's outermost object. Most parsers will accept an array as you have done, but not all (Obj-C's TouchJSON as an example). An alternative way to organize the patch and adhere to strict json would be to have id's on the outside, such as:</div>
<div style><br></div><div style><div>{</div><div><span style="white-space:pre-wrap"> </span>"canvas" :</div><div><span style="white-space:pre-wrap"> </span>{</div><div><span style="white-space:pre-wrap"> </span>"id" : 1,</div>
<div><span style="white-space:pre-wrap"> </span>"name" : "example"</div><div><span style="white-space:pre-wrap"> </span>"x" : 95,</div><div><span style="white-space:pre-wrap"> </span>"y" : 190,</div>
<div><span style="white-space:pre-wrap"> </span>"width" : 809,</div><div><span style="white-space:pre-wrap"> </span>"height" : 538</div><div><span style="white-space:pre-wrap"> </span>"elements" :</div>
<div><span style="white-space:pre-wrap"> </span>{</div><div><span style="white-space:pre-wrap"> </span>"obj" : {"id" : 0, "type": "osc~", "args": [440]},</div><div><span style="white-space:pre-wrap"> </span>"obj" : {"id" : 1, "type": "dac~"},</div>
<div><span style="white-space:pre-wrap"> </span>"connect" : {"from": [0, 0], "to": [1, 0]},</div><div><span style="white-space:pre-wrap"> </span>"connect" : {"from": [0, 0], "to": [1, 1]}</div>
<div><span style="white-space:pre-wrap"> </span>}</div><div><span style="white-space:pre-wrap"> </span>"canvas" : { ... }</div><div><span style="white-space:pre-wrap"> </span>"array" : { ... }</div>
<div><span style="white-space:pre-wrap"> </span>}</div><div>}</div></div><div style><br></div><div style>About the optional GUI, my opinion is that pd is firstly a graphical data flow language existing of canvases and objects with specific location. To make the dimensions optional means interoperability with pd will be optional, probably not so good. If you need extra info, I think that's ok, but at a minimum the information in existing pd patches should be represented.</div>
<div style><br></div><div style>You could also pull the GUI locations into a separate object:</div><div style><br></div><div style><div>{</div><div><span style="white-space:pre-wrap"> </span>"canvas" :</div><div>
<span style="white-space:pre-wrap"> </span>{</div><div><span style="white-space:pre-wrap"> </span>"id" : 0,</div><div><span style="white-space:pre-wrap"> </span>"name" : "example"</div><div>
<span style="white-space:pre-wrap"> </span>"elements" :</div><div><span style="white-space:pre-wrap"> </span>{</div><div><span style="white-space:pre-wrap"> </span>"obj" : {"id" : 0, "type": "osc~", "args": [440]},</div>
<div><span style="white-space:pre-wrap"> </span>"obj" : {"id" : 1, "type": "dac~"},</div><div><span style="white-space:pre-wrap"> </span>"connect" : {"from": [0, 0], "to": [1, 0]},</div>
<div><span style="white-space:pre-wrap"> </span>"connect" : {"from": [0, 0], "to": [1, 1]}</div><div><span style="white-space:pre-wrap"> </span>}</div><div><span style="white-space:pre-wrap"> </span>"layout" :</div>
<div><span style="white-space:pre-wrap"> </span>{</div><div><span style="white-space:pre-wrap"> </span>"0" : { "pos": [123, 78] },</div><div><span style="white-space:pre-wrap"> </span>"1" : { "pos": [123, 100] }</div>
<div><span style="white-space:pre-wrap"> </span>}</div><div><span style="white-space:pre-wrap"> </span>}</div><div><span style="white-space:pre-wrap"> </span>"layout" :</div><div><span style="white-space:pre-wrap"> </span>{</div>
<div><span style="white-space:pre-wrap"> </span>"0" : { "pos": [95, 190], "size" : [809, 538] }</div><div><span style="white-space:pre-wrap"> </span>}</div><div>}</div></div><div style><br></div>
<div style>Don't know if it's better or worse, just throwing it out there. One side effect is that the id's here are both in string and int format.</div><div style><br></div><div style> </div><blockquote class="gmail_quote" style>
<div><br>----------------------------------------------------------------------<br><br></div><div>Comment By: Andras Muranyi (muranyia)<br></div>Date: 2012-06-01 14:00<br><br>Message:<br>@reakin: when mentioning two files for one patch i was referring to the<br>
(nice and convenient) idea of separating logic from presentation by<br>breaking out GUI info into a CSS-like file - which means having two files<br>per patch (not so convenient and nice). <div><br></div></blockquote><div style>
<br></div><div style>Ah, understood. I also think this would be a bit overcomplicated. If it's separated, I think the GUI info could just be under a different object in the json of one file.</div><div style> </div><div style>
Cheers,</div><div style>Rich</div><br><div class="gmail_quote">On Sat, Jun 2, 2012 at 2:01 PM, yvan volochine <span dir="ltr"><<a href="mailto:yvan.pd@gmail.com" target="_blank">yvan.pd@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 06/02/2012 07:50 PM, s p wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So, ... moving the discussion here from sourceforge's tracker :<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
@Sébastien will you write a .json -> .pd converter too?<br>
</blockquote>
<br>
Rich, notice the double arrow ".json<-> .pd" ;)<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
the proposal is for a new, easier to read / parse, format for existing<br>
</blockquote>
patches. This facilities writing/reading patches in other languages (such<br>
as javascript, C / C++ / Obj-C / Java, etc.), since you wouldn't need to<br>
write the text file in a cryptic form.<br>
</blockquote>
<br></div>
I am certainly not a pd-veteran but I think this is a *very good* idea.<span class="HOEnZb"><font color="#888888"><br>
<br>
y<br>
<br>
-- <br>
<a href="http://yvanvolochine.com" target="_blank">http://yvanvolochine.com</a><br>
<a href="http://vimeo.com/yv" target="_blank">http://vimeo.com/yv</a><br>
<a href="http://soundcloud.com/yvanvolochine" target="_blank">http://soundcloud.com/<u></u>yvanvolochine</a><br>
<br>
______________________________<u></u>_________________<br>
Pd-dev mailing list<br>
<a href="mailto:Pd-dev@iem.at" target="_blank">Pd-dev@iem.at</a><br>
<a href="http://lists.puredata.info/listinfo/pd-dev" target="_blank">http://lists.puredata.info/<u></u>listinfo/pd-dev</a><br>
</font></span></blockquote></div><br>