the patch does not actually fix the issue, because it starts a file-manager directly with the internal repository path, which is private by definition. All file transactions by the user must be done through the private DAV interface given by the process called "presenter.py" on port 6222. The "physical" repository should never be accessed directly, only readonly access might be useful, but as soon as one wants to perform write operations, the crypto-layer must be inbetween! See http://angelapp.missioneternity.org/index.py/OverView

Thanks for the tip. I will test this out and see if it can improve how we open things in a browser.
I have written the fix for opening things in the file manager, but want to test it against several managers before I commit.

Ok, looks like the way the platform wrapping is done, I should be able to refactor showRepositoryInFilemanager to work similar to how showURLInBrowser works, which was done pretty well.

Currently, to open the repository in the "file manager", wx.Execute() is called with "start" being the program that gets executed. Essentially, this relies on the fact that a program called "start" is

a- available
b- knows how to handle a URL

This is unoptimal and has unpredictable behaviour (e.g. hard to support).

TODO:

How does one do this properly?
Specify implementation.
Implement.
Test.