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=SFwDcPoB5vNsVsXIqtPNhtamFfPoKxxWBF2Ut6sJBn0=; b=poYQviPM1Wim0x0/ITBc2KUiNIT7CtcXsXrAzikP69o33ybzAUNaLjH+upnQq0rszd QGIyi3qNWSAEmZxUEbUYkdpJ8m6cB1N6sv2Fvmd8S8GPOLCnC8bn3Y/YqJYZ68ThBlOj a8FO0W3RB+BWoARiEmgL6W62bTzJ8nUETb1s2iFR9qT9JXvqTMPuqn7NZdXqg4VXBv+C 9FQDohMAEgCGtYQmAa25mRZ4fDCtPCZIjGCF5+IFuFjRYm4HBpHaoYlY0DrJ59PZ4Q9s 6HxuPpJSD51vrfzTE7C0j9XT/snrEFa6qNZCDkMvWWKcGzo8QV/TrhVw076grg6ow+6J yEjw== MIME-Version: 1.0 X-Received: by 10.107.28.203 with SMTP id c194mr4082108ioc.29.1413489603335; Thu, 16 Oct 2014 13:00:03 -0700 (PDT) In-Reply-To: References: <00E6DEBC-05AB-4079-9E88-152225FF6DDE AT qux DOT com> <87wq80xauh DOT fsf AT hotmail DOT com> Date: Thu, 16 Oct 2014 12:00:03 -0800 Message-ID: Subject: Re: [geda-user] SchemeIt From: Britton Kerin To: geda-user AT delorie DOT com Content-Type: text/plain; charset=UTF-8 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 On Thu, Oct 16, 2014 at 11:32 AM, wrote: > On Thu, 16 Oct 2014, Roger Williams wrote: >> Now, what upverter does offer is a very large component library and handy >> graphical tools to simplify footprint and symbol creation, and tight >> integration between the schematic capture and PCB layout tools. > > Not having libraries that really work and that cover the components we're > using, is a much bigger impediment to collaborative design than not having > application-specific source control integration. Agreed. The huge weakness gEDA has is the total lack of any agreed upon way of reusing component descriptions and subcircuits. Everyone has their own private way of doing it. A short while ago someone came up with IIRC a way to roll component libraries into sch files. This is a step in the right direction. Has anyone gotten around to trying this? I meant to try it but haven't done so, and as usual I'm not sure where the code for it ended up. Britton