- Original Message -
From: Brian F. G. Bidulock bidul...@openss7.org
To: Kicad Developers kicad-developers@lists.launchpad.net
Cc:
Sent: Tuesday, September 3, 2013 12:55 PM
Subject: Re: [Kicad-developers] Experiments and considerations for more
layer
Lorenzo,
While
Lorenzo,
On Tue, 03 Sep 2013, Lorenzo Marcantonio wrote:
On Mon, Sep 02, 2013 at 08:55:31PM -0600, Brian F. G. Bidulock wrote:
that's another 26 (or more) layers. Still think 64 will be
enough?
I said it was a mid-term solution.
Mid-term in the wrong direction. Kicad is like that...
Cirilo,
On Mon, 02 Sep 2013, Cirilo Bernardo wrote:
Hi Brian,
It looks like an awful lot of work you've done there. Has any of
it made its way back into the main tree?
None. I hear you guys might have got internal units done after three
years.
I'm also interested in knowing the
On Tue, Sep 03, 2013 at 04:21:59AM -0600, Brian F. G. Bidulock wrote:
5000 module descriptions to extract the 5000 pieces of placement
data is the horror of kicad's internal representation.
There is a reason for components being copied and not instantiated.
Often you need to 'tweak' a
On Tue, Sep 03, 2013 at 03:41:26AM -0600, Brian F. G. Bidulock wrote:
a layer number is a copper layer or not. For things like holes, range
comparisons are done mostly and bitmasks are useless. For non-copper
I do not agree on that. Everything that's related to a pad need to be
masked. Unless
Lorenzo,
On Tue, 03 Sep 2013, Lorenzo Marcantonio wrote:
On Tue, Sep 03, 2013 at 04:21:59AM -0600, Brian F. G. Bidulock wrote:
5000 module descriptions to extract the 5000 pieces of placement
data is the horror of kicad's internal representation.
There is a reason for components being
- Original Message -
From: Lorenzo Marcantonio l.marcanto...@logossrl.com
To: Kicad Developers kicad-developers@lists.launchpad.net
Cc:
Sent: Tuesday, September 3, 2013 8:26 PM
Subject: Re: [Kicad-developers] Experiments and considerations for more layer
On Tue, Sep 03, 2013 at
Lorenzo,
On Tue, 03 Sep 2013, Lorenzo Marcantonio wrote:
I do not agree on that. Everything that's related to a pad need to be
masked. Unless you add a list of layers, which is just another
(less efficient) representation for a bitmask. Or esplode the pad in
multiple instances to represent a
On Tue, Sep 03, 2013 at 03:41:26AM -0600, Brian F. G. Bidulock wrote:
Mid-term in the wrong direction. Kicad is like that...
Look. I have this board due to fabrication for the end of month.
I simply can't implement the whole object model in time *and* do the
board layout to produce it.
It's a
On Tue, Sep 03, 2013 at 03:35:16AM -0700, Cirilo Bernardo wrote:
That may be the case, but personally I would have preferred to treat that as
being a different component with its own footprint, even if it ultimately
refers to the same part number on the BoM. So many copies doesn't make much
On Tue, Sep 03, 2013 at 04:38:13AM -0600, Brian F. G. Bidulock wrote:
You don't need list of layers: just from and to--a pair.
How do you fit mask, silk and other technical layers in a range? I agree
that it would work for copped layers. But IMHO the 'right' solution
would be to have a pin
- Original Message -
From: Lorenzo Marcantonio l.marcanto...@logossrl.com
To: Kicad Developers kicad-developers@lists.launchpad.net
Cc:
Sent: Tuesday, September 3, 2013 8:51 PM
Subject: Re: [Kicad-developers] Experiments and considerations for more
layer
On Tue, Sep 03,
Lorenzo,
On Tue, 03 Sep 2013, Lorenzo Marcantonio wrote:
On Tue, Sep 03, 2013 at 03:41:26AM -0600, Brian F. G. Bidulock wrote:
Mid-term in the wrong direction. Kicad is like that...
Look. I have this board due to fabrication for the end of month.
I simply can't implement the whole object
Lorenzo,
On Tue, 03 Sep 2013, Lorenzo Marcantonio wrote:
On Tue, Sep 03, 2013 at 04:38:13AM -0600, Brian F. G. Bidulock wrote:
You don't need list of layers: just from and to--a pair.
How do you fit mask, silk and other technical layers in a range? I agree
that it would work for copped
Cirilo,
On Tue, 03 Sep 2013, Cirilo Bernardo wrote:
A down side to keeping things manageable (such as merging components
into the PCB) would be that there has to be a mapping which KiCAD
enforces for the integer layer ID and the usage. That is certainly
possible and when implemented I
On Tue, Sep 03, 2013 at 04:15:39AM -0700, Cirilo Bernardo wrote:
A down side to keeping things manageable (such as merging components into the
PCB) would be that there has to be a mapping which KiCAD enforces for the
integer layer ID and the usage. That is certainly possible and when
On Tue, Sep 03, 2013 at 05:21:58AM -0600, Brian F. G. Bidulock wrote:
Want to generate a Gerber for copper layer 4? Just iterate. No
masking required.
Major column versus major row... you optimize one thing and slow down
the other. A design decision like any other. What if you want to know
On Tue, Sep 03, 2013 at 05:29:12AM -0600, Brian F. G. Bidulock wrote:
See my other note. Just remember what layers things are on instead
of messing around with bitmasks. So, when you place pin 1, you place
it in the cells occupied by its shape and clearance, and place it (by
reference) in
Lorenzo,
On Tue, 03 Sep 2013, Lorenzo Marcantonio wrote:
On Tue, Sep 03, 2013 at 05:29:12AM -0600, Brian F. G. Bidulock wrote:
See my other note. Just remember what layers things are on instead
of messing around with bitmasks. So, when you place pin 1, you place
it in the cells occupied
On 09/03/2013 02:24 PM, Lorenzo Marcantonio wrote:
On Tue, Sep 03, 2013 at 05:29:12AM -0600, Brian F. G. Bidulock wrote:
See my other note. Just remember what layers things are on instead
of messing around with bitmasks. So, when you place pin 1, you place
it in the cells occupied by its
On 09/03/2013 12:33 PM, Brian F. G. Bidulock wrote:
Lorenzo,
On Tue, 03 Sep 2013, Lorenzo Marcantonio wrote:
On Tue, Sep 03, 2013 at 04:21:59AM -0600, Brian F. G. Bidulock wrote:
5000 module descriptions to extract the 5000 pieces of placement
data is the horror of kicad's internal
On Tue, Sep 03, 2013 at 03:23:46PM +0200, Tomasz Wlostowski wrote:
BTW. Judging from Altium's ASCII file format, it also copies every
component - and it's a pretty decent PCB program...
Also: until 2009 it only had 16 mechanical layers, and even today that
you have 32 you have to be consistent
- Original Message -
From: Lorenzo Marcantonio l.marcanto...@logossrl.com
To: Kicad Developers kicad-developers@lists.launchpad.net
Cc:
Sent: Tuesday, September 3, 2013 10:09 PM
Subject: Re: [Kicad-developers] Experiments and considerations for more
layer
On Tue, Sep
23 matches
Mail list logo
