Dear fellow GEDA-users,
Can I get pcb to either treat a layer other than the default silk as
non-metal
(so it would not short pads and mess up nets), or draw different silk
layers
as separate objects, in different colors?
My problem is following:
I have a case consisting of
On Fri, 2010-09-03 at 11:53 +0200, Pawel Kusmierski wrote:
Dear fellow GEDA-users,
Can I get pcb to either treat a layer other than the default silk as
non-metal
(so it would not short pads and mess up nets),
Please note, your SUBJECT may be misleading...
No, currently we have only
On Fri, Sep 3, 2010 at 1:51 PM, Stefan Salewski m...@ssalewski.de wrote:
On Fri, 2010-09-03 at 11:53 +0200, Pawel Kusmierski wrote:
Dear fellow GEDA-users,
Can I get pcb to either treat a layer other than the default silk as
non-metal
(so it would not short pads and mess up
I can't answer your question, but I have one of my own. I use
FreePCB and have requested, along with others, that we be able to
designate layers as documentation such as assembly info, mechanical
details, etc. Is that what you are looking for or do you want these
layers to be usable to
I upgraded my Ubuntu 08.04 to 10.04 and now gschem will not work.
k...@red:/home/backup/Work/BuddiPole/Schematic/condisp $ gschem
condisp-*.sch
gschem: error while loading shared libraries: libltdl.so.3: cannot open
shared object file: No such file or directory
I checked Synaptic Package manager
k...@kdream.com:
k...@red:/home/backup/Work/BuddiPole/Schematic/condisp $ gschem
condisp-*.sch
gschem: error while loading shared libraries: libltdl.so.3: cannot open
shared object file: No such file or directory
...
So do I have to reinstall the whole gEDA system?
You could try to find the
On Fri, Sep 3, 2010 at 6:49 PM, Rick Collins gnuarm.2...@arius.com wrote:
I can't answer your question, but I have one of my own. I use FreePCB and
have requested, along with others, that we be able to designate layers as
documentation such as assembly info, mechanical details, etc. Is that
No, FreePCB is a separate project with no links in any way. I have
used it for a couple of projects and like it pretty well, but it is
hard to get changes made. The developer was on a hiatus for some
time, but is back now. He has a long list of bug fixes and
suggestions people would like to
What are you trying to do? Are you really trying to synthesize your
Verilog design, meaning you are trying to generate a bit stream to
load into your FPGA? Or are you trying to compile and simulate your
Verilog?
Icarus Verilog is mostly a *simulator*, not a synthesizer. There were
some synthesis
On Fri, Sep 03, 2010 at 06:40:05PM +0200, Pawel Kusmierski wrote:
Is anybody willing to elaborate on how difficult would it be
to modify the pcb source code to color-differentiate three or four
silk layers and be able to selectively hide/show them?
It will probably be more work than it
Hey all,
I am working on the structuring PCB files in terms of functional blocks,
and generalizing/extending the DRC rule format. (Things have slowed down
as summer is ending but I am still working on this.)
Mostly I am doing GUI work, since that is more-or-less stateless; I can
spend 20
Andrew Poelstra wrote:
However, this also brings the ability to edit PCB components individually,
which means that some parts could have different layers than others, for
example. And then you have to deal with layer mappings and stuff and it's
a huge complicated mess, both for the
Re: functional blocks
If we contemplate changing the PCB file format, it would be nice if we
went with something that was intrinsically extensible. Knowing that
the 5th element in a list with '[' means clearance is a bad format,
but seeing clearance=5mil in a list of attributes is much better.
DJ Delorie wrote:
If you'd rather work on the GUI, though, that's also a needed project.
It would be nice if the GTK gui supported all the modern Gnome stuff,
like dockable toolbars and menus-with-icons. The SOW has an entry for
that also.
What level of self proving would Andrew need to do
XML? What's wrong with XML? Heavy? How heavy are a few electrons anyway?
There is already a preliminary XML based CAD data spec proposed by
IPC, you know, the guys who write specs for the PCB assembly industry...
I don't know if it is the best thing ever invented and I expect the
spec is
On Fri, Sep 03, 2010 at 11:00:43PM -0400, DJ Delorie wrote:
Re: functional blocks
If we contemplate changing the PCB file format, it would be nice if we
went with something that was intrinsically extensible. Knowing that
the 5th element in a list with '[' means clearance is a bad format,
On Fri, Sep 03, 2010 at 11:29:58PM -0400, Rick Collins wrote:
XML? What's wrong with XML? Heavy? How heavy are a few electrons anyway?
For most data, XML ends up being 50% tags (and 50% data). It's hard to
read for humans, bandwidth-intensive for machines, difficult to parse and
generally
On Fri, Sep 03, 2010 at 04:44:14PM -0700, Andrew Poelstra wrote:
However, this also brings the ability to edit PCB components individually,
which means that some parts could have different layers than others, for
example. And then you have to deal with layer mappings and stuff and
Given the choice between lisp (lol) and xml, the winner is absolutely clear.
There are even less lisp users than there are Linux users, and that's
a sad statistic.
-tc
On Sat, Sep 4, 2010 at 2:16 PM, Rick Collins gnuarm.2...@arius.com wrote:
At 12:11 AM 9/4/2010, you wrote:
On Fri, Sep 03,
If we tagged individual objects with rules it would be difficult to edit
rules in a systemetic way. So I don't think that's a good way to go.
No, we tag objects with rule *names*. Hopefully rules can nest, so
you can have meta-rules like signal-line-rule or 12vac rule.
Without a tag, you'd
1. Refuse to export-as-footprints any PCB with more than one copper
layer. This will likely eliminate the most common problems.
Edge connectors.
___
geda-user mailing list
geda-user@moria.seul.org
The heavy issue is a red herring
The heavy issue impacts the difficulty in using XML as a toolkit.
But I suppose it is better to re-invent the wheel. There is no
reason to try to foster any sort of compatibility in file formats
between all the different CAD tools.
That's a real red
22 matches
Mail list logo
