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: amavisd-new at neurotica.com X-NSA-prism-xkeyscore: I do not consent to surveillance, prick X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=neurotica.com; s=default; t=1436294003; bh=bZ4EkWCKrSXK+jjaN4jBnHkdq6utCekZVE8ZfFytEpE=; h=Date:From:To:Subject:References:In-Reply-To; b=ANoWR4lFurlq/LLHwaeivraHv9zTkHM7fYjI5vG5RTLbjhBYNLGveu+AkAt7ow/6H X05WRwLv6OtjmT24+kqQxI9Fj+nR1+1MhDUs61hI7HBjCrOYHEX4uR1rSwxYmvU97Z 1bXG0jOw7w1Tbjslc6m1Gt+etq0WTj20wGxWcA40= Message-ID: <559C1B73.7040506@neurotica.com> Date: Tue, 07 Jul 2015 14:33:23 -0400 From: "Dave McGuire (mcguire AT neurotica DOT com) [via geda-user AT delorie DOT com]" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] gEDA/gschem still alive? References: <1435510363 DOT 682 DOT 26 DOT camel AT ssalewski DOT de> <20150703030409 DOT 32398 DOT qmail AT stuge DOT se> <1436006726 DOT 677 DOT 13 DOT camel AT ssalewski DOT de> <20150706200609 DOT GD24178 AT localhost DOT localdomain> <20150707060409 DOT GB14357 AT localhost DOT localdomain> <559C0F7D DOT 4020600 AT neurotica DOT com> <201507071805 DOT t67I5tFG012669 AT envy DOT delorie DOT com> In-Reply-To: <201507071805.t67I5tFG012669@envy.delorie.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Reply-To: geda-user AT delorie DOT com On 07/07/2015 02:05 PM, DJ Delorie wrote: >> This is an excellent approach if done properly. One might follow a >> keyword-based "data sources" approach. For example, a component library >> search path might look something like this: >> >> /usr/local/geda/symbols;mysql:::;/foo/bar > > Let's not reinvent *this* wheel too. If we do anything other than > "local directories", we should use URLs, which take care of all the > path handling, authentication (for http/https, possibly others) and > parameterization, and allow us to use plug-ins to add more handlers > (like msql://), plus give us a protocol for transmitting data back and > forth (when remote). > > file:///usr/local/geda/symbols > mysql://localhost/?t=&etc > http://gedasymbols.org/symdb.cgi/74series/ > m4:/~dj/pcb/footgen.m4 > scheme:(gnetlist-spice-export) > > etc That'd work too. But nothing else I've seen (that I can recall offhand anyway) has used URLs, and I have to believe there was a reason behind it. I myself am not opposed to it, even though URL syntax is really quite gross. -Dave -- Dave McGuire, AK4HZ New Kensington, PA