X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=bFuVy/EUPSp44q7ERo/rGv7rKCyKN97AqfF7vul5FUo=;
        b=mmNCI0iMN/n44XzWnYgZicxx+wvmOQjOkj0IZfp9NGEjO34B3ahl9ECbvUjEQfKRvQ
         75ETJUp7lGAzwq1JvPsFtqFopG1Bu9q2gqNfhtfcsvt/CUwyYp9Ct4trGyCAauz8Pu1H
         rcQZU2ePw6CVLF0sS+JR/QagSVVFkyjXOqAA5qGVHV3eWuxGXxu37MGfI7F1zwDBaHWs
         QA8D/zmzN2IUyv+YvjJ/sqmieotw3XAEpOWTaSHNXid0ilEl6rZ9za12GsJkd06Mb2+/
         leROVLhNI45W0yUtxfoNejnL78lwgmux2qyXA3SPnXagqaRYKD/50+BBNAlgOEdGI+5W
         nwsg==
MIME-Version: 1.0
X-Received: by 10.42.167.8 with SMTP id q8mr77070236icy.94.1427925097649; Wed,
 01 Apr 2015 14:51:37 -0700 (PDT)
In-Reply-To: <551C574F.2030708@xs4all.nl>
References: <1427905808 DOT 32608 DOT 60 DOT camel AT benjamin-hp-g70>
	<20150401214846 DOT 5d2261e6 AT jive>
	<201504011954 DOT t31JsnKh020289 AT envy DOT delorie DOT com>
	<20150401221210 DOT 1b4a299e AT jive>
	<201504012014 DOT t31KEq1m020861 AT envy DOT delorie DOT com>
	<551C574F DOT 2030708 AT xs4all DOT nl>
Date: Wed, 1 Apr 2015 17:51:37 -0400
Message-ID: <CA+uY=MTgd=aS-vyUE8RHcHZr+dJjtBe_h4yAFANPi6VBPUPVhQ@mail.gmail.com>
Subject: Re: [geda-user] PCB and gschem libraries
From: Russell Nelson <russnelson AT gmail DOT com>
To: geda-user AT delorie DOT com
Content-Type: multipart/alternative; boundary=90e6ba6e83c4363f600512b0b8e5
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

--90e6ba6e83c4363f600512b0b8e5
Content-Type: text/plain; charset=UTF-8

IMHO, the gedasymbols library is fine. If it were easier to use, people
would use it more. Here is what I suggest:
  o Take the current set of symbols and footprints and incorporate them
into gedasymbols.
  o Nuke the current set of symbols and footprints.
  o Replace it by a cached copy of gedasymbols.
  o Make it easy to refresh the cached copy using, say, rsync or somesuch.
  o ONLY, and I mean ONLY pull footprints out of the cached copy.

In other words, when you create a footprint or symbol, the only way to use
it is to pull it out of gedasymbols. So when you create a symbol or
footprint, you can simultaneously creating it on gedasymbols. If you happen
to be offline, well, you can pull it out of your cached copy. But when you
refresh, the refresh works bidirectionally. Everything you've created
becomes available to everyone else.

Yes, I realize that, for constructed symbols, the gedasymbols library will
blow up. Oh well. As long as the constructed symbols have reasonable names,
people will be able to find them.

On Wed, Apr 1, 2015 at 4:38 PM, Bert Timmerman <bert DOT timmerman AT xs4all DOT nl>
wrote:

> DJ Delorie wrote:
>
>> sqlite3?
>>>
>>> I have a bad habit of jumping to the implementation right away.
>>>
>>>
>> I would prefer a text file, like CSV, but...
>>
>> The tricky part isn't the format, it's (1) choosing the right data to
>> store, and (2) getting the data into the apps.
>>
>>
>>
> Hi,
>
> YMMV, maybe GNU rec files could be of any use ?
>
> https://www.gnu.org/software/recutils/
>
> Kind regards,
>
> Bert Timmerman.
>
>
>
>
>

--90e6ba6e83c4363f600512b0b8e5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">IMHO, the gedasymbols library is fine. If it were easier t=
o use, people would use it more. Here is what I suggest:<div>=C2=A0 o Take =
the current set of symbols and footprints and incorporate them into gedasym=
bols.<br></div><div>=C2=A0 o Nuke the current set of symbols and footprints=
.</div><div>=C2=A0 o Replace it by a cached copy of gedasymbols.</div><div>=
=C2=A0 o Make it easy to refresh the cached copy using, say, rsync or somes=
uch.</div><div>=C2=A0 o ONLY, and I mean ONLY pull footprints out of the ca=
ched copy.<br><br>In other words, when you create a footprint or symbol, th=
e only way to use it is to pull it out of gedasymbols. So when you create a=
 symbol or footprint, you can simultaneously creating it on gedasymbols. If=
 you happen to be offline, well, you can pull it out of your cached copy. B=
ut when you refresh, the refresh works bidirectionally. Everything you&#39;=
ve created becomes available to everyone else.<br><br>Yes, I realize that, =
for constructed symbols, the gedasymbols library will blow up. Oh well. As =
long as the constructed symbols have reasonable names, people will be able =
to find them.</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail=
_quote">On Wed, Apr 1, 2015 at 4:38 PM, Bert Timmerman <span dir=3D"ltr">&l=
t;<a href=3D"mailto:bert DOT timmerman AT xs4all DOT nl" target=3D"_blank">bert.timmer=
man AT xs4all DOT nl</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
class=3D"HOEnZb"><div class=3D"h5">DJ Delorie wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
sqlite3?<br>
<br>
I have a bad habit of jumping to the implementation right away.<br>
=C2=A0 =C2=A0 =C2=A0<br>
</blockquote>
I would prefer a text file, like CSV, but...<br>
<br>
The tricky part isn&#39;t the format, it&#39;s (1) choosing the right data =
to<br>
store, and (2) getting the data into the apps.<br>
<br>
=C2=A0 =C2=A0<br>
</blockquote></div></div>
Hi,<br>
<br>
YMMV, maybe GNU rec files could be of any use ?<br>
<br>
<a href=3D"https://www.gnu.org/software/recutils/" target=3D"_blank">https:=
//www.gnu.org/software/<u></u>recutils/</a><br>
<br>
Kind regards,<br>
<br>
Bert Timmerman.<br>
<br>
<br>
<br>
<br>
</blockquote></div><br></div>

--90e6ba6e83c4363f600512b0b8e5--