X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Message-ID: <56A2F648.20903@iee.org>
Date: Sat, 23 Jan 2016 03:40:56 +0000
From: "M. J. Everitt (m DOT j DOT everitt AT iee DOT org) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] sym precedence ordering
References: <20160102091556 DOT BBC6D809D79B AT turkos DOT aspodata DOT se>	<CAJXU7q_Zwyfpcb4g00QCFNTjQ9Le2Tm8WjKz3CKMnNXb7gMceg AT mail DOT gmail DOT com>	<20160102131252 DOT F383A809D79A AT turkos DOT aspodata DOT se>	<CAMvDHVCi5wR78jybhOEG0EmKyqWVpeaoYFuyWkWSrtkxF7kXQw AT mail DOT gmail DOT com>	<20160121144142 DOT 2703D81053E4 AT turkos DOT aspodata DOT se>	<20160121161958 DOT GB4788 AT localhost DOT localdomain>	<20160121174016 DOT E995881053E3 AT turkos DOT aspodata DOT se>	<20160121184048 DOT GD4788 AT localhost DOT localdomain>	<20160121193929 DOT 11E5881053E4 AT turkos DOT aspodata DOT se>	<CAMvDHVB1jRzDJ_sJnpBwT-YEDSphiLLVVsDYW+jKW0NNKTq2dA AT mail DOT gmail DOT com>	<20160122110632 DOT D67C281053E3 AT turkos DOT aspodata DOT se>	<BFF6073F-1240-4BE6-A0BB-92350870F3C4 AT noqsi DOT com>	<20160122223314 DOT 954B681053E4 AT turkos DOT aspodata DOT se> <CAOP4iL2-rnPiLjFN=_nsiQSx=D6ZbDhr-RK7hyYtvLpzDaV_oA AT mail DOT gmail DOT com>
In-Reply-To: <CAOP4iL2-rnPiLjFN=_nsiQSx=D6ZbDhr-RK7hyYtvLpzDaV_oA@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------090109080400070605060100"
X-Provags-ID: V03:K0:YzRsAuYlW4ncDx4jIpUUKgvhdd/fD7OO0Imu3dzTeZcLiKJI3Or
 usoG0VXp8RVxo6Y9CJcinBTaeshEXQN5hbnflHNRG2SnY+0eCab+/JX7mzX3RFYCIspyrP7
 V875Jm4K+pwgCi0095iTTe+A0/fcuf4eqhAtIicV17RQsnnFv1D9GJEtrFp/moYx9T/z6yv
 5KFmXC90RfLmTLiW4pYUw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:Gvs2lgYAMes=:N0wcZCPeonJTboAMRPkVPs
 6UfwBuVJy5WTVZmXL1SQlRCiV03dHilF4rHLGEW0XQwDQ3LGZUvQdzoXY+cKDZWMkOTCE83bG
 hC0AaNWMqfRtMhlMDxE0ZNm/S5DuDcQML//ZVqXc98f3WRwTF46gZIVa5+wdGPnSo1vwfbt8r
 dKC19q2ZFwGqXop3mSYkn6Tvx4BmutuZ/JxY5gEfIu33V8IQrmk9zEICCuai2lBVtwiR3XSTn
 dj1XlZtUKqqlX3Viy4mgJbjY6MYRWVcnfpiZK8EvQmW4GyM29wXVaV/XTR/TwgGb40DNOUtbE
 OI7o7jjUfK+ymUCGQNGWW5QgvtkijtyCWruSYk97E3XAWxRiaPdCgOCnHYWARwGB/JquyObwn
 81qWRtsOCQCycJPiT0T56lxhRaDFan0XPSDn0hR48kl9E93VXik7hDsJPDjONJEDU4Gy6x+8P
 Zblisyp+LdQkU8x6HbKWFZmrZNlhk7jrwiTMXh2nydhM+NSnguqzH0kftoPpzTHxucOKxQazx
 iDY3v/tSHUw2Xh/J0U8NbCfKN2gmZIlc4mSFQOo4AeZpMfnJ6SKakcLlVds1G628NZODyeYLZ
 C3LX3uug6I0nhikedM41DT78yvVEjLVy9f5mQWMFEtUjAON/wDFy8G4CDZVqSCQDu9ywL7Xpd
 fbqOr+nEy2w6d9BzTbZ9MyDZPZ/aUAOH2j42dpP4UWLMWar2bYy0udEBrRb3qnlsUqkRplud6
 bUGaHDpgyGEEbFsT
Reply-To: geda-user AT delorie DOT com

