Hi
i have an idea and know it’s (most probably) not one of your concerns or priories, but i started to think about it for a while and hope you find it interesting as an idea.
font sources from start to finish have an undo/redo history for all glyphs, but every time when closing the app and opening again, it’s getting disappear. we can tack backups of the source in several points or creating backup layers in the same source, or even using somethings like git, but these have some limitations or complexities imo. if undo/redo history implemented in one source somehow, helps things go easier(costs are: heavier size, complexer system to support different versions of Glyphs software components, maybe more crash reports! ,…).
to implement such system i have some thoughts, i name it ‘snapshot’. a concept like this:
glyphname = A;
currentsnapshot = 0
snapshot = -1 {
# glyph data...
}
snapshot = 0 {
snapshot(-1).node(34).transform.move(x) = -5;
}
snapshot = 1 {
snapshot(0).transform.skew(pivot=topright)= -1.5;
}
snapshot = 2 {
snapshot(1).filter(id=0x00fb, name= Round, ver=1.02) {
#filter parameters settings
}
snapshot = 3 {
#new glyph data
}
...
}
(i made up the codes from myself to present the examples)
sidenotes:
1- more and more snapshots will make the source file heavier, so one idea to solve that, could be to write them at a separated file.
2- i didn’t talk about branches, where we going back to a snapshot and start to change it, we actually make a new snapshot in the past, so the next snapshot(s) either must be deleted or considered as a new branch(this is not exist in a regular file with undo/redo history). for complex efforts and much snapshots and branches, we need a tree diagram.
3- an option should be available to purge snapshot records for selected glyph(s)
