I just offer this here, not sure if it could be interesting (I think
it could, as I see it as a productivity boost)
In the last year I started using Confluence (+JIRA + gliffy) in my
little-tiny company,
and it was a real productivity boost (everything became ultra easy to
document,
Human readability/usability/ease of learning would also be helped with
some standardization.
On 8/04/2012 8:23 p.m., Dick Hollenbeck wrote:
On 04/08/2012 11:38 AM, lajos kamocsay wrote:
Hi Wayne-
The new file format looks awesome. Very simple and readable.
Would it be possible to
On 8/04/2012 8:23 p.m., Dick Hollenbeck wrote:
On 04/08/2012 11:38 AM, lajos kamocsay wrote:
Hi Wayne-
The new file format looks awesome. Very simple and readable.
Would it be possible to standardize the transformation data? Currently
there seems to be a couple different formats, some
On 04/09/2012 08:27 AM, Jerry Jacobs wrote:
I'm using the LLVM clang compiler on OS X (which has a gcc/g++ 4.2 style
frontend), it seems that removing the auto_ptr.h fixed the problem and
linked perfect.
jerry@white:/Volumes/kicad/common$ make
[ 60%] Built target common
[ 60%] Building
Some more feedback:
(segment ...) IS on one line, so good there.
Wonder if (segment) is our best keyword for what is a trace/track. specctra
uses
(wire). Could check EAGLE's new XML format, if we're lacking opinions, which
would be
atypical.
Wonder of the flags in (segment (status HERE)
On 4/9/2012 1:10 AM, Dick Hollenbeck wrote:
On 03/27/2012 12:55 PM, Dick Hollenbeck wrote:
On 03/27/2012 04:56 AM, Edwin van den Oetelaar wrote:
Hello everyone,
My name is Edwin, I have some motivation and skill to help with your
project.
Although I am not very old yet, I do have some deep
On 04/09/2012 09:38 AM, Dick Hollenbeck wrote:
Some more feedback:
(segment ...) IS on one line, so good there.
Wonder if (segment) is our best keyword for what is a trace/track. specctra
uses
(wire). Could check EAGLE's new XML format, if we're lacking opinions,
which would be
On 4/9/2012 6:28 AM, jean-pierre charras wrote:
On 8/04/2012 8:23 p.m., Dick Hollenbeck wrote:
On 04/08/2012 11:38 AM, lajos kamocsay wrote:
Hi Wayne-
The new file format looks awesome. Very simple and readable.
Would it be possible to standardize the transformation data? Currently
there
On 09/04/2012 07:13, Miguel Angel Ajo Pelayo wrote:
I just offer this here, not sure if it could be interesting (I
think it could, as I see it as a productivity boost)
In the last year I started using Confluence (+JIRA + gliffy) in
my little-tiny company,
and it was a real
On 4/9/2012 9:50 AM, Dick Hollenbeck wrote:
Wayne, regarding:
DRAWSEGMENT::Format(), it concerns me in two minor ways:
case S_SEGMENT: // Line
aFormatter-Print( 0, line (pts xy(%s) xy(%s)),
FormatBIU( m_Start ).c_str(),
On 4/9/2012 10:38 AM, Dick Hollenbeck wrote:
Some more feedback:
(segment ...) IS on one line, so good there.
Wonder if (segment) is our best keyword for what is a trace/track. specctra
uses
(wire). Could check EAGLE's new XML format, if we're lacking opinions,
which would be
On 4/9/2012 11:18 AM, Miguel Angel Ajo Pelayo wrote:
They seem to be using wire for schematics: and wire for pcb too.
They also enumerate the layers at start.
Miguel,
Thanks for the eagle files. A layer map at the top of the file is a
good idea. Something like
(layers
(0
Hi Wayne-
I've had a conversation with Dick, and he asked me to clarify my
suggestion about standardizing the transformation data.
Standardizing would save you work and debugging time because you would
only need to write the encoder and decoder (parser) once. Instead of
every object taking care
Le 09/04/2012 17:02, Wayne Stambaugh a écrit :
On 4/9/2012 6:28 AM, jean-pierre charras wrote:
On 8/04/2012 8:23 p.m., Dick Hollenbeck wrote:
On 04/08/2012 11:38 AM, lajos kamocsay wrote:
Hi Wayne-
The new file format looks awesome. Very simple and readable.
Would it be possible to
On 04/09/2012 10:37 AM, Wayne Stambaugh wrote:
On 4/9/2012 9:50 AM, Dick Hollenbeck wrote:
Wayne, regarding:
DRAWSEGMENT::Format(), it concerns me in two minor ways:
case S_SEGMENT: // Line
aFormatter-Print( 0, line (pts xy(%s) xy(%s)),
FormatBIU(
On 04/09/2012 10:45 AM, Wayne Stambaugh wrote:
On 4/9/2012 10:38 AM, Dick Hollenbeck wrote:
Some more feedback:
(segment ...) IS on one line, so good there.
Wonder if (segment) is our best keyword for what is a trace/track. specctra
uses
(wire). Could check EAGLE's new XML format, if
Le 09/04/2012 17:37, Wayne Stambaugh a écrit :
On 4/9/2012 9:50 AM, Dick Hollenbeck wrote:
Wayne, regarding:
DRAWSEGMENT::Format(), it concerns me in two minor ways:
case S_SEGMENT: // Line
aFormatter-Print( 0, line (pts xy(%s) xy(%s)),
FormatBIU(
On 04/09/2012 10:07 AM, Wayne Stambaugh wrote:
On 4/9/2012 9:43 AM, Dick Hollenbeck wrote:
Wayne and all,
I feel better now about PCBNEW loading a BOARD with USE_PCBNEW_NANOMETRES
defined after
some work I did this weekend.
Dick,
Great work! Thanks for fixing this so we can keep the
On 04/09/2012 01:41 PM, jean-pierre charras wrote:
Le 09/04/2012 17:37, Wayne Stambaugh a écrit :
On 4/9/2012 9:50 AM, Dick Hollenbeck wrote:
Wayne, regarding:
DRAWSEGMENT::Format(), it concerns me in two minor ways:
case S_SEGMENT: // Line
aFormatter-Print( 0, line (pts
Yes, Altium makes extensive use of Confluence.
I think this is where I got the idea for using Confluence + JIRA + etc...
for my company :-) in
first place.
I think it could save us a lot of time for design, manual maintenance,
etc... and In the worst case
(if we needed for just any reason a
Now that may be we're still in time (well in fact, now I think that could
be added lately without big impact..)
What do you think about adding a UUID (I see now that you used 'LPID'
for SWEET) to the PCB files, and also a revision number (that goes
incrementally on every modified save).
On 04/09/2012 02:55 PM, Miguel Angel Ajo Pelayo wrote:
Now that may be we're still in time (well in fact, now I think that could be
added
lately without big impact..)
What do you think about adding a UUID (I see now that you used 'LPID'
for SWEET)
to the PCB files, and also a
I love the plan, it matches and extends the tiny idea I had but it's well
planned!!,
About the SWEET_HTTP_LIB source and even SWEET servers, and web apps,
I propose that we could use our (future) new python powers, that are
proficient
in handling XML-RPC, Databases, and similar things with very
On 4/9/2012 2:37 PM, Dick Hollenbeck wrote:
On 04/09/2012 10:45 AM, Wayne Stambaugh wrote:
On 4/9/2012 10:38 AM, Dick Hollenbeck wrote:
Some more feedback:
(segment ...) IS on one line, so good there.
Wonder if (segment) is our best keyword for what is a trace/track.
specctra uses
On 4/9/2012 2:41 PM, jean-pierre charras wrote:
Le 09/04/2012 17:37, Wayne Stambaugh a écrit :
On 4/9/2012 9:50 AM, Dick Hollenbeck wrote:
Wayne, regarding:
DRAWSEGMENT::Format(), it concerns me in two minor ways:
case S_SEGMENT: // Line
aFormatter-Print( 0, line (pts
On 4/9/2012 5:43 PM, Miguel Angel Ajo Pelayo wrote:
Nice Wayne,
Don't you think that also dumping the non-default layers would make
sense?,
just for sanity of the file format (making complete sense even without
the version
of kicad it belongs to).
May be on future kicad version
A month or so ago (2 Mar 2012) Bob Cousins wrote about using FreeCAD to create
3D STEP models. I've been looking into this issue for a few months now and
here are some of my (still early) thoughts on the matter:
1. Due to the complexity of any software implementing the STEP AP203/AP214
27 matches
Mail list logo
