Hi All, Sorry, I sent the previous message to the wrong subject tree. Since this subject may be of interests to others, I am re-sending this under the new subject.
Best Regards, Paul Tan -----Original Message----- From: Paul Tan <[EMAIL PROTECTED]> To: [email protected] Sent: Tue, 20 Nov 2007 9:15 pm Subject: Re: gEDA-dev: gEDA-user: Schematic Level DRC DIscussion Hi Steve Meier, You have quite a good list of valuable features for the guile api. For a while, I have been thinking of doing the following: Add several user configurable "Script buttons" in the gschem window icon menu bar, such that the user can configure gafrc to define the "button label" and the pathname of the script each button would execute. In order not to limit the script to scheme only, but also support other popular script such as python, perl, ruby, bash, cint, etc., any script with a sha-bang (#!) would be supported either directly or indirectly. A way to pass the current schematic/sym filename to the script is needed so that the script can make use of it with ease. I wonder if you already have something similar to the above in your plan. If not, do you think if something like that would be useful for gEDA users in general? Best Regards, Paul Tan ======================================================================== On Fri, 09 Nov 2007 20:35:00 -0800, Steve Meier wrote: > My guile api plan is. As I add guile functions I add to the documentation. > 1) Support for guile scripts to read and write schematic files and > symbol files. (Reading of schematic files is now complete) > 2) writting of guile scripts for both the stock geda and my non-stock > version. > 3) function for displaying page structures. (completed) > 4) Functions for controlling the swapping of symbols into schematic > pages. (C code exists) > 5) Support for retrieving and modifying attributes to guile. > 6) Control of the netlister functions. Generate page level netlists and > buslists. Generate project level flat netlists. > 7) Fetching of nets or buses from the page or flat page. > 8) Fetching of pins from a net > 9) Fetching of parent devices from pins > and as each step progresses document document document. > I think that given a net list you should be able to ask each pin's > parent about voltage limits. The net should know the expected voltage > levels. Did we smoke? Similarily for signals I would like to ask about > logic families do we all agree. How about asking if there is multiple > drivers for a net? are they all tri-state? > Please think about the types of questions you would ask the data > structure? Where would the answers have to come from? pin, device, net? ________________________________________________________________________ Check Out the new free AIM(R) Mail -- Unlimited storage and industry-leading spam and email virus protection. _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev ________________________________________________________________________ Check Out the new free AIM(R) Mail -- Unlimited storage and industry-leading spam and email virus protection. _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
