mirror of
https://github.com/tahoe-lafs/tahoe-lafs.git
synced 2025-01-19 19:26:25 +00:00
The Tahoe-LAFS decentralized secure filesystem.
2f2de9df2e
Previously, once the node itself was launched, the UI event loop was no longer running. This meant that the app would sit around seemingly 'wedged' and being reported as 'Not Responding' by the os. This chnages that by actually implementing a wxPython gui which is left running while the reactor, and the node within it, is launched in another thread. Beyond 'quit' -> reactor.stop, there are no interactions between the threads. The ui provides 'open web root' and 'open account page' actions, both in the file menu, and in the (right click) dock icon menu. Something weird in the handling of wxpython's per-frame menubar stuff seems to mean that the menu bar only displays the file menu and about etc (i.e. the items from the wx menubar) if the focus changes from and back to the app while the frame the menubar belongs to is displayed. Hence a splash frame comes up at startup to provide an opportunity. It also seems that, in the case that the file menu is not available, that one can induce it to reappear by choosing 'about' from the dock menu, and then closing the about window. |
||
---|---|---|
bin | ||
contrib | ||
docs | ||
mac | ||
misc | ||
src/allmydata | ||
twisted/plugins | ||
windows | ||
_auto_deps.py | ||
.darcs-boringfile | ||
COPYING.GPL | ||
COPYING.TGPPL.html | ||
CREDITS | ||
ez_setup.py | ||
Makefile | ||
README | ||
README.win32 | ||
relnotes.txt | ||
roadmap.txt | ||
setup.cfg | ||
setup.py | ||
Tahoe.home |
Welcome to the Tahoe project, a secure, decentralized, fault-tolerant filesystem. All of the source code is available under a Free Software, Open Source licence. Please see docs/about.html for an introduction, docs/install.html for install instructions, docs/running.html for usage instructions.