Mail Archives: geda-user/2012/10/29/05:11:55
This is a multi-part message in MIME format.
--------------010300030809010304040302
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
On 10/28/2012 01:13 AM, Bert Timmerman wrote:
>
> KiCad does that with integration of schematic capture + PCB layout +
> 3D views and models,
>
> gEDA-tools do that with ... letting the user find his way in a maze of
> dispersed tools.
Perhaps the easier option is to port gEDA's best features to Kicad?
As far as I understand, the reason to do any of this is to get more
users and more developers. But I think the former is hampered by the
command-line focus and operating-system near-dependency and the latter
by a mish-mash of older libraries in straight-up C.
You could go to all the work to reinvent the smooth flow done in Kicad,
but it'll still be an unsexy codebase and you'd just be duplicating work.
The biggest pain for me is creating new parts. If there was just one
global database that held everybody's parts, that you could search by
part number and edit at will, and -- here's the best part -- be able to
work with multiple EDA tools, it wouldn't matter much whether people
were using gEDA or Kicad or upverter or whatever, because when someone
adds a part to Kicad, I get it too. It certainly would be less work than
integrating gschem & pcb, and a heck of a lot more useful! Basically
DJ's idea http://www.delorie.com/pcb/component-dbs.html except one
database for everyone, pull data from vendors/octopart automatically
when creating a symbol (i.e. if I type "OPA330AIDBVT
<http://www.digikey.com/product-detail/en/OPA330AIDBVT/296-25307-2-ND/2179354>"
it should already pre-fill the SOT23-5 footprint), have a very easy way
to fill the mapping between symbol and footprint, and be able to record
when a component is verified in a very easy manner (like after a board
is populated and all the parts fit, I should be able to point a program
at my project and have it tell the database that all the parts in the
project are correct).
I'm not up to doing it myself, yet. :(
Cory
--------------010300030809010304040302
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 10/28/2012 01:13 AM, Bert Timmerman wrote:
<blockquote cite="mid:508CE947 DOT 4050408 AT xs4all DOT nl" type="cite"><br>
KiCad does that with integration of schematic capture + PCB layout
+ 3D views and models,
<br>
<br>
gEDA-tools do that with ... letting the user find his way in a
maze of dispersed tools.
<br>
</blockquote>
<br>
Perhaps the easier option is to port gEDA's best features to Kicad?<br>
<br>
As far as I understand, the reason to do any of this is to get more
users and more developers. But I think the former is hampered by the
command-line focus and operating-system near-dependency and the
latter by a mish-mash of older libraries in straight-up C.<br>
<br>
You could go to all the work to reinvent the smooth flow done in
Kicad, but it'll still be an unsexy codebase and you'd just be
duplicating work.<br>
<br>
The biggest pain for me is creating new parts. If there was just one
global database that held everybody's parts, that you could search
by part number and edit at will, and -- here's the best part -- be
able to work with multiple EDA tools, it wouldn't matter much
whether people were using gEDA or Kicad or upverter or whatever,
because when someone adds a part to Kicad, I get it too. It
certainly would be less work than integrating gschem & pcb, and
a heck of a lot more useful! Basically DJ's idea
<a class="moz-txt-link-freetext" href="http://www.delorie.com/pcb/component-dbs.html">http://www.delorie.com/pcb/component-dbs.html</a> except one database
for everyone, pull data from vendors/octopart automatically when
creating a symbol (i.e. if I type "<a itemprop="url"
href="http://www.digikey.com/product-detail/en/OPA330AIDBVT/296-25307-2-ND/2179354"><span
itemprop="name">OPA330AIDBVT</span></a>" it should already
pre-fill the SOT23-5 footprint), have a very easy way to fill the
mapping between symbol and footprint, and be able to record when a
component is verified in a very easy manner (like after a board is
populated and all the parts fit, I should be able to point a program
at my project and have it tell the database that all the parts in
the project are correct).<br>
<br>
I'm not up to doing it myself, yet. :(<br>
<br>
Cory<br>
</body>
</html>
--------------010300030809010304040302--
- Raw text -