delorie.com/archives/browse.cgi | search |
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=gmail.com; s=20120113; | |
h=mime-version:in-reply-to:references:date:message-id:subject:from:to | |
:content-type; | |
bh=Ncr6YAA0y6VEacWUoZzNZsumt4WNK8cTbx8eQKXFG4I=; | |
b=LZB2gcrtW9h9AFs39ZwY/lKS98keM68aq3207RLTwgam0k7D+PPisMeIRTUHXj5Kjt | |
1Nl2qpa8DJaIqPqONdWX2rgizWqK1YXe8rr9PTdcuFhaNpKlTJJsQrpE5K3+K9BXzgPq | |
X7KMzGTUOVL/eG98C2e8FEJu8hfIVhr1PXrWeA0AAHGthylQH5P/O9CJ5y8O3nr8foPB | |
fDc1L+NP/71SrkJgO+XpbQ4LEMnPGCVkvV4IHzATP6M3mko/ybVXvU2nxybPb9n1R3AH | |
+8cgd2Yz4vIB/6lC6rQtbHEdkQZcwELh6k5HPifE7zUlqiDYOZ/dlxwf7ruaN1M5l6yK | |
3hIg== | |
MIME-Version: | 1.0 |
X-Received: | by 10.112.190.10 with SMTP id gm10mr33071279lbc.2.1436816931798; |
Mon, 13 Jul 2015 12:48:51 -0700 (PDT) | |
In-Reply-To: | <CAM2RGhQ70Pex5aNeQ86vKHc7sKf_Vpws69__CPb2QKg6fJTeHg@mail.gmail.com> |
References: | <CAM2RGhQ70Pex5aNeQ86vKHc7sKf_Vpws69__CPb2QKg6fJTeHg AT mail DOT gmail DOT com> |
Date: | Mon, 13 Jul 2015 15:48:51 -0400 |
Message-ID: | <CAM2RGhQ_RfN4x=s7BBy_3T8tfe4aNER-FRBOV_9wbo=90eMcbQ@mail.gmail.com> |
Subject: | [geda-user] Re: The new to do |
From: | "Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> |
To: | geda-user AT delorie 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 |
This is the order I imagine things happening in. 1. Fill in missing documentation on gEDA starting with libgeda and moving to gschem. 2. Make an API that allows for C instead of Scheme. 3. Add code to libgeda to support going from netlist to edited schematic file. 4. Write a back annotation tool netlist to schematic via libgeda. (exactly how is t.b.d.) 1. Fixing the 45 degree preservation patch so dragging works (Lilith Bryant) 2. PCB clean up documentation so that people can actually code with out heroic measures. 3. Clean up PCB's concept of a design with a unified data structure 4. Add netlist export to PCB to facilitate back annotation Documentation meaning adding to doxygen and/or an over all architectural document. -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |