X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=mail.ud03.udmedia.de; h= message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; s=beta; bh= kjLp7Ab5xRjlKCwl/IftIlUjTFJQUudbctrHEJy+E6o=; b=uAlMrDyndZ4q1DC+ OtqoJ8a4XQSryeCA2ItSVTdHmjrGj/d6B+QDBnhK33MgN2+lmWHkJHSY6LXNGm/M 4c89OOJY1iDCQTk/vFHa1QjzrEwHSuSYaOZfFi42Pyrqag6tyvmBNYkTFZu18+2V O6RMUN2NbFbQLLXKzyYx86uxXq0= Message-ID: <50924802.4070307@jump-ing.de> Date: Thu, 01 Nov 2012 10:59:30 +0100 From: Markus Hitter User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1 MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] The state of gEDA/gaf (Was gEDA/PCBs diversity, Was: Pin hole size) References: <2CB304B5-9587-4734-84E4-49F464744D11 AT noqsi DOT com> <6BF2E986-51EB-41E9-A4AD-8071CD00B1A1 AT jump-ing DOT de> <834283D4-0891-486E-A981-2FF20B32C615 AT noqsi DOT com> <54CAA7EE-7638-4B89-8197-111D0493F859 AT noqsi DOT com> <508CE947 DOT 4050408 AT xs4all DOT nl> <665E18E2-E9F9-40E4-9DE1-CC8FDBBDCB00 AT noqsi DOT com> <508EE43F DOT 5050505 AT neurotica DOT com> <9B14233C-F3A7-489C-BDC7-F6EAAAFCAB51 AT noqsi DOT com> <508EECDA DOT 8090803 AT neurotica DOT com> <20121030231609 DOT 615b3238 AT akka> <520BBE4F-11DA-4213-9AFF-F6F1127625C2 AT noqsi DOT com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: geda-user AT delorie DOT com Am 01.11.2012 04:39, schrieb Benjamin Bergman: > I think there is some unneeded complexity in the > interface. I don't know if there is currently any effort to correct > this, but I would be willing to lend a hand to do some of this > development. I haven't touched the code much, but if someone wants to > point me to a good starting place, I'm all ears. Small fixes are welcome, too, just open a Launchpad bug for it so the patch can find it's way into the repo. The public repo viewer is here: http://git.geda-project.org/pcb/ You could try to review bug fix branches like this one: http://git.geda-project.org/pcb/commit/?h=LP1035979 See what it does, wether it solves the problem properly, then it can be cherry-picked onto master. For changes changing the way users work with pcb (GUI users as well as command line hackers) I usually write a short description to this list to see wether I've overseen use cases and to collect opinions about changes (if there are ones). There's also a number of bug reports on Launchpad with patches attached. Reviewing them for committing them to the Git repo should be a good start to get an idea how the pcb stuff is coded. Compared to other open source projects it's pretty tidy. Markus -- - - - - - - - - - - - - - - - - - - - Dipl. Ing. (FH) Markus Hitter http://www.jump-ing.de/