I think it's really important to show how things were made with visuals like this. This is very cool, and will likely inspire others into using KiCad and then being able to show their family and less tech-savvy friends how they progressed. :-)
I completely agree! A big part of the educational project behind this kit is not only to have a bunch of small exciting intro activities for novices, but to have all the resources that a hobbyist would need in order to recreate the creative process behind the process.
I would love to teach not just the intro electronics lessons, but the entire social/technological/ecomonical process behind the creation. We are aiming to have an "Engineer's Diary" write up that includes all that information.
I wonder how hard a tool to do this could be. Probably not too hard, as long as the window is maximized, you can specify the coordinates beforehand and just leave the screenshot program to do its thing.
The only wrinkle would be that taking screenshots based on intervals isn't as interesting as taking screenshots based on activity, but that doesn't seem insurmountable.
It depends on whether you want to show the particular thing being designed (like in this post) or to show the entire process. There is an esthetics issue with showing the whole thing: all of the small undo/redo steps and panning around makes for a jittery experience. Occasionally that looks good, but it is less easy to pull off.
It's basically a similar problem to Github's arbitrary filetype web preview notion. If you can preview the repo state visually, you can animate it over time. The issue is that n-dimensional datasets (including PCB traces) do not have a standard 2D visualisation, which requires tradeoffs, which means one size does not fit all, which means hassle factor works against mass uptake.
9 comments
[ 3.6 ms ] story [ 30.6 ms ] threadI would love to teach not just the intro electronics lessons, but the entire social/technological/ecomonical process behind the creation. We are aiming to have an "Engineer's Diary" write up that includes all that information.
Timelapse of a Sketch doc.
Timelapse of a code repo.
Timelapse of a painting.
The only wrinkle would be that taking screenshots based on intervals isn't as interesting as taking screenshots based on activity, but that doesn't seem insurmountable.