Updated Development (markdown)
parent
e5fc7451fc
commit
6a20a9d229
|
@ -1,3 +1,11 @@
|
|||
# Tuhi GUI vs Tuhi server
|
||||
|
||||
Tuhi has (currently) two distinct components: a DBus session daemon that performs the actual communication with the device and a GUI component that talks to that daemon. These are two separate processes started by the `tuhi` executable.
|
||||
|
||||
For development, both components can be started separately via `./tuhi-server.py` and `./builddir/tuhi-gui.devel`. Note that the server component is started from the source directory, it doesn't need to get built.
|
||||
|
||||
In the source tree, the server is in `tuhi/` and the GUI is in `tuhigui/`.
|
||||
|
||||
# Resetting devices
|
||||
|
||||
Tuhi stores the device data in `$HOME/.local/share/tuhi/<btaddress>` (i.e. `$XDG_DATA_HOME`) The primary file is `settings.ini` which is how Tuhi remembers devices it has already seen. Removing that device and/or the whole folder makes the device unknown again and the device has to be re-registered.
|
||||
|
|
Loading…
Reference in New Issue