Hi,
What we do, is that we package the associated files to a data narrative
as a Fossil[1] repository, with versioned and unversioned files.
Versioned files are used for the ones where we want to track the history
and the unversioned are used for raster files (for example, PDF outputs
for the data stories or PNG/JPG) images. This gives us a pretty simple
infrastructure to exchange and publish our resources, that can travel in
a single file. It's like .zip but with history.
[1] https://fossil-scm.org
I think that, via Fossil, SQLite as an application format is a pretty
powerful tool. Some related docs and videos below:
* https://www.youtube.com/watch?v=8y_ABXwYtuc
* https://www.youtube.com/watch?v=Jib2AmRb_rk
* https://www.sqlite.org/appfileformat.html
My 100 pesos,
Offray
On 29/03/23 12:48, Thomas Passin 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.
If the outline contains @file trees and these external files aren't
included in, e.g., a zip file, those files will be blank when the
recipient open the outline. Yes, one can change the @files to @clean
and re-save them all. But that is awkward, and negates the reason for
having them be @files in the first place.
Otherwise, one is forced to create a package file - usually a zip file
- that contains the outline and any required external files and
subdirectories.
Current software, such as LibreOffice or Word, handle this by saving
their files as archives that contain all the external resources a
document needs. I suggest that Leo needs a similar capability. This
would not replace the existing Leo file format nor the existing
outline save commands. It would add new /Save/Open Archive/ commands.
How might this work? For a save, Leo would check each external file
and each @rst tree to get their paths, and then compress the external
resources and at-files into the archive. For other resources, such as
images in, say, an /images/ directory, An outline could have a new
kind of node, perhaps with an /@resources/ headline, that specifies
what subdirectories and files to include. Perhaps there could be more
than one /@resources/ node in the document.
To open an archive, Leo would expand the archive, which would create
all the directories and files. Then it would load the .leo outline
contained in the archive.
--
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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/516d7db0-e2e9-4fdf-9197-0a10f869edfbn%40googlegroups.com
<https://groups.google.com/d/msgid/leo-editor/516d7db0-e2e9-4fdf-9197-0a10f869edfbn%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/bf351b2e-f8ef-4c9a-9238-4a0dad478c8c%40riseup.net.
