Aeon timeline 2 windows version11/18/2023 ![]() ![]() I haven’t figured which hashing algo is being used, and honestly, I don’t feel like spending time on this. Every event has a hashed identifier of length 21 which will need to be added to a (new) event/entry. But writing back to it looks like a hard problem. Reading the JSON of an Aeon file into an external DB is solved. The jellyfish above is actually from an entry in the “Feature Overview.aeon” example that comes with Aeon TL. I also learned that the binary part of an *.aeon file are attachment(s) to an event. Your updated script is working very well! I like the level up/down trick - haven’t thought of that. Apart from that, there was also once talk of an API for synchronization, but I don’t know if that has been realized yet. If you want to send data to Aeon 3 with your own program, the csv import might be the easier way. By the way, this was the decisive reason for me to stay with Aeon 2, whose format I can read and write completely, which I use for synchronization with yWriter. Thus the Aeon 3 format can be read by third-party software, but hardly written. However, the Aeon3 format adds an extensive amount of redundancy, which, as far as I understand it, is supposed to speed up loading, because it takes over various program states directly. By the way, so far this is also true for the Aeon2 file format. ![]() That is, it is quite an extensive tree full of cross-references, which in turn are defined in other sub-trees. The file format is not easy to figure out, because the flexibility of the software is reflected in the data structure. My extraction script separates the JSON part, formats it and saves it in a text file. The Aeon3 file, as I know it, is composed of a JSON part and a binary part.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |