As for the layer number issue, as I already said, you're free to search
and replace it to int. I'll do it personally if you like it.
Thank you for that offer. Since you were aware of my concern about
LAYER_NUM ahead of
your commit, and the fact that I do not view that enum as helpful,
On Mon, Apr 22, 2013 at 08:01:15AM -0500, Dick Hollenbeck wrote:
Lorenso, you were the only person consulted on this one. Some amount of work
was expended
by you.
The consultative decision process is described here:
On Fri, Apr 19, 2013 at 9:17 PM, jp charras jp.char...@wanadoo.fr wrote:
Another think... what does the ki in kicad stand for???
No special meaning.
after a small brain storming, a friend of mine suggest me kicad.
Now all I need to know is how to say it! KeeCad or KeyeCad?
Mitch.
On Mon, Apr 22, 2013 at 09:27:39PM +0800, Mitch Davis wrote:
Now all I need to know is how to say it! KeeCad or KeyeCad?
In Italy it's kee-kad :D
--
Lorenzo Marcantonio
Logos Srl
___
Mailing list: https://launchpad.net/~kicad-developers
Post to
On Fri, Apr 19, 2013 at 07:11:48PM -0500, Dick Hollenbeck wrote:
LAYER_NUM is mostly used as an iterator in our code, used to walk through for
loops.
Also as a parameter for indexing into stuff and especially LAYER_MSK
stuff. The main 'practical' reason for its introduction was finding
I'd like to have feedback from everyone on these opinions.
I fully agree with Lorenzo, I really need Top Assembly and Bot Assembly layers,
as well as more user layers (and user grids too).
But that's doesn't matter because all we could get as a result of discussion is
a Dick's cry about
On Apr 18, 2013 2:34 PM, Lorenzo Marcantonio l.marcanto...@logossrl.com
wrote:
On Thu, Apr 18, 2013 at 12:35:01PM -0500, Dick Hollenbeck wrote:
Lorenzo,
The page selection dialog was broken in rev 4081 by a change which
collapsed
was from USLedger to US Ledger.
Sorry my fault. I
On Fri, Apr 19, 2013 at 05:45:33AM -0500, Dick Hollenbeck wrote:
We might do well as a team by slowing down and focusing on reliability and
quality not features for awhile. Firstly, the bugs are damaging to the
project.
Using the user visible string as an index *is* a bad practice and a bug
On Apr 19, 2013 6:12 AM, Lorenzo Marcantonio l.marcanto...@logossrl.com
wrote:
On Fri, Apr 19, 2013 at 05:45:33AM -0500, Dick Hollenbeck wrote:
We might do well as a team by slowing down and focusing on reliability
and
quality not features for awhile. Firstly, the bugs are damaging to the
Le 19/04/2013 13:12, Lorenzo Marcantonio a écrit :
On Fri, Apr 19, 2013 at 05:45:33AM -0500, Dick Hollenbeck wrote:
We might do well as a team by slowing down and focusing on reliability and
quality not features for awhile. Firstly, the bugs are damaging to the
project.
Using the user
On Fri, Apr 19, 2013 at 02:11:08PM +0200, jp charras wrote:
Good or bad practice mainly depend on your criteria:
I know (and Dick knows) using an user visible string can create
issues, but using an index is not better:
when you insert a new item or change items order, indexes in
existing
On Fri, Apr 19, 2013 at 07:06:05AM -0500, Dick Hollenbeck wrote:
My dog is named jasper. He is not named 80 lb. brown labrador.
*YOU* named your dog. And since it has been given a *proper* name, why
couldn't a layer be called 'ClearancesForAvoidingBigExplosions'.
Otherwise you're
Le 19/04/2013 14:39, jp charras a écrit :
Le 19/04/2013 14:28, Lorenzo Marcantonio a écrit :
To this day I still don't know what ECO stands for, in fact... Comment2
would have been more explicative. And *I* know english, at least a bit.
Some EDA tools use ECO layers for specific comments:
ECO
On Fri, Apr 19, 2013 at 02:41:01PM +0200, jp charras wrote:
Engineering Comment Order
Maybe Engineering Change Order? some CAD use this term for forward/back
annotation...
Another think... what does the ki in kicad stand for???
Just curious:P
--
Lorenzo Marcantonio
Logos Srl
On 4/19/2013 8:11 AM, jp charras wrote:
Le 19/04/2013 13:12, Lorenzo Marcantonio a écrit :
On Fri, Apr 19, 2013 at 05:45:33AM -0500, Dick Hollenbeck wrote:
We might do well as a team by slowing down and focusing on
reliability and
quality not features for awhile. Firstly, the bugs are
Le 19/04/2013 14:48, Lorenzo Marcantonio a écrit :
On Fri, Apr 19, 2013 at 02:41:01PM +0200, jp charras wrote:
Engineering Comment Order
Maybe Engineering Change Order? some CAD use this term for forward/back
annotation...
Yes, or perhaps Engineering Command Order.
ECO was used in my
On Fri, Apr 19, 2013 at 09:06:39AM -0400, Wayne Stambaugh wrote:
comments about indices is correct. Using an ordinal number does not
guarantee layer compatibility when we finally get around to adding
more layers. They are also not readable. What is a layer 0, 1, 2,
3...N? You would always
On 04/19/2013 08:17 AM, jp charras wrote:
Le 19/04/2013 14:48, Lorenzo Marcantonio a écrit :
On Fri, Apr 19, 2013 at 02:41:01PM +0200, jp charras wrote:
Engineering Comment Order
Maybe Engineering Change Order? some CAD use this term for forward/back
annotation...
It is ECO Engineering
As for the layer number issue, as I already said, you're free to search
and replace it to int. I'll do it personally if you like it.
Thank you for that offer. Since you were aware of my concern about LAYER_NUM
ahead of
your commit, and the fact that I do not view that enum as helpful, I
On Fri, Apr 19, 2013 at 07:11:41PM -0500, Karl Schmidt wrote:
In real life ECO means something a bit different -- they are
documents that help stop things like purchasing substituting parts
with lower voltages.. I would write and sign an ECO for any part
change - sometime purchasing would not
20 matches
Mail list logo
