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=pbEgQJP0+UoMRKZCeW+S9M7ctjDA4ML4gos/LUFVQdE=; b=sNJN0ASg2PQAiQZlHqobNe7pEQ4CzH1GVyaiO+8+dt51jejf3sK2ZLBL141wx9hMks 4gbmPVoIwecsNvccNGkoiBPW03FmiU1PjESIiVLL/jzi/D3j6ZDyCcGOvPCuOWTaY7Yh z03XSCqosaWDLNi/Gko1TSs5RX5YMnbxlv1Ade5+30cEm2eMQWIvtI4squv4U1xEsZhY 8Hxx2iPZDV7TKkXkVvWyNNji489dZOe30MVvq9XWiRJmAQ+DnyZxbqKCF2/Wv9F/ceyh upKAqN4GUPTBmqC+YfcEtNZVVbXdtf0HhpE8HKX5SeyxfU9HreZ3Cl4zwgA/kgNLO9zL Uiug== MIME-Version: 1.0 In-Reply-To: <20121120022308.1d9f109c@akka> References: <20121116030224 DOT 5c7750ee AT akka> <201211160225 DOT qAG2PrVD005630 AT envy DOT delorie DOT com> <20121116035513 DOT 14519 DOT qmail AT stuge DOT se> <201211160357 DOT qAG3vUXo017504 AT envy DOT delorie DOT com> <20121116041216 DOT 16057 DOT qmail AT stuge DOT se> <201211160428 DOT qAG4Sh3h018631 AT envy DOT delorie DOT com> <20121117163351 DOT 14988 DOT qmail AT stuge DOT se> <5C6FC5CD-A358-476D-A8CA-C9AF2E72A914 AT noqsi DOT com> <20121117185520 DOT 25698 DOT qmail AT stuge DOT se> <9C626D0F-7D63-4FBE-8D63-37A2FFAD96FE AT noqsi DOT com> <20121120022308 DOT 1d9f109c AT akka> Date: Tue, 20 Nov 2012 11:10:27 -0500 Message-ID: Subject: Re: [geda-user] git mirror of gedasymbols.org From: Evan Foss To: geda-user AT delorie DOT com Content-Type: text/plain; charset=ISO-8859-1 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 Mon, Nov 19, 2012 at 8:23 PM, Kai-Martin Knaak wrote: > John Doty schrieb am 18. November 2012: > >> If you treat the gedasymbols tree as an installation target, not a >> development tree, these problems disappear. > > Of course, I do the actual development on my local disk. But at the end > of the day, the result has to enter gedasymbols.org. > > >> >> We should talk some time about adding >> >> spice-prototype attributes to your symbol >> > >> > IMHO, this only makes sense, if they are compllemented by a lib of >> > spice models. >> >> As you know, the primary issue here is legal, > > I firmly believe, that it is possible to assemble generic models that can > be tuned according to data sheet parameters. These may not be the most > efficient, or the most realistic models. But they can provide a starting > point and possibly a seed for better models. This premiss is not going to fly. I have models from manufactures for some analog parts where they bothered to build very large structures in spice one transistor/diode at a time. There is just no way some one bothering to model a circuit would want to turn that down in favor of a generic model. While I can appreciate the importance of building a totally open source library I just can not see investing this level of time. >> I'm also considering the >> possibility of automating the fetch of a model from a URL. > > IMHO, it would be better to provide idealized open source models that > can be modified and improved over time. Download of closed source models > is just a band-aid. To help new users understand spice better I could see building a few heavy symbols of ideal parts into the standard gEDA suite library so that they can see how that works. > ---<)kaimartin(>--- > -- > Kai-Martin Knaak -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/