The "import->import any file" method for .db3 files no longer
works for me, and does, in fact create completely empty nodes titled
after the file (@auto nodes). Thus I cannot repeat the process, and I
was hoping someone could figure out how I got that result, if Leo *doesn't*
support .db3 files. And trust me, I have better things to do than make
up stories for Leo developers. I can't repeat it, but it *did happen* ; )
With sqlite3 files importable as xml (as shown) I knew it would be
relatively
easy to write my plugin, so hopefully you can understand my disappointment
upon finding that the imports no longer worked, and why I asked for help.
Hmm, SQLite files are binary and I don't remember Leo having any
> support for them, so wouldn't have expected that to do anything useful
> - can you verify you can do it repeatably?
>
> Building an outline in Leo based on the content of SQLite file with a
> Python script wouldn't be too hard, but you'd need to know the
> structure of the data in the SQLite file and how you wanted to map it
> to Leo's tree.
>
> Cheers -Terry
>
--
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.
