X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Virus-Scanned: Debian amavisd-new at papyrus.altaweb.hu Date: Sat, 9 Jan 2016 11:28:51 +0100 From: "Kovacs Levente (leventelist AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] (features: layers stack, padstack/vias) Message-ID: <20160109112851.1129dc38@wind.levalinux.org> In-Reply-To: References: <1512221837 DOT AA25291 AT ivan DOT Harhan DOT ORG> <20160106091006 DOT 5F67B809D7A1 AT turkos DOT aspodata DOT se> <20160106133049 DOT 5A0E9809D79B AT turkos DOT aspodata DOT se> <20160106143629 DOT 4D39D809D79B AT turkos DOT aspodata DOT se> <20160106164022 DOT D0D4E809D79B AT turkos DOT aspodata DOT se> <20160106180912 DOT 42ddf4079d91384f206b7c35 AT gmail DOT com> <20160106191433 DOT 5dc5cb59 AT jive DOT levalinux DOT org> <20160106202817 DOT 56197b2c539d426a1b724c9e AT gmail DOT com> <568E09ED DOT 1080508 AT m0n5t3r DOT info> <568E6354 DOT 80302 AT m0n5t3r DOT info> <20160108002640 DOT 03233b24 AT jive DOT levalinux DOT org> <20160108175259 DOT 127a3f073616758434f7edff AT gmail DOT com> <20160109020345 DOT 1e07cb84 AT jive> Organization: logonex.eu X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; i586-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/00jrIsQ8oAZZ4Bjx=2tQ/rB"; protocol="application/pgp-signature" Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk --Sig_/00jrIsQ8oAZZ4Bjx=2tQ/rB Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 8 Jan 2016 20:15:24 -0900 "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" wrote: > The way to think about YAML/JSON is as portable text-based > serialization formats for the couple most popular datatypes that get > built into modern languages, in particular arrays, hashes, and scalar > values (basically numbers and strings). JSON doesn't support native > (non-tree) references so you have to add your own id field if what > you want to refer to doesn't have already have a unique name. YAML > does. JSON is much more common but unfortunately also more noisy. > Some people like the noise because they don't trust any > whitespace-based approach (bad experiences with make). Ok. I try to express my data model in YAML. The only problem is that I don't have any experience in YAML, but hopefully I catch up some in the weekend. Then we might write a library that is able to read write gpcb object to/from either YAML or SQL. It might be double work, but we can make performance te= sts at the end. So could we first think about an API? So we might work together parallel. F= or example, you implement the API in current pcb, and I write the file handler? I think the first step would be to implement the current capability of pcb, and later, when the infrastructure is there, we can fiddle with the GUI and other logic. Another idea came in my mind to separate the exporter HIDs from the main pc= b. For example, the gerber exporter would be a separate piece of program (using shared libraries). Lev --Sig_/00jrIsQ8oAZZ4Bjx=2tQ/rB Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWkODpAAoJECHeg32hsZ8oywQH/jIwlIU5cKY3stZJjIFxND9x xl8z6k+SUU4rXX6CmTdLeVlL3lfZWRQDEk0/Axg7hnIetP8AhOSv6gYGDMxHsoRD QQ66ga/yyOui4Zo3Fe8AxHR87+oYOY9WlAhRVPamIikZ17p7SQdIz47RDgg5w7Hf ltrYPpLK+R4Fxa8rrAVL+KHfRdNcLF6rHhi36vuaKZMC7LqBSYwUuBLbrNjPBh+Y eh+O3T7PHumSGAQNTjZLOOG8vhOC4uDOXbfLWhxhoFIx7jlTebOf2BDIBOQoQzmz 1uETRKGzJoQa0qQpGgIHUqPET5mcdIhndrufJwiYJgsIEUnSMR/u1/O1Q4u+QH8= =b1Wa -----END PGP SIGNATURE----- --Sig_/00jrIsQ8oAZZ4Bjx=2tQ/rB--