PCBWay - seeking help/developers for automating KiCAD data parsing/checking


#48

I stand with my guess of two years after v 5.1 is released (So at least 3 years from now) Kicad 6 development has not yet officially started!!

If there is more money this will simply mean more of the planned features will be implemented :wink: There is already talk of putting some nice things for the symbol file format on hold for version 7 as the devs fear they can not be finished till v6 should be released.

v6 will be a lot of busy work where the users see little of it. Rewriting the file format takes a lot of effort and is simply there for preparing for future ideas. Only after the new file format works reliably will it be possible to add new features. (So my personal guess is: kicad 6 will be the file format change without adding new features to the file format. Version 7 will add all the inheritance stuff that gets us lib maintainers excited.)

One good thing that will come with v6 and the new file format is that the whole cache and rescue lib stuff can be finally retired as the symbol data will be included in the schematic file. (so like the pcb side you can then update from library on user action)


#49

When do you mean this check is done ?

@ PCB_Wiz Begin to review files as they upload PCB file, Our factory engineer use CAM350 to audit the file. We didn’t find the suitable gerber check can achieve this,I think engineers here can make this.


#50

The problem is in Cairo, which doesn’t deal well with large zoom levels at all. It becomes visible when we render through wx, because the zoomable canvas class in wx configures a large zoom level (the legacy canvas uses mils as coordinates for eeschema).

So no, the bug won’t go away, but it won’t affect us anymore, and we have that part of the code under control, rather than requiring users to compile a patched Cairo library.


#51

Some nonsense removed
Locking this thread now


#52