Pages 'caching' doesn't plays nice with version control
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zim |
New
|
Undecided
|
Unassigned |
Bug Description
Hello there.
I've setup version control for Zim because I'm using it in collaboration with other people. I know Zim is not intended as a real-time collaborative Wiki but it's good enough with version control except when two people are editing the same page simultaneously.
However, there's a problem that really annoys me, all the pages you access are 'cached' (presumably there's a limit), so, when you access a page, it will be cached, and even if the page was edited from another Zim instance, when you go back to it, you're accessing the cached page, not the actual page that was changed on disk. This is a real problem if, for example, someone added lots of lines to that page, but you didn't see because you have a cached version, and then you fix a typo and save it, then everything the other person added will be buried in a obsolete version.
I think a configuration to disable the caching of pages (or to 'reload' a page whenever you access it) is a decent solution to this problem. Until of course you guys implement the fully-featured real-time collaborative editing over XMPP :P.
Thanks in advance.
PS: How can I install the deps for the spellchecker plugin on Windows 7?