Re: New Leo "Package" File Format?

On Sat, Apr 1, 2023 at 4:04 PM David Szent-Györgyi wrote: > I have seen this function referred to as "Pack and Go" in other software > that is widely used - SolidWorks, AutoCAD for starters. See #3238 . I'm going to keep this simple for

Re: New Leo "Package" File Format?

Now this is interesting! I wasn't considering huge image files, most just "ordinary" ones like photos, screenshots, or graphs that would be common images to want to include with, for example, a markdown document. I'll read up on your links. Thanks! On Sunday, April 2, 2023 at 5:18:24 PM

Re: New Leo "Package" File Format?

On Sunday, April 2, 2023 at 3:55:31 PM UTC-4 tbp1...@gmail.com wrote: It seems to me that the main challenge would be for Leo to know just what to have in the package. External files would be easy, but for example image files - how to know about them could be a real challenge. I'm thinking

Re: New Leo "Package" File Format?

On Sun, Apr 2, 2023 at 2:55 PM Thomas Passin wrote: > That's good to know. It seems to me that the main challenge would be for > Leo to know just what to have in the package. External files would be > easy, but for example image files - how to know about them could be a real > challenge. I'm

Re: New Leo "Package" File Format?

That's good to know. It seems to me that the main challenge would be for Leo to know just what to have in the package. External files would be easy, but for example image files - how to know about them could be a real challenge. I'm thinking that an outline could contain an @resources node,

Re: New Leo "Package" File Format?

On Saturday, April 1, 2023 at 10:06:06 PM UTC-4 mys...@gmail.com wrote: 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. Given use of the appropriate codec, Zip files are easily packed or unpacked. The zlib

Can Leointeg Achieve Near Parity With Leo?

I've need thinking about leointeg and how I've been using Leo. This has generated some thought and questions, so I thought I'd air them here. Felix has done magnificent work with creating leointeg, no doubt about it, and I hope he will post some of his thinking here. One topic is about

Re: How can I keep md-content in Leo instead of importing it?

I use ReST more than MD, but they should work the in a similar way. For Leo trees that are intended to be used by Sphinx, I just make the headline of the top node start with @rst. Otherwise I just put @language rest in the body of the top node of the tree. The rst3 command creates a ReST

Re: How can I keep md-content in Leo instead of importing it?

Sorry, folks, found a thread back in 2020, where the appropriate setting is described: @bool create-at-persistence-nodes-automatically = True Seems to work, but: Any caveats to watch out for? Cheers Paul On Sunday, April 2, 2023 at 4:31:36 PM UTC+2 p.os...@datec.at wrote: > I recently started

How can I keep md-content in Leo instead of importing it?

I recently started to document some of my Python projects using MkDocs and mkdocstrings. I write all markdown text using Leo, of course.That makes it possible to use clones for stuff being important to more than one MkDocs document. Alas, all clones are just copied on import (of course) and the