X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f Date: Fri, 11 Sep 2015 13:07:46 -0400 Message-Id: <201509111707.t8BH7kS8004233@envy.delorie.com> From: DJ Delorie To: geda-user AT delorie DOT com In-reply-to: <20150911190224.5b50175919e00b91df2ccf53@gmail.com> (geda-user AT delorie DOT com) Subject: Re: [geda-user] About reinventing the wheel, and how to avoid it References: <201509111624 DOT t8BGOPYV000685 AT envy DOT delorie DOT com> <20150911190224 DOT 5b50175919e00b91df2ccf53 AT gmail DOT com> Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > It could be a lot easier to add copper spacing rules in the > schematic. I guess attaching spacing attribute to nets possible > refering to a specific category for example "InverterOutputVoltage" > may solve it in the schematic but it must also be transferred to the > layout. Sure, attaching text to objects is easy if the application doesn't need to understand the text. gschem doesn't impose any copper spacing rules on schematics, so it doesn't care what text you add relating to copper spacing rules. It's just text. PCB has to enforce the rules, so it needs to both understand the desired rules and know how to impose them on the design. That's a much harder task than just keeping track of some text. I'm not denigrating the usefulness of being able to put arbitrary text anywhere; we added that to pcb (somewhat) as well. But don't think that being able to add a chunk of text is the same as doing something useful with that text.