kicad-developers team mailing list archive

[Jean-Paul Louis <louijp@xxxxxxxxx>]

To me, that really look like feature creep.
you rarely need everything from 4 to 64 pins, and then why stop at 64?
The idea of a library is that you can pick what you need, not what you can do just because you can.
Most of my work life, I was pushing design engineers to reduce the number of different parts, not increase it.


My $0.02,
Jean-Paul
AC9GH


On Nov 5, 2014, at 6:33 PM, LordBlick <lordblick@xxxxxxxxx> wrote:

> In response to a message written on 05.11.2014 23:53, from Nick Østergaard:
>>> IMHO that plugin should be named „pyDynamicFootprint” or similar.
>>> Instead of creating a long library from 4 to 64 pins we can easily generate
>>> desired package footprint on demand.
>> 
>> How do you select it? There is also the footprint wizzards.
> For KiCad it would be visible as normal library with all possible footprints, but takes less HDD space. Of course wizards interface is more useful, but needs some parameters.
> In fairness, however, this plug is flawed, because it however, as already we operate in python, so it's better to create footprints by embedded in pcbnew.py functionality, than discover the wheel again and do the parser/footprint lib saver job around.
> BTW. Perfection would be achieved if one could still generate 3D models ;)
> But unfortunately, the 3D model is a external element…
> -- 
> Best Regards,
> LordBlick
> 
> _______________________________________________
> 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