Mail Archives: geda-user/2016/01/22/22:41:30
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"><<a moz-do-not-send="true"
href="mailto:karl AT aspodata DOT se" target="_blank">karl AT aspodata DOT se</a>></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--
- Raw text -