>> I really don't like that idea, we were supposed to be improving that >> workflow, not removing it. > > Again, we're optimizing the common case, not removing the ability to > do the old ways. Backwards compatibility is spelled out in the SoW. > So, the old gsch2pcb still works, you'll be able to manually feed anno > actions to pcb, etc. But 90% of the users just push the update > button.
Just to clarify, my vision is that the old gsch2pcb program (and its friends) will be modified to emit an action script instead of a .pcb.new file. Updating gsch2pcb is intended to be outside the SOW. I envision that I (or anybody else with rudimentary programming skills) could do that work in parallel with DJ's work, once the action script file format is defined. On the subject of the action script, ummm, DJ have you thought about what it might look like? My idea was to make it Scheme like, similar to what gEDA/gaf uses. However, please *don't* use guile to parse/process it. We've had too many issues with the guile folks changing the API & breaking gEDA/gaf, as well as the usual dependency problems. Rather, if we could use tiny scheme to handle the forward anno file, and build the tiny scheme interpreter into PCB, that would be cool. Of course, I'm not wedded to a Scheme-like file format; it just seemed to be easy to use and there are plenty of tools available to take advantage of. But if you have a better idea which minimizes your work & doesn't re-invent the wheel, that's cool. Cheers, Stuart _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
