On Fri, 2008-01-04 at 01:42 +0000, Robert Fitzsimons wrote: > > I'd personally suggest using a directory with .sym files, rather than > > using a "magic" .sch file to embed all locally instantiated / edited > > symbols, although as you'll read below, this could all be a back-end > > detail. > > I guess a filesystem backed solution would work, might be some issues > with portability if you want to implement project hierarchy or sharing > within/between projects.
Files are fairly easy, portability wise. (Assuming you mean cross-platform portability?). > I'm not sure I'd want to have to duplicate the symbol data for each > customized component, but being able to reference a symbol/component > file from another component file would work. So you could have > something like this: > > ./db/ > ./db/capacitor-1.sym > ./db/capacitor-1_0805.comp > ./db/capacitor-1_0805_0.1uF.comp > ./db/capacitor-1_0805_1uF.comp > ./db/capacitor-2.sym > ./db/capacitor-2_ta3216.comp > ./db/capacitor-2_ta3216_10uF_16V.comp > ./db/capacitor-2_ta3216_100uF_10V.comp Ok, I understand.. I hadn't thought you'd be modifying the symbol so many times. You're looking at "light .sym" + "delta" => component here? > > If we can teach gschem to edit a symbol from a memory buffer (dropping > > the implicit assumption of a filename, but adding that of some "save" > > callback), then saving (in this case) be hooked up the new component > > source write API, or to update the embedded data in the embedding case. > > This may not be needed because we could have a modal dialog which allows > a customized version of a symbol to be defined/edited. Please, no more new modal dialogs. There are still a few existing ones which I've not managed to kill off yet ;) Ok, I accept some interaction dialogs might want to be modal, however editing a symbol is probably something we don't want to be modal. -- 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
