On Sun, 7 Jan 2018 10:31:22 -0800 Chris George <technat...@gmail.com> wrote:
> What I envision is the ability to use a .db file to store binary > files in their entirety. The only place the file would exist is in > the .db file. So no references to the file system at all, no litter > of files here and there, just one file that contains it all. I agree that approach will be useful, but I think sometimes for some workflows the BLOBs will need to be available via the filesystem. For example preparing a paper with pandoc, it needs to be able to see the BLOBs as files, assuming they're PDFs or bitmaps to be included in the generated file. You could get there two ways, either a file system backend for BLOBs, so from the Leo end you're mainly gaining the convenience of being able to edit the BLOB associated with a node from Leo quickly without switching contexts, or with a single file backend that could export BLOBs to a filesystem on demand so things like pandoc could see them. But I think supporting multiple backends won't be hard and is maybe easier than dealing with the export on demand complexity - a single file based backend for the workflow you describe, and a file system based backend for cases where it needs to integrate with pandoc or similar. So I think we can have it all, but I also think the discussion up front's a good way to ferret out all the use case / workflow variations. Cheers -Terry > Then I could unleash the power of the outline to make sense of it > all. BLOB nodes could be placed into the outline, nodes containing > information could be appended to the BLOB nodes etc. Being able to > view the BLOB in Leo would be nice, but not entirely necessary. > > The goal, for me, would be the ability to attach information to the > BLOB and then organize it using Leo. > > Chris > > On Sun, Jan 7, 2018 at 9:22 AM, Terry Brown <terrynbr...@gmail.com> > wrote: > > > On Sat, 6 Jan 2018 21:24:26 -0800 (PST) > > tscv11 <tsc.v...@gmail.com> wrote: > > > > > Let me know if you want to look at my script in its' current > > > incarnation. > > > > It looks like https://github.com/tscv13/leo4sqlite went away - that > > would probably be the simplest / most common way of sharing the > > current state of code. > > > > I think there's still some thinking to do about how to associate > > nodes with BLOBs, and how BLOBs would be available to other > > systems, but it would be good to see your code as a reference. > > > > Cheers -Terry > > > > > When it comes to blobs it will: > > > > > > 1. insert > > > 2. extract > > > 3. view > > > 4. open > > > > > > (not sure how 'edit' should be different from 'open') > > > > > > If you give me a better idea of how you'd like it done, I'll try > > > adding the choice to > > > save outlines with the blobs. > > > > -- > > 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 post to this group, send email to leo-editor@googlegroups.com. > > Visit this group at https://groups.google.com/group/leo-editor. > > For more options, visit https://groups.google.com/d/optout. -- 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 post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
