The majority of project manipulation functions seem to be located in libgerbv, so I suggest moving the file load/save functions into libgerbv too, as they are currently in gerbv application. This would benefit those writing their own code on libgerbv requiring persistent storage.
E.g. I have an program which builds a project automatically by scanning a directory using rules on the file names. I can programmatically export a PNG from this project, but I can't save it (in order to edit it later in gerbv) without making my own copy of gerbv save function.
Or can anyone tell me why this is not a good idea?
Log in to post a comment.