I keep the supplied libraries intact too. As I edit or create components, I place them in my own set of libraries which I share between projects. When I'm happy with the quality of my libraries, I plan to share them with the Kicad community.
The relationship between footprints and the schematic is a bit of a thorny issue. I certainly would not want to have to choose between dozens of different resistors each time I lay one down in eeshema. It would also make changing footprints hell. My initial thoughts on this were that it would be nice to have a drop-list in place of the edit box in the component editor, a drop list linked to the available footprints. Better would be a combobox so you can enter the name of a footprint you plan to create later. However, I like the idea of targets as suggested by degrootc. Maybe two droplists (and therefore two fields) are needed - one for the component family (target), and the other for the actual footprint. The latter could be left blank by those who want to select the actual footprint in pcbnew, or completed by those wanting to define it in eeschema. Alternatively it might be better to insist that the actual footprint is some default, so pcbnew knows what to draw on first loading the netlist. Just my two penny's worth. However, I have to say although I'm no fan of the idea of going via cvpcb, a bigger gripe for me is that cvpcb doesn't work terribly well, especially when trying to change a footprint. Even so, there are issues that for me are more important (I've put them on the wishlist :) ). Robert. [EMAIL PROTECTED] wrote: > On 3 Oct 2007 at 20:17, degrootc wrote: > >> Hi Dave, >> >>> In eeschema, open the Library Editor. If you go to "Fields", one of >> the fields >>> is the footprint. This is blank in the supplied libraries. If you >> type the name >>> of a footprint, >> Thanks for your response. This is interesting. It allows me to set >> the default footprint in eeschema when I lay down a component. It >> certainly is better then what I have currently. I suppose I could just >> go into the *.lib files and add these fields in a text editor to speed >> up the edits. I'm starting to think that I'm moving further and >> further into a customer application usage pattern and thus will have >> difficulties when I update the version of kicad I use mmmm. >> >> Thanks C. >> > I create a special library for each project I do. I then copy the > components I > need from the supplied libraries to my special library and make modifications > there. That way, if I update KICAD, my modified components don't get > overwritten. > > Dave - WB6DHW > <http://wb6dhw.com> > > > > > > Please read the Kicad FAQ in the group files section before posting your > question. > Please post your bug reports here. They will be picked up by the creator of > Kicad. > Please visit http://www.kicadlib.org for details of how to contribute your > symbols/modules to the kicad library. > For building Kicad from source and other development questions visit the > kicad-devel group at http://groups.yahoo.com/group/kicad-devel > Yahoo! Groups Links > > > > > -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.488 / Virus Database: 269.14.0/1048 - Release Date: 10/3/2007 20:22
