On Mon, 13 Dec 2010 09:02:15 +
andrew whyte ajwh...@gmail.com wrote:
Hi Everyone,
I realise that I am joining a very established thread, but I'd like
to put forward 2 cents worth. Please don't be offended if what I'm
saying isn't the same as your opinion. I have used gEDA as the main
Bob Paddock wrote:
If you switch to gEDA, will you want a native windows build? Help with that
from anyone who is up on windows is on the wanted list.
I've been poking at 'the perfect windows version' for some time, will
give up on that for now.
I think I just make basic canvas and
On 12.12.2010 17:36, Martin Kupec wrote:
I am personally not that strong on windows. But getting it up
on windows will probably help.
Do you have an idea, how to build it on windows? I expect errors
and problems, but just generally which toolchain to use?
pcb
Colin D Bennett wrote:
If footprints are extended to allow text elements to be included, then
I really hope that general polygons will be allowed too.
plus arcs, two layers of silk, lines in copper, vias, mid layers, ...
In short: The footprint format should allow everything you can do in a
Anthony Blake wrote:
We already have a decent footprint/symbol library..
Ermm, no. We don't have decent libraries. What we have, is two sets of
inconsistent, incomplete libraries plus an orderless bunch of user
contributions in gedasymbols.org. The default symbols refuse to give a
clue what
Did you try to build/test all the demos that come with wxWindows - did you
try to build another app, that uses it? - please report. My personal
impression
when I went for a widget tool kit was, that it's very complicated and broken.
I've been using wxWidgets for over ten years now. You'll
On Sun, 2010-12-12 at 17:03 +, Peter Clifton wrote:
I've used Cesar Strauss' minipack tools to build it before. This isn't
particularly maintained, but the latest gEDA version is packaged up here
for testing:
http://www2.eng.cam.ac.uk/~pcjc2/geda-windows.html
WARNING::
A colleague of
${EnvVarUpdate} $0 PATH A HKLM $INSTDIR\bin
It looks OK from a quick glance, but it depends what build settings
were used for the NSIS...
Warning this code will replace paths rather than append if the existing path
exceeds the
maximum string length in the NSIS build you are using.
Maybe he
Bob Paddock wrote:
so I'm well familiar with its warts.
All of the commercial apps I've had to develop at work have been based on wx.
Then you are in a special situation and I won't argue with you about
usability.
Can't argue with it being complicated. Start with the above book, and
get
At 04:30 AM 12/14/2010, Kovacs Levente wrote:
On Mon, 13 Dec 2010 09:02:15 +
andrew whyte ajwh...@gmail.com wrote:
Hi Everyone,
..snip..
Because of the GERBER standard, FOSS stands a chance of creating
competitive tools for EDA, this is much more difficult in areas where
open
Anybody going to 27C3 in Berlin during the 27th-30th of December? I'd
like to spend some of my spare time at the conference working on or
promoting gEDA. I've signed up to give a two hour workshop/tutorial on
gschem/pcb, so hopefully that will be accepted. If there were a couple
of us going
On Tue, 2010-12-14 at 22:04 +0900, timecop wrote:
${EnvVarUpdate} $0 PATH A HKLM $INSTDIR\bin
It looks OK from a quick glance, but it depends what build settings
were used for the NSIS...
That I don't know, I just apt-get install'ed it. I guess it might be
worth me re-building the
Warning this code will replace paths rather than append if the existing
path exceeds the
maximum string length in the NSIS build you are using.
Maybe he tried installing it into some huge path and ended up trimming
the entire var set or something...
I think what could happen if im
On Tue, 2010-12-14 at 14:18 +0100, Armin Faltl wrote:
As this was 2006, probably a very old version. If I remember correct,
the minimal sample
(using OpenGL?) either didn't compile or segfaulted or just didn't do
anything on Windows or Linux (I have no Mac).
The OpenGL sample I found for
On Tue, 2010-12-14 at 23:10 +0900, timecop wrote:
Maybe he tried installing it into some huge path and ended up trimming
the entire var set or something...
I think what could happen if im reading this warning correctly is that
if he already HAD a lot of stuff in $PATH that was some huge
On Tue, 14 Dec 2010 12:09:45 +0100
Kai-Martin Knaak kn...@iqo.uni-hannover.de wrote:
If footprints are extended to allow text elements to be included, then
I really hope that general polygons will be allowed too.
plus arcs, two layers of silk, lines in copper, vias, mid layers, ...
In
John Coppens wrote:
I see no point in arbitrary restrictions.
That was mainly what I was wondering about in the first place.
Shouldn't footprints be something like functions in programming? Or
maybe slightly more similar to macros?
There is one caveat, though:
Layouts can contain layers
Parentheses around a constant are nonsense - there is nothing a plain number
could evaluate to in the preprocessor than itself (unless you #define 1e20
(foo * i++)),
so it has the highest precedence by itself. (couldn't you even #define
(1e20) foo*i++ ?;-)
Not knowing how the #define
I did a geda/pcb lab for Devcon which you can borrow from if you
like...
http://www.delorie.com/electronics/rulz/A31L.html
It takes my son about 45 minutes to go through it, but the average
engineer takes over an hour due to play time :-) I'd schedule two
hours for it as-is. One hour was *not*
Layers in the footprint have to be mapped according to the principle
of least surprise.
Last we talked of this, I mentioned symbolic layer tags vs physical
layer tags. So footprints would have top/inner/bottom layers, boards
would have 1(top)/2/3/4(bottom) layers.
Yes, mapping everything is
DJ Delorie d...@delorie.com writes:
Layers in the footprint have to be mapped according to the principle
of least surprise.
Last we talked of this, I mentioned symbolic layer tags vs physical
layer tags. So footprints would have top/inner/bottom layers, boards
would have
Bob Paddock wrote:
Parentheses around a constant are nonsense - there is nothing a plain number
could evaluate to in the preprocessor than itself (unless you #define 1e20 (foo *
i++)),
so it has the highest precedence by itself. (couldn't you even #define (1e20)
foo*i++ ?;-)
Not
We talked about that. It's hard to do but not impossible :-)
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
On Tue, 2010-12-14 at 13:18 +, Robert Fitzsimons wrote:
Anybody going to 27C3 in Berlin during the 27th-30th of December? I'd
like to spend some of my spare time at the conference working on or
promoting gEDA. I've signed up to give a two hour workshop/tutorial
on gschem/pcb, so
On Sat, Dec 11, 2010 at 04:05:11PM +, Peter Clifton wrote:
Well, don't forget to raise the issues here - you might find you get
some of them fixed for free ;) Fixing issues affecting everyone
benefits everyone. If they are very complex to fix, sponsoring someone
with the required know-how
On Tue, 2010-12-14 at 22:57 +0100, Martin Kupec wrote:
Sometimes, when you place to lines too close, but not that close
in polygon. It will make thin line in the polygon connecting two
part of the polygon. DRC will mark this line as too thin.
Actually, I'm pretty sure the
26 matches
Mail list logo
