better filesystem integration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zim |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
tags:whishlist/
It's clear that zim can turn any folder into a notebook and/or that zim can almost(see issue 1 below) be considered as a file browser that displays notes related to the file-tree, and the first part of that claim is noted in some of the documentation.
However, the traditional way to use file folders is to have a README.txt INSIDE the relevant folder.
So traditional:
Topdir
subdir1
README.txt
subdir2
README.txt
Zim way:
topdir.txt
topdir
subdir1.txt
subdir2.txt
subdir1
subdir2
This is more cluttered when viewing the contents of topdir and there are related problems and bugs:
1) .txt file bugs. There are about 3 of these in the bug tracker, slightly different but all related to the fact that zim cannot tell a zim file from a txt file. The traditional method can use a single zim.txt at least, instead of arbitrary filenames, thus solving these bugs in the same way the readme has always unambiguously been the readme.
2)Presently zim only looks at one layer of folders below a page and if that folder has no corresponding txt file, while it will provide access to the folder as a stub, it will NOT navigate below that folder. This breaks interoperability of zim with standard filesystem usage. Ie.. you can't just use zim to browse a directory tree... adding notes only when and where desired. This issue could be fixed by itself though.
3)Moving directories outside of zim... ok, this is a sticky point anyway, but if the notes are in the directory at least that stays together more naturally. Of course moving from outside of zim still breaks links. It's possible to imagine fixing that too maybe by embedding a UUID or such in each note, translating to plain text links on edit view, and translating plain-text links to UUID links upon creation or discovery. This only works if pages stay within some defined and searched top directory.
I do understand that this is a grand departure from the present zim way, probably beyond the zim programming resources, and that backward compatibility would require a converter. But I'm floating the idea anyway, because I really like how universal it makes integration of a wiki and ordinary file organization. Most of my notes relate to files. It's not that I attach a few files with my notes.
A couple of the related .txt file (issue 1) bugs that wouldn't exist in the modified arrangement:
https:/ /bugs.launchpad .net/zim/ +bug/931901
https:/ /bugs.launchpad .net/zim/ +bug/705479
https:/ /bugs.launchpad .net/zim/ +bug/1162270
https:/ /bugs.launchpad .net/zim/ +bug/787850
And apparently issue 2 has been reported too:
https:/ /bugs.launchpad .net/zim/ +bug/1097742
One related to the general clutter created by having files mirroring every "attachment" directory but not in it:
https:/ /bugs.launchpad .net/zim/ +bug/1580639
I think my idea improves that situation and the precise issue described in that bug is a huge part of why I filed this one... to be able to have zim coexist in shared work environments without necessarily requiring other users to care much about, or be bothered much by zim being there. Even if un-hidden, if people just see a zim.txt in every directory, that's much less intrusive/ unusual/ distracting than every directory having a similarly named txt file outside of it.