kicad-developers team mailing list archive

[Chris Pavlina <pavlina.chris@xxxxxxxxx>]

I like that idea. I've got a few eeschema additions cooking in feature 
branches and I've done something similar, adapted existing parts in ways 
that don't change the file format and maintain backward compatibility. 
It's pretty easy to do, the file format is fairly versatile and the 
parser liberal :)

Would probably be sensible, even if it's totally compatible with older 
versions of eeschema, to make a special properties editor for these 
parts so users don't have to figure out how the relatively 
general-purpose fields relate to the specific pcbnew properties.

+1 for "A****m" ;)

Let me know if you want someone to offload the eeschema work onto, I'm 
rather familiar now :)

--
Chris


On Tue, Jun 30, 2015 at 01:28:03AM +0200, Tomasz Wlostowski wrote:
> On 30.06.2015 01:20, Chris Pavlina wrote:
> > What about doing it differently altogether? Altium, and AFAIK many other 
> > high-end and midrange tools, allow you to tag nets with properties in 
> > the schematic editor. We could have a net property for this instead.
> 
> What I meant is more or less what A****m does. I even played around a
> bit with eeschema code - a net attribute/property can be in the simplest
> form a virtual component (with no footprint), connected to a net. In the
> fields of such component, one could place all the constraints, this way
> we would need no changes to file formats.
> 
> Tom