On Sun, 2008-09-28 at 07:01 -0400, Ales Hvezda wrote: > > Option B. External program > > Plop down a light component. Save the schematic. Run an > external program to specify the footprint and the appropriate logical > to physical mapping is applied. Run gnetlist, and then layout. > > I have always been under the impression that people would prefer B since > they could replace the default/supplied mapping program with something of > their own choosing. If it was built into gschem, it would be harder to > replace/modify/etc... But what do I know, I've been known to be wrong > often enough.
I tend to work almost exclusively in gschem now the multi-attribute editor is non-modal. gattrib still gets to play if I forget to set a footprint= attribute before I copy-paste that symbol all over the page. If we make it an external app, lets make our stock app a GUI one, and have it launchable from gschem, which can interact in real-time with the schemaitc. (Implementation detail: DBus + magic ;)). I'm of the opinion that the .sch file should still end up containing all the required design information, even if we use a helper app. to fill in some of the blanks. The only exception to this feeling would be if the schematic stored some attributes suitable for keying into a database which are picked up by a gnetlist "back/front" end. This said, it would still be nice to see the schematic cache the results of any database lookup, so they can be distributed eaily to other parties who might not have the same database setup. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
