So, ... moving the discussion here from sourceforge's tracker :
@Sébastien will you write a .json - .pd converter too?
Rich, notice the double arrow .json - .pd ;)
the proposal is for a new, easier to read / parse, format for existing
patches. This facilities writing/reading patches in other
On 06/02/2012 07:50 PM, s p wrote:
So, ... moving the discussion here from sourceforge's tracker :
@Sébastien will you write a .json - .pd converter too?
Rich, notice the double arrow .json- .pd ;)
the proposal is for a new, easier to read / parse, format for existing
patches. This
(This was on the sourceforge feature requests, I'm taking the liberty to
move it directly to pd-dev)
Initial Comment:
Hi all !
With several people from *libpd* and other *pd* offsprings, we have been
thinking that it would be great to have an alternative format for pd files
(see:
(from Sébastien:)
We were thinking that a simple JSON file would save a lot of trouble :
- it has a nested structure, which allows for much clearer, even
human-readable format. ex :
[
{class: obj, id: 0, type: osc~, args: [440]},
{class: obj, id: 1, type: dac~},
{class: connect,
