X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=3NyBDyG9t9ZxCcwNnwl3UHZsvw4wCmLmXtwObaoqZXM=; b=B+dGpEgBcNNMnCu7EFiMtp0hkZonGeA4aW9y1H5PWIGxxt412pAG53IALl53ZxWIEX v31W+P5Dw+boRefQxH82syL0vzK+9feijQuM7yfe4+FMpjZ1s77U3BmcZJMaJNdImMZA 3B4OtDP7Aqz+adgiaUWofR6EXi83BwK/d3fEhroadV4AAZdF4Pi9HztHzDaFwNWcfOID 61aEMFtlZbQRAYbh+RURVmw0NBFFAMEtZy8q5hi+vjDAKm1G1sxpLQQf2gtkVJV0Kvnl tCWR9jPpIiwIF+NAaptLNqIlsPW1WOeouDPzirZw6siWEmnUOWiQEivLM/OvXDx8cOs2 8FyQ== X-Received: by 10.28.184.136 with SMTP id i130mr12369170wmf.96.1452123642968; Wed, 06 Jan 2016 15:40:42 -0800 (PST) Date: Thu, 7 Jan 2016 00:40:41 +0100 From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] A fileformat library Message-Id: <20160107004041.8812ea2779c265f6d827d39a@gmail.com> In-Reply-To: References: <1512221837 DOT AA25291 AT ivan DOT Harhan DOT ORG> <20160105182120 DOT 3237F809D79B AT turkos DOT aspodata DOT se> <8E0210CD-0694-4717-A7B1-3224E39691DA AT sbcglobal DOT net> <20160106095351 DOT 410e3f2407176052d835251e AT gmail DOT com> X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 > > > I recently did a tiny bit of work on the parser in pcb. Of course we > > > should continue to support it, but it's going to be tough to extend it > > > much. It's already overloaded in weird ways (e.g. thermals are parsed as > > > flags, with their own non-flex sub-syntax, even though they don't set any > > > actual flags). If you do extend it you do hard work and still only pcb > > can > > > read it. Of course you still have to teach the innards of pcb about your > > > extensions in order for them to do anything useful. > > > > A good start might be to write down what need to be stored even though > > they are not implemented right now and maybe never will be: > > 1. Padstack, probably as collection of ordinary drawing primitives. > > 2. Local copy and reference so update is possible. > > 3. Net and possible segment attribute for route style, width. > > 4. Net clerances between any net. > > 5. Net clerance classes although (4.) could be extended before entering > > pcb. > > 6. Trace impedance. > > 7. Differential impedance? > > 8. Pin swapping! > > 9. Slot swapping. > > > > Lev did something very like this last time this got discussed as sql > schema. I don't think it had all the above but some of it. > > Britton I wrote down some more in a text files. Would it be possible collect them somewhere there everybody could read them? Nicklas Karlsson