Paul, Yes I am overloaded. Keep in mind that my work as of today is not included in geda it is in a fork of geda. I am trying to make it possible to use geda applications as a front end for my efforts. I am also trying to make it easy to translate to and from other eda tools.
I am as time allows working on three documents 1) mra_netlist users guide This is meant to instruct users on how to run the netlister and includes examples/screen shots. 2) libakeda gschem interface manual How to write front end file reading scripts How to write middle data structure manipulation scripts How to write back end output file scripts All the available scheme extensions that libakeda provides the intent is to make it easier for users to write scripts as well as open a dialog on what the interface should include. 3) libgeda & gnetlist and libakeda & mra_netlist netlist explanation This is a review of the netlisting algorithms/process that the two systems provides with the intent being to make it easier for other developers to modify the underling code as well as debate the merits and efficiencies of competing algorithms. I also have paying work that drives a lot of my requirements. The use of out side contractors made my netlister support (modify the geda pads back end) and has left the board layout in a pads ascii format. I want to bring this project back into pcb so I have been working on a python script for translating pad's ascii format to pcb this is about 80 percent complete. This pads ascii to pcb also needs to work the other way from pcb to pads ascii so that pcb fabrication and assembly shops can program their flying probe tester. If it isn't obvious I have a lot that I am chewing on, hopefully some of it is of interest to others. Have fun, Steve Meier On Fri, 2009-01-09 at 01:06 -0500, Paul Tan wrote: > Hi Steve, > > Great! I am very much interested to see any added > flexibilities included in gEDA. Please don't get me > wrong, I am all for it. > > I know you are very busy and its very difficult > to discuss all the details. Do you think an > example, or a screen shot may help? > > I do appreciate very much your effort and time > to discuss the BUS subjects. I know we all want > to see gEDA successful. Thanks again, Steve. > > Best Regards, > Paul Tan > > > -----Original Message----- > From: Steve Meier <[email protected]> > To: gEDA developer mailing list <[email protected]> > Sent: Thu, 8 Jan 2009 9:31 pm > Subject: Re: gEDA-dev: Google Summer of Code 2009 > > > > Paul, > > In my non-stock version I have additional flexibility not reduced > flexibility. Again, others can continue to use the stock version. > > One of the reasons for open source is to allow users to modify code for > their needs and desires. This is the free as in speech not free as in > beer. > > Steve Meier > > On Fri, 2009-01-09 at 00:22 -0500, Paul Tan wrote: > > Hi Steve, > > > > I am all for changes that do not impose > > contraint and do make things more flexible. > > I do raise concern if changes are imposed to > > constrain gEDA flexible architecture unnecessarily. > > > > Best Regards, > > Paul Tan > > > > > > > > -----Original Message----- > > From: Steve Meier <[email protected]> > > To: gEDA developer mailing list <[email protected]> > > Sent: Thu, 8 Jan 2009 8:58 pm > > Subject: Re: gEDA-dev: Google Summer of Code 2009 > > > > > > > > On Thu, 2009-01-08 at 22:19 -0500, Paul Tan wrote: > > > > > > > > Is it necessary that Gschem and/or Gnetlist > > > C/SCM has to changed to accomodates your way > > > of implementation? > > > > > > Best Regards, > > > Paul Tan > > > > > > > No it isn't necessary Gschem and/or Gnetlist C/SCM change. That is > why I > > have my own non-stock version. GEDA et al can continue on anyway it > > likes as long as the file format is well documented. I do appreciate > > Paul's work where gschem allows the setting of pin types. > > > > Steve Meier > > > > > > > > _______________________________________________ > > geda-dev mailing list > > [email protected] > > http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev > > > > > > > > _______________________________________________ > > geda-dev mailing list > > [email protected] > > http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev > > > > _______________________________________________ > geda-dev mailing list > [email protected] > http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev > > > > _______________________________________________ > geda-dev mailing list > [email protected] > http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
