kicad-developers team mailing list archive

[Miguel Angel Ajo <mangelajo@xxxxxxxxxx>]

I agree with JP here, QFP and QFN may be separate wizards. If there are common parts, feel free to use inheritance from a common base to reuse code.

About naming: footprint generators sound better, or whatever, at that time I was following an industry leader on naming it..., but I agree footprint generator is more clear for the task.

About including our scripting examples, I wouldn't, those are not tested with the current codebase, and likely to be broken because of C++ interface changes.

Sorry for my slow response,
best regards,
Miguel Ángel.


jp charras wrote:
> Le 30/09/2015 01:25, Wayne Stambaugh a écrit :
> > JP,
> >
> > Your name is on the initial commit for qfn_wizard.py.  I don't have time
> > to figure out these patches should be included.  Do these patches make
> > sense?  Let me know so I can make a decision on whether or not to commit
> > them.
> >
> > Thanks,
> >
> > Wayne
>
> These patches make sense, I used them to fix bugs in our footprint
> wizard dialog issues, and issues in some pythons scripts (mainly usage
> of print command which created python exceptions when stdout was never
> read, especially on Windows).
>
> But do not commit them. Reasons:
> - I am thinking the wizard to create a QFN should be an other wizard
> than the QFN wizard.
> The thermal pad needs many parameters, useless for a QFN without thermal
> pad.
> - The wizard to create a QFN with thermal pad needs refinements, before
> being committed
>
> I'll have a look at that later.