gEDA-user: Expansion of the footprint definition
I am sure there has been discussion around this in the past - but I am keen to know if there is any chance of PCBs understanding of what a footprint can contain being expanded in the near future? Primarily just two things I would really like... text and polygons... Is this something that requires a major refactor - or is it something that someone who is new to the pcb source may have a chance of looking at? cheers, Geoff ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Expansion of the footprint definition
I am sure there has been discussion around this in the past - but I am keen to know if there is any chance of PCBs understanding of what a footprint can contain being expanded in the near future? It's been discussed, but would be a major change. Very desirable, though. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Expansion of the footprint definition
DJ Delorie wrote: I am sure there has been discussion around this in the past - but I am keen to know if there is any chance of PCBs understanding of what a footprint can contain being expanded in the near future? It's been discussed, but would be a major change. What is the blocking aspect? Is the change so intrusive that half of the code base is affected? Or is it the problem of breaking backward compatibility? Or something completely different? ---)kaimartin(--- -- Kai-Martin Knaak Email: k...@familieknaak.de Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Expansion of the footprint definition
Is the change so intrusive that half of the code base is affected? Or is it the problem of breaking backward compatibility? Both of these. We'd need a file format change, editing code, display code, DRC changes, autorouter changes, optimizer changes, connectivity checks, buffer conversions, etc. It is generally agreed that, if we're going to do that much work anyway, it would be better to redesign the internals to have a concept of sub-layout and have elements just be a special case of those. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
