kicad-developers team mailing list archive

[easyw <easyw@xxxxxxxxxxxx>]

Don't get me wrong... I don't say KiCad has not to be improved.

I just say that complex mechanical objects have to be designed and 
checked in a mechanical environment.

And that is exactly what we have done with the KiCAd libraries...
Most of footprints are designed using scripts and are checked using a 
mechanical sw.

I agree that a new user should find a decent drawing editor, but when 
he/she gets experienced, the right direction is toward a MCAD/ECAD 
collaboration.

All commercial ECADs do it already, even with the entry level products.
So mechanical collaboration should be strongly suggested IMO.

Maurice


On 07/11/2019 6:51 PM, Jon Evans wrote:
> I strongly disagree with this mindset.
> It feels like saying that because KiCad is currently bad at something, it
> should always be bad at something and users should just use a different
> tool because KiCad will never be good at it.
> If we have the developer interest to make KiCad good at drawing things, why
> not do so?
> It doesn't help that the available FOSS MCAD tools are (in my opinion) much
> less capable relative to their commercial competitors than KiCad is
> relative to commercial ECAD tools.
>
> -Jon
>
> On Thu, Jul 11, 2019 at 12:16 PM easyw <easyw@xxxxxxxxxxxx> wrote:
>
> > On 07/11/2019 5:17 PM, Jeff Young wrote:
> > > Here’s a footprint I drew recently which was made much harder by Kicad’s
> > focus on arc centre points:
> > >
> >
> > This is exactly an example that should be done in a mechanical CAD and
> > imported later in KiCAD (i.e. as DXF).
> >
> > Complex mechanical object should be addressed with mechanical CAD, not
> > ECAD.
> >
> >
> > _______________________________________________
> > 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