kicad-developers team mailing list archive

[Carl Poirier <carl.poirier.2@xxxxxxxxx>]

Benoît, this is exactly what I tried to say. I wasn't talking about symbols
in Altium, but about components. They are already associated with
footprints and so on, thus making them components. The drawing that we are
working on in the schematic library editor is a symbol. In the component
properties, we can only put a filter on footprints for it, but AFAIK,
that's about it. So I'd say it still stands as a symbol. If some more
pairing is going to be done in this editor, such as a unique footprint, a
SPICE model, and so on, then we might as well call the editor a component
editor. But what if it's used to create only a symbol?

Furthermore, how would the symbol and component libraries be
differentiated, once some more serious associations are done? Will they all
be mixed together? I think that's also part of the problem.

On Mon, Oct 13, 2014 at 8:10 AM, Benoît Roehr <benoit.roehr.ec@xxxxxxxxx>
wrote:

> In KiCAD each project can have its own library of footprints, so this idea
>> duplicates, that exist already.
>>
> OK thanks ! I did not know about it before :)
>
> Le 13/10/2014 13:21, LordBlick a écrit :
>
>> In response to a message written on 13.10.2014 12:04, from Benoît Roehr:
>>
>>> Le 13/10/2014 11:40, LordBlick a écrit :
>>>
>>>> In response to a message written on 13.10.2014 08:01, from Benoît
>>>> Roehr:
>>>>
>>>>> For kicad, it could be a good thing to be able to embed a single
>>>>> footprint to a
>>>>> component if the footprint is really special, but it's non sens if you
>>>>> can
>>>>> appropriately tag the footprint and put it with the others.
>>>>>
>>>> There is a special field to assign footprint to schematic element…
>>>>
>>> Yes i know, I was meaning if you need a very special footprint just for
>>> one
>>> component, you may not want to pollute your existing pcblibrary with this
>>> footprint. For example, you have just one component packaged in a 2 rows
>>> QFN
>>> package. You don't want this in your standard QFN lib.
>>> So the ability to attach a single footprint directly to the component
>>> without
>>> creating or modifying a PCBLib can be useful.
>>> But it is new feature and it doesn't have to be implemented yet. Not
>>> important.
>>> Footprint have to be well named, and all searchable in the same place,
>>> not
>>> hidden. ;) More important for me would be a footprint preview in schlib
>>> editor.
>>>
>> In KiCAD each project can have its own library of footprints, so this
>> idea ​​
>> duplicates, that exist already.
>>
>
>
> _______________________________________________
> 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
>