This is a multi-part message in MIME format.
--------------090109080400070605060100
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


On 23/01/16 01:57, Ouabache Designworks (z3qmtr45 AT gmail DOT com) [via
geda-user AT delorie DOT com] wrote:
>
>
> On Fri, Jan 22, 2016 at 2:33 PM, <karl AT aspodata DOT se
> <mailto:karl AT aspodata DOT se>> wrote:
>
>
>
>     Though, in the lib.browser, you can choose any one, even the ones
>     deep down the list. Then when you late open the sch, you'll get the
>     wrong syms. And that is not how it should be, precedence order or not.
>
>     I propose that the C (component) syntax be augmented whith some
>     optional selector, so can get  the right one.
>
>      In
>     $ grep ^C regulator.sch | grep -i diode | head -1
>     C 16600 76400 1 0 0 diode.sym
>
>     why not append e.g. author="Karl Hammar", to select the diode.sym
>     which has the attribute given.
>
>     Regards,
>     /Karl Hammar
>
>     -
>
>
> Thats how IP-Xact does it. It has fields for component name, library
> name and vendor name for that reason.
> Search paths should only be used to initially find a component and
> never used to load a schematic. Two designers
> with the same schematic and different rc files will have two different
> designs
>
>
> John Eaton
>
>
This is why its quite important to define a project file, and its
subdirectories (imho) where you distribute/share the entire
schematic/symbols/pcb layout/footprints hierarchy all as one (as I do).

I'm not sure there's a way to force geda ONLY to use the libraries in
the project/config file though .. this would be a really handy feature
if we re-write sections of the library code to facilitate, say, library
limits per schematic/project.

I do like the idea of further tagging the symbols, but I think we're
gonna hit library implementation 'walls'. Good to have the discussion
though.

MJE

--------------090109080400070605060100
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <div class="moz-cite-prefix">On 23/01/16 01:57, Ouabache Designworks
      (<a class="moz-txt-link-abbreviated" href="mailto:z3qmtr45 AT gmail DOT com">z3qmtr45 AT gmail DOT com</a>) [via <a class="moz-txt-link-abbreviated" href="mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>] wrote:<br>
    </div>
    <blockquote
cite="mid:CAOP4iL2-rnPiLjFN=_nsiQSx=D6ZbDhr-RK7hyYtvLpzDaV_oA AT mail DOT gmail DOT com"
      type="cite">
      <div dir="ltr"><br>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Fri, Jan 22, 2016 at 2:33 PM, <span
              dir="ltr">&lt;<a moz-do-not-send="true"
                href="mailto:karl AT aspodata DOT se" target="_blank">karl AT aspodata DOT se</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
              <br>
              Though, in the lib.browser, you can choose any one, even
              the ones<br>
              deep down the list. Then when you late open the sch,
              you'll get the<br>
              wrong syms. And that is not how it should be, precedence
              order or not.<br>
              <br>
              I propose that the C (component) syntax be augmented whith
              some<br>
              optional selector, so can get  the right one.<br>
              <br>
               In<br>
              $ grep ^C regulator.sch | grep -i diode | head -1<br>
              C 16600 76400 1 0 0 diode.sym<br>
              <br>
              why not append e.g. author="Karl Hammar", to select the
              diode.sym<br>
              which has the attribute given.<br>
              <br>
              Regards,<br>
              /Karl Hammar<br>
              <br>
              -<br>
            </blockquote>
            <div><br>
            </div>
            <div>Thats how IP-Xact does it. It has fields for component
              name, library name and vendor name for that reason.<br>
            </div>
            <div>Search paths should only be used to initially find a
              component and never used to load a schematic. Two
              designers<br>
            </div>
            <div>with the same schematic and different rc files will
              have two different designs<br>
            </div>
            <div><br>
              <br>
            </div>
            <div>John Eaton<br>
              <br>
              <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    This is why its quite important to define a project file, and its
    subdirectories (imho) where you distribute/share the entire
    schematic/symbols/pcb layout/footprints hierarchy all as one (as I
    do).<br>
    <br>
    I'm not sure there's a way to force geda ONLY to use the libraries
    in the project/config file though .. this would be a really handy
    feature if we re-write sections of the library code to facilitate,
    say, library limits per schematic/project.<br>
    <br>
    I do like the idea of further tagging the symbols, but I think we're
    gonna hit library implementation 'walls'. Good to have the
    discussion though.<br>
    <br>
    MJE<br>
  </body>
</html>

--------------090109080400070605060100--