On 9/6/10, Peter Clifton pc...@cam.ac.uk wrote:
...
confusing non-copper with skip-drc is
probably a bad idea.
...
Thank you, your suggestion is really reasonable.
I renamed the attribute to PCB::non-copper
and corrected the variable name and comments accordingly;
probably it does not make the
On Mon, 6 Sep 2010 22:18:18 -0400
DJ Delorie d...@delorie.com wrote:
How about this: Let footprints contain a file name of an macro image
from the top. Then, the photo mode could use the image to render a
populated board. ;-)
I thought of that, but you need to be able to correctly align
On Mon, 6 Sep 2010 16:32:10 -0400
DJ Delorie d...@delorie.com wrote:
Arcs can be simulated with many short lines, so the only primitive we
need are lines. Of course, if line is a two-point polygon, then the
only primitive we need is polygons.
So, your pcb file would contain nothing but
On Mon, Sep 6, 2010 at 10:09 PM, Eric Brombaugh ebrombau...@cox.net wrote:
Whenever I post pix from photo mode I always get questions about what tool I
used to do them. Surprising that none of the big pro tools out there provide
that. Who says OSS apps always follow the lead of the
On Sep 6, 2010, at 8:31 PM, Rick Collins wrote:
I have often thought that I would prefer to write an HDL that works like
Forth.
I believe Chuck Moore (the inventor of Forth) beat you to it.
http://www.colorforth.com/vlsi.html
John Doty Noqsi Aerospace, Ltd.
On Tue, 2010-09-07 at 06:56 +, Ineiev wrote:
On 9/6/10, Peter Clifton pc...@cam.ac.uk wrote:
...
confusing non-copper with skip-drc is
probably a bad idea.
...
Thank you, your suggestion is really reasonable.
I renamed the attribute to PCB::non-copper
and corrected the variable
I think (hope) DJ was being sarcastic
I was.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
I might have put the attribute string PCB::non-copper in a #define
somewhere, but if the string is canonical, I guess it doesn't hurt to
place it explicitly in the code.
Perhaps we should tell DRC about all sorts of attributes? Then we can
do layer-specific ones. I'd want to use DRC::* at
Shall we / I push this? I think it looks good overall.
I desparately need to push out a release to get the LF work
published in order to close it out. Maybe I'll do a 1.99za release
just to accomplish those goals, then we can cram in all the new
functionality we can for the 4.0 release. Let's
DJ Delorie wrote:
How about this: Let footprints contain a file name of an macro image
from the top. Then, the photo mode could use the image to render a
populated board. ;-)
I thought of that, but you need to be able to correctly align the
photo with the rotated/positioned element
On 09/05/2010 10:21 AM, Bert Timmerman wrote:
On 09/04/2010 10:19 PM, Andrew Poelstra wrote:
I have one more suggestion: the facility to create recursive PCBs.
Recursive PCBs could work the same way as the footprint
re-use: a node could contain a reference to a parent node;
the parent node
On Sep 7, 2010, at 9:01 AM, DJ Delorie wrote:
* Real layer types. Silks, keepouts, docs at least. Maybe anti-draw
or paste.
How about mask keepout layers? I have to manually merge gerbers to get my
negative-tone unmasked regions now. This would be *huge*.
Noted.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
On 09/07/2010 11:01 AM, DJ Delorie wrote:
My 4.0 short list is:
* More route styles. Four is *way* too few for me.
Yep.
* Real layer types. Silks, keepouts, docs at least. Maybe anti-draw
or paste.
A layer that is insulator would be good for printed conductive traces,
printed
On 07/09/10 18:01, DJ Delorie wrote:
Shall we / I push this? I think it looks good overall.
I desparately need to push out a release to get the LF work
published in order to close it out. Maybe I'll do a 1.99za release
just to accomplish those goals, then we can cram in all the new
On 09/07/2010 04:49 PM, Link wrote:
Some things I regard as quite important:
* Variable-angle arcs. 90 degrees is extremely limiting. gschem does
this right.
* Filled circles, sans kludge. :)
If you think in terms of gerber output history, everything's a kludge, so I'd
lower this
Sounds nice -- could come from DJ upgrading GTK functionality.
I was hoping someone else would do the GTK stuff :-)
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
On 09/07/2010 06:24 PM, DJ Delorie wrote:
Sounds nice -- could come from DJ upgrading GTK functionality.
I was hoping someone else would do the GTK stuff :-)
Oh, I suppose I could, I just need more economic stability first.
John
___
geda-user
On Tue, Sep 07, 2010 at 07:24:38PM -0400, DJ Delorie wrote:
Sounds nice -- could come from DJ upgrading GTK functionality.
I was hoping someone else would do the GTK stuff :-)
I'm working on cleaning up the Gtk code - well, refactoring gui-top-window.c,
anyway. Hopefully I'll be able to
On Sep 7, 2010, at 2:49 PM, Link wrote:
* Trace impedance calculator, with automatic adjustment capability (fill in
thickness, stray capacitance and desired impedance, and the width is adjusted
to satisfy the conditions).
To get this it would be nice to have stackup information with the
On Tue, Sep 7, 2010 at 4:49 PM, Link l...@penguindevelopment.org wrote:
Some things I regard as quite important:
* Variable-angle arcs. 90 degrees is extremely limiting. gschem does this
right.
Yes! Yes! Not all designs are rectilinear.
* Having all shapes that are supported for traces
To get this it would be nice to have stackup information with the
layers, 4 layer board with 1oz copper on the outside and .5oz on the
inside. etc.
I think we decided at some point in the past that the layer *group*
order would be our stackup order, but more information needs to be
added
On 09/07/2010 08:28 PM, Mark Rages wrote:
* Ability to edit netlist in-situ (possibly by drawing on the rat lines
layer) - e.g, when you want to add a heatsink soldered to ground, it will
always show up as shorted until the netlist is edited to incorporate it.
A desirable feature, but
Surely in 2010 there is a portable non-polling way to get file update
notification?
On 8 Sep 2010 09:46, Ethan Swint [1]eswint.r...@verizon.net wrote:
On 09/07/2010 08:28 PM, Mark Rages wrote:
* Ability to edit netlist in-situ (possibly by drawing on the rat
lines
layer) -
Surely in 2010 there is a portable non-polling way to get file update
notification?
More than one, I think...
But any design that requires you to edit files behind pcb's back, is bad.
___
geda-user mailing list
geda-user@moria.seul.org
On Sep 7, 2010, at 6:50 PM, DJ Delorie wrote:
But any design that requires you to edit files behind pcb's back, is bad.
You're not thinking flexible toolkit. You're thinking inflexible integrated
tool.
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
j...@noqsi.com
On 09/07/2010 08:50 PM, DJ Delorie wrote:
Surely in 2010 there is a portable non-polling way to get file update
notification?
More than one, I think...
But any design that requires you to edit files behind pcb's back, is bad.
I text-edit PCB files on every single board I do... arcs
DJ Delorie wrote:
Shall we / I push this? I think it looks good overall.
off the top of my head . . .
A) slots in planes (may be already in the process?)
B) square/rectangular holes (e.g. mounting tabs)
___
geda-user mailing list
On Sep 7, 2010, at 7:21 PM, DJ Delorie wrote:
You're not thinking flexible toolkit. You're thinking inflexible
integrated tool.
I'm thinking two things shouldn't edit the same file at the same time
I don't care what you do when pcb isn't running, but when it is...
The trouble with
The trouble with GUI tools is that they don't just do one thing and
get out of the way. Therefore, a GUI tool has special
responsibilities, including watching the file it's editing.
What? I don't know of any guis that do that. The best I've seen is
the file seems to have changed since the
On Sep 7, 2010, at 7:24 PM, DJ Delorie wrote:
I do stuff like that too, but it's still bad. Way too easy to lose
work by saving one set of changes over another.
But having the GUI tool on alert helps.
Now, if we had an edit the raw pcb file menu option that LOCKED the
file so that you
On Sep 7, 2010, at 7:31 PM, DJ Delorie wrote:
What? I don't know of any guis that do that. The best I've seen is
the file seems to have changed since the last load... are you sure
you want me to overwrite it?
Nedit, for example, watches and pops up a dialog box that says: file has
been
But having the GUI tool on alert helps.
Warning: it's too late to avoid losing your work!
Locks tend to cause more problems than they solve. Ever use RCS?
Yes. It kept me from stomping on my co-workers changes, many times.
Every source control system I know has some sort of mechanism for
Nedit, for example, watches and pops up a dialog box that says:
file has been modified by another program. Reload? with the
appropriate buttons. Not a perfect mechanism, but a useful and
practical one.
And if you've just spent the last hour editing the file, you're
screwed.
On Sep 7, 2010, at 7:38 PM, DJ Delorie wrote:
But having the GUI tool on alert helps.
Warning: it's too late to avoid losing your work!
Locks tend to cause more problems than they solve. Ever use RCS?
Yes. It kept me from stomping on my co-workers changes, many times.
Every source
35 matches
Mail list logo
