kicad-developers team mailing list archive

[Dick Hollenbeck <dick@xxxxxxxxxxx>]

On Apr 19, 2013 6:12 AM, "Lorenzo Marcantonio" <l.marcantonio@xxxxxxxxxxxx>
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
> > project.
>
> Using the user visible string as an index *is* a bad practice and a bug
> in the user view.

No, I am a user and do not hold that view.

My dog is named jasper.  He is not named "80 lb. brown labrador".

Once people learn his name and see him, they call him jasper.

That is exactly what I did when I first saw the eco1 layer.  I learned its
name and realized I could use it or not.

Since I have two 80 lb. brown dogs, people can have a conversation about
jasper only by using his name.  Otherwise which one are they talking about?

I have used 3 features of kicad this week and none of them worked.  Two of
them had been working when I committed them.

Yes you can have your own branch and make your own changes.  However it
takes a team to keep from having hundreds of separately evolving branches
and instead one cohesive common code base.  Somehow that team needs to come
to a more or less unified vision.

That my friend is not a purely technical process.  Being the smartest guy
in the room may actually make you the least likable and hardest to work
with.  At least that is what I have heard.





Why not replacing it with a simpler enumeration? The
> whole one-class-for-paper format is also debatable when a simple array
> would suffice (like for the color table array).
>
> 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. Then you're
> even free to use void* for every pointer in the project. Good luck then
> finding when a layer is used instead of a simple counter (or something
> which is not a layer is passed in, which actually occurred a few times
> in the past). Also have fun with the two layer numbers encoded in
> a single variable in the via class (obviously worth the 4 byte gain for
> each via).
>
> Other than that these are only design opinions (altough type safety is
> generally considered a good thing) and everybody can do whatever he want
> with his own code.
>
> --
> Lorenzo Marcantonio
> Logos Srl
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp