kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #32508
Re: New records with zone filling.
Hi Wayne,
It is not in that way, and I did not ask that.
Merry Christmas and happier new year for everyone.
Heikki
On Sun, Dec 17, 2017 at 9:41 PM, Wayne Stambaugh <stambaughw@xxxxxxxxx>
wrote:
> Heikki,
>
> I am replying to you directly to avoid any potential issues on the
> developers mailing list. If you prefer to make this public, I am
> comfortable with that.
>
> Since English isn't your first language, I will try to give you the
> benefit of the doubt and assume that the intent of this post is not to
> bash the lead development team by showing how superior your code is. If
> that is the intent of this message, please refrain from doing this. The
> developers mailing list is not a forum for developers to advertise how
> superior their code is to other developers code. This is mailing list
> is for developers to collaborate for the advancement the KiCad project.
> I am not interested in how great of a programmer you are. I am
> interested in how you can help the project move forward.
>
> Too answer your earlier question as to why Tom's zone filling code got
> merged and yours did not is simple. You seem to be unwilling to
> cooperate with the lead developers by making changes to your code so
> that we can get them merged. I distinctly remember that I and other
> developers asked you on more than one occasion to fix issues with the
> connectivity assumptions you were making in your stitching via code.
> You seemed unwilling to make these changes so we could not use your code
> and instead had to write our own code to get the desired behavior.
> Apparently your code base has deviated so much from the KiCad
> development branch that Tom could not merge your threaded zone filling
> changes without a huge amount of effort on his part. It is unreasonable
> expect lead developers to spend large amounts of time getting
> your code in an acceptable condition for merging. My guess is that with
> a bit of cooperation on your part, we would have used your code instead
> of Tom's. This would have freed Tom up to work on other things and your
> threaded zone filling code would be in the KiCad development branch.
>
> I would prefer that you do cooperate with the development team. Many of
> your changes would be useful to the project. I understand if you are
> not interested in working with the development team. However, I'm not
> fine with you creating a hostile and combative environment for the
> development team just because you do not agree with out development
> process or you feel your changes are superior. Hopefully you will
> thoughtfully consider your role in the KiCad project and work with the
> development team in the future.
>
> Cheers,
>
> Wayne
>
>
> On 12/15/2017 11:50 AM, Heikki Pulkkinen wrote:
> > Hi
> >
> > And NEXT! I am going to improve pcbnew connectivity. I am just tired
> > that waiting in big boards when routed or dragged. Especially when
> > tracks are added full off my new track features (teardrops, t-junctions,
> > fillet junctions and rounded track corners). Old algorithm just worked
> > quite fine.
> >
> >
> > Regards
> >
> >
> > Heikki
> >
> > On Mon, Dec 11, 2017 at 12:39 PM, Heikki Pulkkinen <hei6mail@xxxxxxxxx
> > <mailto:hei6mail@xxxxxxxxx>> wrote:
> >
> > Hi,
> >
> > With interest, I try to improve my parallel zone filling. And new
> > records are:
> >
> > Olinuxino A64 board.
> > My parallel zone filling with new connectivity algo 4s.
> > My parallel zone filling with old connectivity algo 6s.
> > Current master 13s.
> >
> > WRS board.
> > My parallel zone filling with new connectivity algo 12s.
> > My parallel zone filling with old connectivity algo 2min 37s. Old
> > ratsnest calculation spend so much time at this board.
> > Current master 1 min 47s.
> >
> > Olinuxino A64 board with fully teardrops, stitch vias and rounded
> > track corners inserted.
> > My parallel zone filling with new connectivity algo 2min 16s.
> > My parallel zone filling with old connectivity algo 2min 27s.
> > Current master 3min 45s.
> >
> >
> >
> > Records are to be broken. Other things... that was the question.
> >
> >
> > Regards
> >
> > Heikki
> >
> >
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help : https://help. <https://help.launchpad.net/ListHelp>
Follow ups
References