X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1432916565; bh=TjMqwFmipEQn46wx8kgtibqL6jPNHQESetml31GQ2H4=; h=Subject:From:To:Content-Type:Date:Message-ID:Mime-Version:Content-Transfer-Encoding; b=2leZZ+7kZaPxCGeBSdjDN0HU5JX3I4RmTUPygld0HawcNEyBtd4Y1y9cOMJGdqmz6B4X4yzkqD79Vx8721IAND3UaNcgaadCooUf0sAEhQmEhQnldPoQDN8yq1BKPH7Sufv7eXsJf8fVKrR++JKIHNULeGj+zpCfPevKJO4/LCQ= X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 63cwgGIVM1nGuhzIiapujEeojLFPnlhoW6B2sTi5lNikdE8 dEZ0hAw_Y2B3Zhcymc.QLW.ej6kMt.TcDcxnOgd3KAjTFPctfInwd9slSpI5 Pk0zs0ZnX.P27FuI_RTRvQ9caGPo6hjDkYjZRanIkjWsb_UMbCw03TUztt0I zLsSl6UxxY.gZTwHOCG_kjILrsoCaSru6n1h3Uqo9LAu20bolG9DanhEKIdW NSbqxp8QdWE7Cq3hha8USamVF6yHHZg.26OAUTHJwKzBoK.RgLMqZ4AqVjr6 tZ8BkntwHBFRQtLmQYrdF7oa9KSCUSCk7So6zH2VUMvYb9HKPlstf70jexlU hdPACBgx4WNS1HL5LkaHSzMPrYv1Nrs7M0kHf8GZvfTL_oFjWzDZzpJGprUy kSpoh8XpvoaK7CdfeMsVmtbABlGs6WR82WCTNe5zkyUHLKQmcne7NUhD0w8t IcILNEaYeq19ewXlPkP7E9.HGamTPgFH2c5E.he5d40..KTJ5Tu3q0x_EJvt Db_PSsvtl15.BGKyFxOyGXbWTzuB8N5uMURYb6lJjJ91OJ8rv X-Yahoo-SMTP: 7zb8EAqswBCnSUMm5KccNoxZ2QYVikaLwu.J Subject: [geda-user] PCB implementing slot attribute in a footprint From: "Mike Crowe (mcrowe AT gcdataconcepts DOT com)" To: geda-user AT delorie DOT com Content-Type: text/plain; charset="UTF-8" Date: Fri, 29 May 2015 11:22:44 -0500 Message-ID: <1432916564.3024.451.camel@crowe.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 (2.30.3-1.fc13) Content-Transfer-Encoding: 7bit Reply-To: geda-user AT delorie DOT com Hello All I've been using gEDA pcb for several years now have found it to be an excellent, stable, "meat and potatoes" tool for board layout. While there are several features I'd like to have implemented (keep out regions, blind and buried vias, footprints that allow generic traces, add pad flags 'start-round', 'stop-round'...) there is one feature that I'd really like to see. The ability to put slot on a board as part of a footprint. I'm interested in enough to volunteer time to help implement this. On the output NC-drill side, implementing it seems simple enough. It would be a start point, a "G85" keyword and an end point. There is some preliminary code support for viewing slots in gerbv (git version). At the footprint side, it seems to me that a new keyword identifier is in order, maybe "slot" It would have to properties of a "pin" except that it would have a start and stop point. Then, of course, there's all that stuff in the middle. Either a pin object would be extended to include a start/stop point, or a new object class would be created ( I know its "C", but the idea is the same regardless of the language ). I'm a relatively adept "C" programmer, and I think I'm up to the task. But before I dive in, I have a few questions. Is someone already working on a feature similar to this? If I generate a patch that works how do I go about getting this feature merged? Are there any roadmap developer docs that help lead the way through the code maze? In looking through the code, I see this "bison" stuff. I unfamiliar with it. What kinds of development tools are being used to implement this? Does the the above implementation approach make sense? Cheers Mike