Any way to export?

[anthrolisp]

Is there any way to export one's data? Many thanks in advance!

[deadjakk]

it would be great if there were a option to use a designated directory that maintained "real" files so that the data could be edited/read/exported instead of placing the content into the voidmap itself.

[Alch-Emi]

Considering implementing this myself. I know this thread is 2+ years dead, but what sort of format do folks think would be appropriate for this?

I'm thinking plaintext, with each node on one line, one tab per indentation level off of the root node. It'd lose node position and arrow data, but it's closest to how I would be representing the data if working just in plaintext + my editor

[deadjakk]

I think this was about exporting the information from the nodes using txt:blah at least in my case, that's what I want(ed).
So after hitting some keybinding, you could be prompted for a root directory name and then it could create a directory tree containing each of the nodes' names at their respective level. Any final 'leaves' could be an empty text file with the name of the leaves. If the leaf is a txt: node, then the plaintext leaf file could contain the same plaintext information within the txt: node.
You'd of course have to account for multiple root nodes and txt: nodes that are branches but it's do-able.
So for something like :

The following could be generated:

~ $ tree Some\ note/
Some note/
└── something
    ├── level
    │   └── another_level
    │       └── final.txt
    └── something.txt

3 directories, 2 files

[plavcik]

I see two possible future requests.

1st export binary void.db to human readable format, at least TXT, but formats "supporting" trees can be usefull to. Workarround for TXT is copy/paste from void terminal to text file in other terminal.

2nd export or even use nativelly tree structure on filesystem (advantage, you can use other tools for editing, searching, copying, deleting, .. void started at some level will take root from that part, challanges: encoding, unix vs dos end of lines, name of files in UTF-8, .. ) the native use of filesystem looks too complex
Jiří

[deadjakk]

I see two possible future requests.

1st export binary void.db to human readable format, at least TXT, but formats "supporting" trees can be usefull to. Workarround for TXT is copy/paste from void terminal to text file in other terminal.

2nd export or even use nativelly tree structure on filesystem (advantage, you can use other tools for editing, searching, copying, deleting, .. void started at some level will take root from that part, challanges: encoding, unix vs dos end of lines, name of files in UTF-8, .. ) the native use of filesystem looks too complex Jiří

Well with the idea of using the filesystem tree as a possible export format is also the idea of creating an import/build function from the filesystem. this could be useful for visualization of a number of projects, such as project notes, code files, mdbooks, etc. lastly the implications of this is that void could then function as a way of altering file structures in a visual manner from the terminal without really impeding or redefining it's originally intended purpose.

Also if you had to make a number of changes to a lot of nodes or files within nodes, you could do so by exporting, make mass changes to the files, then re-build (import) the void map from the tree which is a neat help.

Just throwing out ideas.

[metaory]

I made db files human readable and editable with any text editor

JSON Storage Migration #67

@anthrolisp @Alch-Emi @deadjakk @plavcik

[metaory]

Now I can have other tools integrated with void,

Early idea phase now,

Rough idea is to have Void node created and synced with certain magic tags from some markdown or maybe bi-sync

Markdown <---> Void
    ^            ^
    |            |
    v            v
Other Tools    Other Tools