X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: geda-user AT delorie DOT com
From: Peter TB Brett <peter AT peter-b DOT co DOT uk>
Subject: Re: [geda-user] [RFC] Major changes to symbol/schematic libraries in geda-gaf
Date: Sun, 08 Sep 2013 23:02:47 +0100
Lines: 48
Message-ID: <87ppsjas54.fsf@harrington.peter-b.co.uk>
References: <87ob83dodl DOT fsf AT harrington DOT peter-b DOT co DOT uk>
	<201309082106 DOT r88L6uGB008410 AT envy DOT delorie DOT com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
X-Complaints-To: usenet AT ger DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: cpc4-oxfd23-2-0-cust628.4-3.cable.virginmedia.com
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Cancel-Lock: sha1:cxlj0za+ZMxisQdfzTOuip7YX5w=
Reply-To: geda-user AT delorie DOT com

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

DJ Delorie writes:

> There was some discussion of containing resources for multiple tools
> in each "library" such that relationships between tools could prefer
> resources from the "same" library.  Does this new gaf library help
> with that?  Because it would be cool if it did :-)

The geda.conf files are in a standard file format for which there are
many parsers available (it's basically an advanced .ini file), and the
rules for how to interpret the relevant configuration variables are
pretty clear (I hope).  There's no reason in principle why PCB couldn't
use exactly the same library logic as gschem.  You could have a
library.conf with:

  [library]
  mimetypes=3Dapplication/x-geda-symbol;application/x-pcb-footprint

and then put the symbols and footprints all in there together.

> Also, it would be cool if the library "path" included cloud support,
> like http:// and git:// paths.

It would be cool, but I feel like that might be better implemented via
helper daemons that just keep an on-disk library up-to-date.  You
wouldn't need any synchronisation with gschem; the library system would
monitor the filesystem and DTRT when updates occurred (i.e. prompt the
user, probably).

                               Peter

=2D-=20
Dr Peter Brett <peter AT peter-b DOT co DOT uk>

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iEYEARECAAYFAlIs9AcACgkQZ7Gbq7g7vppo7ACfTOsrcGZz6p+Wjn81fJXOytti
FioAn3fBm5TkZrOuBQaCA39QEM2H8HeD
=dVhM
-----END PGP SIGNATURE-----
--=-=-=--