5/25/2023 0 Comments Unarchiver one![]() ![]() ![]() I do not understand what would be the problem with project specific libraries, or even why there would be any problem at all with them. ![]() The “unarchiver” would take only files with this extension and would unzip the project and move the -archive.lib file and remap the path in project sym-lib-table I’d just add one final step where I’d zip all relevant files into. I’d base it on python (KiCad’s) use tkinter for GUI and reuse the business end of my plugin. I’d probably go for standalone tool and I’d reimplement the archive part also. If I would do it though, I’d firstly have to think whether I’d want this as a stand-alone tool or as an action plugin. It is doable, but as I am short on time and as I personally would not use such a tool I will not be the one implementing it. I strongly advise putting it anywhere else.Īs for the “unarchiver”. I can only see this working if you would want to put the -archive.lib file into a specific subfolder within the project folder. You can move the -archive.lib file anywhere you want but you’ll have to change the path within sym-lib-table. The -archive.lib file is project specific library which is referenced by project specific sym-lib-table file. The main benefit of having our own copy of the official repo is that we can add assets which can not be accepted in KiCad repo due to licensing issues (mainly the requirement to not redistribute 3D models). We don’t change any assets already in the library. We base our libraries on KiCad official libraries, but we have our own copy (private repo) where we only add assets. Any asset that is used in the project and exists only in user or project specific library has to be put in the common (shared or global) library and used from there. What I’ve found out was that the easiest setup for collaboration is to use common (shared or global) libraries only. Thus any changes to the libraries from that point onward do not affect the project. The main goal of the plugin was to archive the project once the PCB went into fabrication, so that all of the assets for the project are contained within the project folder. The plugin is not really usable for collaboration on a project, as you’ve found out. That would speed the process of transferring a project to a distant site while setting up the machine at that site so that the distant team could make changes to the design.Īlso, could I ask that one of the “archive” button or the “archive_project” action plugins have a name change? Perhaps the action plugin could become “Make project portable”? They work very differently from what I can see and having names so similar make it very confusing to the user. My ideal solution would be MitjaN’s action plugin with another unarchiver action plugin which would allow the user to ask the user to which folder the unarchived symbol should be placed. I haven’t tried adding a symbol to this library but to do so seems counterintuitive. If I use MitjaN’s “archive_project” action plugin, I get the -archive.lib file in which all of the symbols used in the design can be found, however, this is also a little awkward to use also because all symbols are in the “archive” library. This means that the distant machine must be a clone of mine. However, when I send the resulting zip file to a distant machine, the file when unarchived doesn’t work unless the distant machine has the symbols and footprints in the same places. The “archive all project files” button does archive the project. I need to archive a project so that it is portable and can be worked on by a team located elsewhere.
0 Comments
Leave a Reply. |