On Sun, May 29, 2011 at 02:30:08PM +0100, Peter Clifton wrote:
On Sun, 2011-05-29 at 11:37 +1000, Russell Shaw wrote:
Hi,
In _borast_bentley_ottmann_tessellate_bo_edges() which is from
_cairo_bentley_ottmann_tessellate_bo_edges(), i see you deleted
case
On Mon, 2011-05-30 at 09:37 +0200, Gabriel Paubert wrote:
Think i know now. Polygons can't have edges that cross other edges.
You got it.. PCB doesn't allow self intersecting polygons, so I removed
support for rendering them in an attempt to manage the complexity (and
hopefully
On May 29, 2011, at 12:01 AM, Dave McGuire wrote:
This is my opinion, speaking as a professional developer of both hardware
and software: Scheme was a good choice for gEDA, and it should be left alone.
The chosen implementation of Scheme, guile, may not be the best tool for the
job
On 05/30/2011 01:50 AM, John Doty wrote:
But who's volunteering?
On 05/30/2011 01:50 AM, John Doty wrote:
So, one way or another, we're looking at a new tool, I think. Maybe we keep
the old gnetlist around and feed it modified/annotated schematics.
There will always be people who don't
One thought I had for gnetlist backends, is to recode gnetlist as a
set of libraries. The Core would only load the design files
(schematics, spreadsheets, databases, back-annotation info, etc) as
raw data; the backend would be required to call at least one library
function that said I want data
Has anyone successfully built guile 1.8.7 with the latest minipack?
If so, did you encouter theses errors, and how did you work around
them?
With no change to guile.recipe:
configure:19646: checking what kind of threads to support
configure:19648: result: pthreads
configure:19665: checking
On Mon, May 30, 2011 at 10:15 AM, DJ Delorie d...@delorie.com wrote:
Is there a quick way to check to see if a local repo is out of date
relative to a remote repo? I'd like to write a shell script that
rebuilds pcb but only if something's been committed to the master
repo. Rather than check
git remote update origin would be the easiest way.
How is this different than git fetch? Assuming the unneeded branches
aren't huge.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
On Mon, May 30, 2011 at 1:39 PM, DJ Delorie d...@delorie.com wrote:
git remote update origin would be the easiest way.
How about
$ git remote show origin
--wpd
___
geda-user mailing list
geda-user@moria.seul.org
Op donderdag 26-05-2011 om 11:07 uur [tijdzone -0400], schreef DJ
Delorie:
I'd really like to contribute something back -- but as I'm not really a
proficient coder
Contributions come in other forms, Certainly, library work and
documentation are sorely in need of contributors and even
Op donderdag 26-05-2011 om 22:56 uur [tijdzone +1000], schreef Stephen
Ecob:
Then two more usage questions:
- Zero length lines in PCB: I found that when drawing lines in PCB,
sometimes dots (zero length lines) get created inadvertently on corners
and bends. This isn't much of a problem,
- Zero length lines in PCB: I found that when drawing lines in PCB,
I think you're tripping over the metric-rouding bug, where what you're
seeing is lines that are 0.01 mil long. We're working on that with
the metrification of PCB.
Is there already some sort of script to eliminate those
On Tue, May 31, 2011 at 7:21 AM, Richard Rasker ras...@linetec.nl wrote:
Op donderdag 26-05-2011 om 22:56 uur [tijdzone +1000], schreef Stephen
Ecob:
Then two more usage questions:
- Zero length lines in PCB: I found that when drawing lines in PCB,
sometimes dots (zero length lines) get
Op vrijdag 27-05-2011 om 19:56 uur [tijdzone +0100], schreef Peter
Clifton:
On Thu, 2011-05-26 at 10:03 +0200, Richard Rasker wrote:
- Work flow of newer gschem/PCB version: until recently, I worked with
an older PCB version (20080202), but I finally got round to compiling
and installing
On 05/30/2011 11:55 AM, DJ Delorie wrote:
One thought I had for gnetlist backends, is to recode gnetlist as a
set of libraries. The Core would only load the design files
(schematics, spreadsheets, databases, back-annotation info, etc) as
raw data; the backend would be required to call at least
The trace optimizer only touches autorouted tracks by default - if you
want it to work on manually routed traces you need to clear the
Connects - Optimize routed tracks - [/] Only autorouted nets
checkbox.
Thanks for the suggestion, but it messed up the layout something
wicked: over a 100
On Mon, May 30, 2011 at 1:01 PM, DJ Delorie d...@delorie.com wrote:
Has anyone successfully built guile 1.8.7 with the latest minipack?
I just did a fresh checkout of minipack and am not even getting that
far right now:
pango:
Build succeeded.
On Mon, May 30, 2011 at 1:01 PM, DJ Delorie d...@delorie.com wrote:
Has anyone successfully built guile 1.8.7 with the latest minipack?
guile:
Build succeeded.
That part worked fine with the minipack I just pulled.
On May 31, 2011, at 1:55 AM, DJ Delorie wrote:
One thought I had for gnetlist backends, is to recode gnetlist as a
set of libraries.
Now you're talking.
The Core would only load the design files
(schematics, spreadsheets, databases, back-annotation info, etc) as
raw data; the backend
On May 31, 2011, at 6:35 AM, John Griessen wrote:
I'd like the first definition
of what gnetlist does be, Output any data it takes in, in the same format,
with lost spatial position information allowed, but keeping all other data
intact.
I think the reader should preserve *all* of the
Richard Rasker wrote:
OK, I'll start by reading up on the light vs. heavy symbol discussions.
Do I understand correctly that heavy symbols basically have certain nets
with predefined names (e.g. VCC, GND) implicitly included, whereas light
symbols offer the pins to connect those nets oneself?
I was thinking of how to represent all of the connections and relationships.
Then thought of sqlite3, as a database of connections.
a table of symbols,
a table of pins
This table maps the pins to a net and a symbol.
a table of nets
This is a rather simple database, of connections.
To
22 matches
Mail list logo
