> al davis wrote: > > One feature I would really like is a way to back-annotate > > those changes, a way to update the schematic other than > > manually changing the values. > On Monday 11 June 2007, John Griessen wrote: > I like the idea of a separate place for commands to > simulators via symbols on the schematic that are probes -- a > pictorial symbol of a lab instrument. The separate place > should be non-volatile and outside the schematic, so it's a > file. If you are using DBUS or any IPC to do cross probing > and back annotating that method should also update the file > with every change, and take in every change to the file. In > other words any IPC dealing with back annotation should poll > the probes file and keep it in sync with the memory resident > version of it. > > And so far, that probes file seems to be best made in > resource file format.
I was thinking of something much simpler and more portable, like a way to back-translate a file, or back-annotate a file. How about ... You draw a schematic, save it, convert to a format for simulation. You simulate, it isn't quite right, you modify through the simulator, repeat until it works the way you want. You save the revised circuit in the simulator's format. We have this. Now you want to update the schematic. If the changes are simple, such as component values, it would be nice an easy way to modify the schematic file to include the changes. The best way is a stand-alone program, or maybe something like gnetlist working backwards. I think DBUS or other IPC adds a lot of complexity across the board, and will never happen. The complexity added to one program might not be significant, but requiring everyone to play that way probably means they just won't. Remember there are lots of related programs we don't have yet, and lots of people developing them that we don't know yet. _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
