Luke Frisken
Luke Frisken
Great thanks!
Looks like it should be possible now with https://github.com/iced-rs/iced/pull/1830 completed
Okay I have a proposal about how this change tracking could work. ## Requirements + All data related to tracking state needs to be available in plain text in the...
We will need a way for translators to interact with this system. The long term goal is to create a GUI for #83 which could be used to do this,...
Perhaps the design could be simplified by not using git hashes, but rather by searching back through the history to find the file that matches the file hash.
@alerque > Not duplicating data like checksums that could be deduced through other tooling would be a huge advantage. I do suggest looking into that. I'm not sure I understand,...
> Sure, happy to try to explain and maybe even help work on this. I would definitely love to collaborate with more people on this project if you have some...
Edit previous post: wrong emoji!
> I'd go for the former myself, but then I'd also avoid JSON like the plague if I had my druthers. Either way it's the same information with different parsing...
To add to this proposal I would like to try to make the change tracking generic over the source of messages, and also have a plugable storage backend. I don't...