-Original Message-
From: geda-user-boun...@moria.seul.org
[mailto:geda-user-boun...@moria.seul.org] On Behalf Of Anthony Blake
Sent: Wednesday, March 17, 2010 9:14 PM
To: wind...@oskay.net; gEDA user mailing list
Subject: Re: gEDA-user: Toporouter update?
On Thu, Mar 18, 2010
Hi,
I couldn't compile a fresh copy of PCB cloned from git.
It fails with:
hid/lesstif/menu.c: In function ‘lesstif_call_action’:
hid/lesstif/menu.c:856: error: ‘x’ undeclared (first use in this function)
hid/lesstif/menu.c:856: error: (Each undeclared identifier is reported only once
is that really building a 'motif' based frontend lol.
On Thu, Mar 18, 2010 at 11:20 PM, Kovacs Levente leventel...@gmail.com wrote:
Hi,
I couldn't compile a fresh copy of PCB cloned from git.
It fails with:
hid/lesstif/menu.c: In function ‘lesstif_call_action’:
hid/lesstif/menu.c:856:
Ur? Not trendy enough for you? ;)
-Dave
On Mar 18, 2010, at 10:25 AM, timecop wrote:
is that really building a 'motif' based frontend lol.
On Thu, Mar 18, 2010 at 11:20 PM, Kovacs Levente
leventel...@gmail.com wrote:
Hi,
I couldn't compile a fresh copy of PCB cloned from git.
Hello,
Kovacs Levente writes:
[...]
hid/lesstif/menu.c: In function ?lesstif_call_action?:
hid/lesstif/menu.c:856: error: ?x? undeclared (first use in this function)
hid/lesstif/menu.c:856: error: (Each undeclared identifier is reported only
once
hid/lesstif/menu.c:856: error: for
On Thu, 18 Mar 2010 23:25:50 +0900
timecop time...@gmail.com wrote:
is that really building a 'motif' based frontend lol.
I miss some feature from the GTK HID:
The layerlist, the toolbox, and the route style selection stuff can't be
removed from the left. This waists space from the design.
Dear all,
It has come to my attention that my PCB+GL branches (starting from
polygon_speedup onwards, contain a flaw which can in some
circumstances result in subtly corrupted polygons - which can in turn
ruin a finished board's connectivity.
It is very important that until this is resolved, all
On Thu, 2010-03-18 at 17:09 +1300, Anthony Blake wrote:
Who's going to mentor you for GSOC purposes?
Since Harry Eaton has never been shy with lots of really good criticism
and comments regarding the toporouter (off list), I asked if he would be
interested a few weeks ago..
Can you guys
Anthony Blake wrote:
On Thu, Mar 18, 2010 at 12:56 PM, Windell H. Oskay wind...@oskay.net wrote:
Also, can anyone think of a new name for the toporouter? There is
already a commercial tool called the 'toporouter', which I don't want
us to be confused with.
untangler
runtangler ( route
On Thu, 2010-03-18 at 11:14 -0500, John Griessen wrote:
Anthony Blake wrote:
On Thu, Mar 18, 2010 at 12:56 PM, Windell H. Oskay wind...@oskay.net
wrote:
Also, can anyone think of a new name for the toporouter? There is
already a commercial tool called the 'toporouter', which I don't want
Hello,
On 3/18/10, Kovacs Levente leventel...@gmail.com wrote:
I couldn't compile a fresh copy of PCB cloned from git.
It fails with:
hid/lesstif/menu.c: In function ‘lesstif_call_action’:
hid/lesstif/menu.c:856: error: ‘x’ undeclared (first use in this function)
hid/lesstif/menu.c:856:
Peter Clifton wrote:
On Thu, 2010-03-18 at 11:14 -0500, John Griessen wrote:
Anthony Blake wrote:
On Thu, Mar 18, 2010 at 12:56 PM, Windell H. Oskay wind...@oskay.net wrote:
Also, can anyone think of a new name for the toporouter? There is
already a commercial tool called the 'toporouter',
On Thu, 2010-03-18 at 15:09 +, Peter Clifton wrote:
Dear all,
It has come to my attention that my PCB+GL branches (starting from
polygon_speedup onwards, contain a flaw which can in some
circumstances result in subtly corrupted polygons - which can in turn
ruin a finished board's
Can you guys keep this on the geda-dev list in future.. it is always
fun
to see how things are progressing.
Certainly, if Anthony and I discuss anything now that GSoc is not to
be.
Previously, I couldn't subscribe or send to the geda-dev list (or user
for that matter).
Harry Eaton wrote:
Can you guys keep this on the geda-dev list in future.. it is always
fun
to see how things are progressing.
Certainly, if Anthony and I discuss anything now that GSoc is not to
be.
I'm not going to stop working on the toporouter (greenlight?) just
On Mar 18, 2010, at 7:54 PM, Anthony Blake wrote:
Can you guys keep this on the geda-dev list in future.. it is always
fun
to see how things are progressing.
Certainly, if Anthony and I discuss anything now that GSoc is not to
be.
I'm not going to stop working on the
+1 *hassle*
(i really like toporouter :)
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
I'm not going to stop working on the toporouter (greenlight?) just
because Google didn't fund us. If people keep hassling me, I'll probably
find the time for small commits here and there.. e.g., most of my work
last year was an answer to some scathing criticism from Harry.. I *had*
to do
I'm not going to stop working on the toporouter (greenlight?) just
because Google didn't fund us. If people keep hassling me, I'll
probably
find the time for small commits here and there.. e.g., most of my
work
last year was an answer to some scathing criticism from
Peter Clifton wrote:
It has come to my attention that my PCB+GL branches (starting from
polygon_speedup onwards, contain a flaw which can in some
circumstances result in subtly corrupted polygons - which can in turn
ruin a finished board's connectivity.
Thanks for the warning!
Luckily, I
Harry Eaton wrote:
I'm not going to stop working on the toporouter (greenlight?) just
because Google didn't fund us. If people keep hassling me, I'll
probably
find the time for small commits here and there.. e.g., most of my
work
last year was an answer to some
Hi,
I want to do an OS upgrade this weekend on gpleda.org. I don't
expect long downtimes, but there might be a period of a couple hours
of downtime. I'm not sure which day, but probably either Saturday
afternoon/evening EST or Sunday.
I'll send a note when things go down and when they come
On Fri, 2010-03-19 at 01:39 +0100, kai-martin knaak wrote:
Peter Clifton wrote:
It has come to my attention that my PCB+GL branches (starting from
polygon_speedup onwards, contain a flaw which can in some
circumstances result in subtly corrupted polygons - which can in turn
ruin a
Stuart Brorson wrote in geda.devel:
Why is the summer of code topic discussed on the developer list only?
(Non-)acceptance to GSoC certainly matters to ordinary users, too.
If you're interested, here's the list of accepted groups:
On Fri, Mar 19, 2010 at 2:15 PM, kai-martin knaak k...@familieknaak.de wrote:
If you're interested, here's the list of accepted groups:
http://socghop.appspot.com/gsoc/program/accepted_orgs/google/gsoc2010
... Facebook ... Mozilla ... Gentoo
Not exactly organizations I'd expect to need
Anthony Blake wrote:
greenlight -- Despite being the least
router-ish
of these names, I really like
this one.
Hmm.. me too..
I'd strongly suggest to invent a new word rather
On Fri, Mar 19, 2010 at 2:27 PM, kai-martin knaak k...@familieknaak.de wrote:
So let's concentrate to the most blocking of all issues:
If I got it right, these are the inability to deal with preexisting tracks
and the missing way to confine the router to selected nets. If these issues
were
Anthony Blake wrote:
The toporouter will already route a selection of nets if some nets are
selected when the toporouter is invoked.
Nice!
---(kaimartin)---
--
Kai-Martin Knaak
Öffentlicher PGP-Schlüssel:
http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x6C0B9F53
On Mar 18, 2010, at 9:15 PM, Anthony Blake wrote:
Thanks for the offer =) On the one hand, I really want to finish the
toporouter, and its hard while I'm studying full time.. so taking a
funded break for a few weeks to work on the toporouter seems like a
great option. On the other hand, there
On Fri, Mar 19, 2010 at 2:33 PM, kai-martin knaak k...@familieknaak.de wrote:
Anthony Blake wrote:
The toporouter will already route a selection of nets if some nets are
selected when the toporouter is invoked.
Nice!
Also, it will only route on the currently visible layers.
--
Anthony
On Mar 15, 2010, at 6:35 PM, Dan McMahill wrote:
I spend a *lot* of time looking at simulator output and some of the things
which are used over and over again are easy interactive zoom in/out,
panning at a fixed zoom, putting cursors on waveforms that will lock onto
the actual datapoints,
Anthony Blake wrote:
most of my work
last year was an answer to some scathing criticism from Harry.. I *had*
to do something after that =)
So, all we have to do is read the code, scratch our heads and find
critiques to make and you'll be compelled to improve it?
I may have to stay up late
kai-martin knaak wrote:
Anthony Blake wrote:
greenlight ---
I'd strongly suggest to invent a new word rather than take an existing
buzzword. The term greenlight currently yields 1.5 Mio google hits.
A greenlight router would be almost as invisible to internet searches
33 matches
Mail list logo
