On 12/11/2012 11:47 PM, Dick Hollenbeck wrote: > On 12/11/2012 10:01 PM, Kaspar Bumke wrote: >> I would just like to chime in as a user that I guess I don't mind >> whether I launch the "window" where I assign footprints from the main >> KiCad launcher or from eeSchema. The decoupling between the schematic >> file and the footprint assignment is quite important to me though. I >> like being able to have a diode somewhere and not care what package it >> comes in. Having these as separate files is definitely a feature for >> me. >> >> WIth that in mind I guess I fail to understand why maintaining a >> seperate DLL/DSO is easier than maintaining a separate executable. > The problem is I want to make footprints before I make a board. > > The footprints I need are rarely there, I have to make them more than 50% of > the time. > > I don't want to have to enter Pcbnew to design footprints, create a project, > assign > library paths, this is all a nuisance to making a footprint in a library I > already have. > > It feels like there is a *chasm* in the design process. > > So if you are asking me, forget maintenance, think nuisance.
You have to cross the chasm to get to the thing you need, which is to create a footprint. Why put CVPCB, assigning footprints, in the path of the creation of footprints? That is out of sequence, think about it. _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
