X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f Date: Tue, 7 Jul 2015 14:05:55 -0400 Message-Id: <201507071805.t67I5tFG012669@envy.delorie.com> From: DJ Delorie To: geda-user AT delorie DOT com In-reply-to: <559C0F7D.4020600@neurotica.com> (geda-user@delorie.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> 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 > 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