-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-06-03 22:30, s p wrote:
That's a very good point, ... it's a good idea to specify GUI
infos, for better interoperability, but it should be explicitly
said that this is optional information
gui information (e.g. spatial layout) is not
the patch's behaviour depends on the layout
Arr ... that's right !!!
Still, it doesn't mean that the layout is mandatory. It just means that
those infos should be extracted and saved somehow.
This should be pretty simple ... for example, if I think of inlets in a
abstraction, I guess pd infers
On Mon, Jun 4, 2012 at 2:52 AM, IOhannes m zmoelnig zmoel...@iem.at wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-06-03 22:30, s p wrote:
That's a very good point, ... it's a good idea to specify GUI
infos, for better interoperability, but it should be explicitly
said
From: Rich E reakina...@gmail.com
To: IOhannes m zmoelnig zmoel...@iem.at
Cc: pd-dev@iem.at
Sent: Monday, June 4, 2012 12:59 PM
Subject: Re: [PD-dev] [ pure-data-Feature Requests-3531000 ] Proposal for an
alternative file format
On Mon, Jun 4, 2012 at 2:52
Strict json has a dictionary as it's outermost object.
I don't think this is true. I was not sure so I checked the spec :
http://www.ietf.org/rfc/rfc4627.txt?number=4627
and apparently a valid json string is either an array or an object.
Most parsers will accept an array as you have done, but
Question: do you care about backwards compatibility, or is it a non-issue?
-Jonathan
From: s p seb...@gmail.com
To: pd-dev@iem.at
Sent: Sunday, June 3, 2012 9:33 AM
Subject: Re: [PD-dev] [ pure-data-Feature Requests-3531000 ] Proposal for an
alternative
On Sun, Jun 3, 2012 at 9:33 AM, s p seb...@gmail.com wrote:
Strict json has a dictionary as it's outermost object.
I don't think this is true. I was not sure so I checked the spec :
http://www.ietf.org/rfc/rfc4627.txt?number=4627
and apparently a valid json string is either an array or an
what _is_ the array? Is it a patch? A canvas? A file? When you use a
dictionary, the name of the key is helpful in clearing this up.
Well ... this just cosmetics ... I think the array is very flexible, in
that you can just stuff objects in there. And, there will be arrays
anyways. What you
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
(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,
Feature Requests item #3531000, was opened at 2012-05-30 23:49
Message generated for change (Tracker Item Submitted) made by ouiouaa
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=478073aid=3531000group_id=55736
Please note that this message will contain a full
12 matches
Mail list logo
