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=tTKuvmIYJkPZu3EuIqX3/SoYxFat0IPbMK0nL5qnX38=;
	b=M7hjbIp3Ri5DflmQ2b1ExBFbpEkIxHtuOsDPYFijEK9fEiOy616JO1ICZHda+tuUR1
	+j8qG0kFR1UArHuSBGToz/+G3WLGnwqe+LFrtpd2gMQeOCpgXvkMjKmoRE/RscDXABgF
	WARpnBCk7gMyN5c+NKFWFzdX9F+JXeDHQKWsyIP13zuXtEmge8ou/Q1c0KCZJlOEkpYC
	gyUjnEaihjPT6EXXQBBq0fNMsLN7C7FFqtgK8FnxRXOU3DyxT8zn9AdBAWUYcPVO7xGr
	NI6cexK+8xNzR8mT59BUtXiIzJXI03DkdkrGkRju1irY5lrMZdDvFZmifsf5do8ijQP/
	DNHQ==
X-Received:	by 10.28.47.11 with SMTP id v11mr18729280wmv.27.1450861250179;
	Wed, 23 Dec 2015 01:00:50 -0800 (PST)
Date:	Wed, 23 Dec 2015 10:00:48 +0100
From:	"Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] A fileformat library
Message-Id:	<20151223100048.3cf885ae5b0a359b06d5abc6@gmail.com>
In-Reply-To:	<20151222232230.12633.qmail@stuge.se>
References:	<1512221837 DOT AA25291 AT ivan DOT Harhan DOT ORG>
	<CAJXU7q_mXmipJ1fLvLpuLvnYjktV2SHoA+bG=L5+E-EfdygeOA AT mail DOT gmail DOT com>
	<s6n37uumanm DOT fsf AT blaulicht DOT dmz DOT brux>
	<CAJXU7q_qxdvJaejF-VcY=u7VHZ-zrfrc+Z7-qSwfFyPdy-umxw AT mail DOT gmail DOT com>
	<B02363CD-469D-493A-AC15-1D5DC7836982 AT noqsi DOT com>
	<20151222232230 DOT 12633 DOT qmail AT stuge DOT se>
X-Mailer:	Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version:	1.0
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

> John Doty wrote:
> > > Bonus points for PCB using the core-library too, so it can "give up"
> > > its one preferred on-disk netlist format, and read any useful ones we
> > > care to implement a reader for in the core EDA library.
> > 
> > I’m quite skeptical of a core library. An agreed-upon external data
> > representation is handy, but tool writers will want their own
> > internal representations in their own languages for their own problems.
> 
> The purpose of a core library is to take care of the lower-level
> things required to deal with the external data representation.
> 
> It is key for a core library to make all available data easily usable
> for tool writers, not to enforce a particular internal representation.
> 
> I expect different tools to use the same core library to do different
> things and to use the data provided by the core library in different
> ways.
> 
> 
> //Peter

Yes the library would functions to access the data. Ideally the necessary functions could be found by searching the source code and move already existent functions to a library but in practice I think coding is needed to move out the functions. Once they are moved and listed work could begin to clean up the list of functions.

Yes different tools use the library or data to do different things: graphical output on the screen, gerber output, centroid output, back annotation, graphical representation in file ps/eps/png/... Data also need to be accessed then doing layout such as adding a line/polygon/... moving objects, autoroute, ... For data accessed while doing layout graphical and possible other output should be updated then changed.

I guess there would be functions needed to manipulate data and ideally there would be a notification sent for these using the data then making a change. Output is different, screen need to be updated at once or then all changes have been done while for example gerber output is done manually.

Nicklas Karlsson

- Raw text -