On Wed, Mar 29, 2023, 11:48 Thomas Passin <[email protected]> wrote:
> There is a perennial problem when one wants to give a Leo outline to > someone else. It happens when an outline contains external files, or > images to display, or any other data files that might be needed. For > example, an article written with the Viewrendered3 plugin in mind, or for a > Sphinx document, must have its resources available or it cannot work. <Snip> This is the main reason why Audacity decided to move to SQLite as its file saving format in v3.0. Someone would have an AUP file and not every one of the .au additional files to go along with it and wonder where their project went when they tried to move it. I assume they wanted to make it something that was simply usable in the program as an extent API, however this does have the issue of not releasing space from the save file until an unsaved session is completely closed. [Truth be told I'm not a huge fan of the SQLite format myself, and would much prefer a mysql server in almost every use case.] It seems it took audacity ~2 years to implement this as a lasting format change from the point it was mentioned as a pull request until it became cemented in version three of the program. Having a zip file of all file assets would work as well with some implementation of a VFS by the program utilizing it I presume. Mike -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAN%2B%2B4hFhqEhg_RCXrBetDm%2BD6J%3DTv880cQROF2DTLpmS26whFQ%40mail.gmail.com.
