Previous KDiff is KiRI now

[leoheck]

Hi folks. I am here to announce that the name of my previous known KDiff tool is KiRI (Kicad Revision Inspector) now. The name was changed to distinguish easily from Kidiff which is an important tool used inside KiRI.

KiRI is a tool to help easily comparison of different versions of the schematics and the layout, visually for projects that use Git as source management.

This is the updated repo URL

GitHub - leoheck/kiri: A tool for reviewing Kicad's projects visually...

Some, related topics

Diff tool for Schematics and Layout using Git

Hi guys. I am working on a simple tool (called kdiff) to make the review process on git changes easier. I am discussing a lot with @John_Pateman since this is kind of his idea for the next version of his Kicad-Diff. While this doesn’t happen, I am making this tool that is a working mockup to evaluate the idea. It also generates diffs for schematics using @jnavila Plotgitsch This is the repo https://github.com/leoheck/kdiff in case anyone is interested to experiment with it. It is possible t…

KiCad enhancement recommendations - schematic + pcb

Diff comparison is not directly supported within KiCad yet, but there are a few external projects that might be of interest. PlotGitSch This project will render views of schematic revisions and can be used to show differences between them. [svg_diff] KiCad-Diff This project renders pcbnew layouts as svg layers and uses a svg filter to overlay images and highlight differences in the pcb layout. [main1] [diff] [composite] kdiff This project is a combination of the two previous proje…

Tools for cooperation?

There are already a few projects that compare version controlled layouts (which include programs other than git) Whilst closer integration within KiCad might offer some benefits, these projects do provide some insight into how version control can already be used with EDA projects. KiCad-Diff also has a text diff which identifies simple swaps . However, merging is a different problem - it is not a matter of how KiCad files are structured, it is a fundamental issue of how to compare 2d da…

How to save intermidate states of a layout?

I create a number of folders and just move from one to the next copying all the files. As mentioned above I keep a txt file in the project to keep track of what I’ve done. This works for me because as a hobby I can afford the time to tweak the design. Say I have all connected then I want to rotate an IC.

[ppelleti]

That also helps avoid confusion with kdiff3.

[John_Pateman]

Good to see this - and hopefully will be possible to install soon via the new PCM! Like the new name too.

[leoheck]

@ppelleti indeed

@John_Pateman I am not aware of this PCM. What is this? Is this some sort of package manager? Well, if we have a package manager on Kicad 6, this version is going to rock! Well, for that happening we would need to have the new python API working too.

Have you tried to install my simple kicad_plugin on Kicad 5.1.*?

[craftyjon]

Copied my note from today to the dev list to here: Attention Python devs - 6.0 API and plugin repository info

[John_Pateman]

PCM = Package & Content Manager in latest 5.99/6.0.0RC1

[leoheck]

This is awesome guys!

@craftyjon thank you for the link.

[SembazuruCDE]

@John_Pateman

PCM = Package & Content Manager

Probably a brain-fart, but the screenshots show the acronym “PCM” as expanding to “Plugin and Content Manager”… (Not “Package”).

I wasn’t following it’s development, so the error might simply be due to a name change somewhere in development. Or your brain is as swiss-cheesed as mine is and you just remembered the wrong term.

[John_Pateman]

You are right - PCM - plug-in & content manager not package. Or anything to do with pulse codes or monthly payments for that matter. TLAs[1] should be banned.

[TLA ]- Three letter acronyms.

[hermit]

@ppelleti

That also helps avoid confusion with kdiff3 .

Gnome and KDE developers have the annoying habit of forking a project and adding a G or K to the beginning. One of the reasons I avoided Kicad for awhile is I thought it might be a fork of another project that had simply been rebranded.

[leoheck]

@hermit I felt exactly the same when I was about to start using Kicad 4.0 a long time ago. And after some time I realized this was not KDE-related stuff…