kicad-developers team mailing list archive

[Manveru <manveru@...>]

--000e0cd2a0ecbbbd9a046d908f67 Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

2009/6/30 Lorenzo <lomarcan@...>

>
>
> [...]
>
> Other stuff that could be useful/interesting:
> - Libraries fetched from a DB, like orcad CIS. I don't know if wx has
> standard DB access classes or if we need to choose between
> mysql/postgres/whatever. The important thing is that it has to be a NETWORK
> db. So we could avoid mailing colleagues new libraries and package :D (we
> keep them under svn, by the way) And of course there it would be a lot more
> manageable (aliases, order number and such things)
>
> .
>
> 
>

This was mentioned once in different thread here about improvements. I
perceive this as a large step in direction of cleaning up the mess with the
library structure. Using of the database could help a lot with searching
parts by different criteria like manufacturer, part number, maximum
frequency (if someone who adds the element wants to provide such data from
data sheets). This would allow easy pairing of logical part (on schema) with
some common module (for diodes, transistors, ICs).

-- 
Manveru
jabber: manveru@...
gg: 1624001
http://www.manveru.pl
 --000e0cd2a0ecbbbd9a046d908f67 Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">2009/6/30 Lorenzo <span dir=3D"ltr">&lt;=
<a href=3D"mailto:lomarcan@...";>lomarcan@...</a>&gt;</span><br><block=
quote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 2=
04); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">









<div style=3D"background-color: rgb(255, 255, 255);">


<div style=3D"width: 655px;">
<div style=3D"margin: 0pt; padding: 0pt 25px 0pt 0pt; width: 470px; float: =
left;">


<div>
=20=20=20=20=20=20=20=20=20=20=20=20
<br><br>
=20=20=20=20=20=20
<p>[...]<br>
<br>
Other stuff that could be useful/interesting:<br>
- Libraries fetched from a DB, like orcad CIS. I don&#39;t know if wx has s=
tandard DB access classes or if we need to choose between mysql/postgres/wh=
atever. The important thing is that it has to be a NETWORK db. So we could =
avoid mailing colleagues new libraries and package :D (we keep them under s=
vn, by the way) And of course there it would be a lot more manageable (alia=
ses, order number and such things)<br>

<br></p></div></div>=20

=20=20
=20=20
=20=20
=20=20=20=09=20=20
<div style=3D"clear: both; color: rgb(255, 255, 255); font-size: 1px;">
=20=20=20=20
=20=20=20=20

<div>
</div>.</div>
</div> <img width=3D"1" height=3D"1"> <br>
=09
<div style=3D"color: white; clear: both;"></div>
=09
</div>
=09
=09


=09


=09
=09
=09
=09
=09

</blockquote></div><br>This was mentioned once in different thread here abo=
ut improvements. I perceive this as a large step in direction of cleaning u=
p the mess with the library structure. Using of the database could help a l=
ot with searching parts by different criteria like manufacturer, part numbe=
r, maximum frequency (if someone who adds the element wants to provide such=
data from data sheets). This would allow easy pairing of logical part (on =
schema) with some common module (for diodes, transistors, ICs).<br clear=3D=
"all">
<br>-- <br>Manveru<br>jabber: manveru@...<br> =C2=A0 =C2=A0 gg: 1624=
001<br> =C2=A0 <a href=3D"http://www.manveru.pl";>http://www.manveru.pl</a><=
br>
 --000e0cd2a0ecbbbd9a046d908f67--