Compare commits

...

4 Commits

6 changed files with 30 additions and 24 deletions

1
.gitignore vendored Normal file
View File

@ -0,0 +1 @@
/.hugo_build.lock

View File

@ -5,16 +5,6 @@ date = 2021-10-23T00:11:38-07:00
# ITD
{{% notice warning %}}
There is currently a bug in the bluetooth library used for ITD that will cause the following error when using BlueZ 5.62+:
```
MapToStruct: Field not found: MTU
```
This is mentioned in [an issue](https://gitea.arsenm.dev/Arsen6331/infinitime/issues/3).
{{% /notice %}}
ITD is a daemon written in Go that communicates with the [InfiniTime](https://github.com/InfiniTimeOrg/InfiniTime) firmware running on the [PineTime](https://www.pine64.org/pinetime/) smartwatch.
ITD is meant to be fast and easy to use. As such, it is is only a single binary that works on all Linux systems since it is statically compiled and thus does not rely on any dynamic libraries.

View File

@ -6,16 +6,6 @@ weight = 2
This page is about the various sections in the config, their purpose, and how to use them.
### cfg.version
{{% notice note %}}
This field was removed in [fbb7cd9bc1](https://gitea.arsenm.dev/Arsen6331/itd/commit/fbb7cd9bc1f632fb52f14f10ee76ade06b68824c)
{{% /notice %}}
This field is temporary and was added because I changed the config format a while ago and wanted to make sure no one was still using the old config with a new version of ITD.
---
### socket
This section contains options for the control socket exposed by ITD.
@ -119,4 +109,18 @@ This section contains options for music control
#### vol.interval
This field is an integer indicating how much the volume should be changed for each volume up or down event from the music control app.
This field is an integer indicating how much the volume should be changed for each volume up or down event from the music control app.
---
### weather
This section contains options for ITD's weather support
#### weather.enabled
This field is a boolean indicating whether the weather support should be enabled.
#### weather.location
This field is a string. It is given to OpenStreetMap Nominatim to retrieve coordinates to feed into the Norwegian Meteorological Institute's API. Anything that can be found on OpenStreetMap should also work here. It will always use the first result.

View File

@ -31,6 +31,10 @@ Music control is implemented using `playerctl` which uses the MPRIS DBus interfa
ITD exposes a UNIX socket at `/tmp/itd/socket` by default. This socket can be used to control the daemon. It is how `itctl` and `itgui` work. This can be used in any language which supports UNIX sockets which is nearly all of them. Even bash can be used with `netcat`.
### Weather
ITD uses data from OpenStreetMap Nominatim to get coordinates for a location, and then feeds those to the Norwegian Meteorological Institute's API to retrieve weather for that location.
### New Features
New features are added whenever I find out they exist from InfiniTime's repo or developers. This means ITD's master branch may contain features not yet released in InfiniTime.

View File

@ -8,7 +8,14 @@ This is a note for anyone using or planning to contribute to ITD. I am {{<raw>}}
{{<raw>}}
<script>
birthday = new Date("April 24, 2005")
document.getElementById("age").innerHTML = (new Date).getFullYear() - birthday.getFullYear()
birthday = new Date("April 24, 2005");
now =new Date();
age = now.getFullYear() - birthday.getFullYear();
if (now.getMonth() < birthday.getMonth()) {
age--;
} else if (now.getMonth() == birthday.getMonth() && now.getDate() < birthday.getDate()) {
age--;
}
document.getElementById("age").innerHTML = age;
</script>
{{</raw>}}

View File

@ -6,4 +6,4 @@ weight = 1
ITD was created because I could not find a good InfiniTime companion for Linux. There is [Siglo](https://github.com/alexr4535/siglo) which cannot do much beyond syncing time and updating the watch and is not very reliable. There is [Amazfish](https://github.com/piggz/harbour-amazfish) which works, but at least for me, is a bit clunky and unreliable.
I wanted something that was easy enough to use that I could just run it and forget about it, and had any feature I may want to use. Also, I needed it to work on Linux because I only own Linux devices, including my phone, which is a PinePhone. This leads to the next requirement. I needed it to be easily cross-compiled so that I could use it on all my computers as well as aarch64 devices such as my PinePhone and Raspberry Pi 4s. All of these reasons contributed to me deciding to make ITD and they are what I try to emphasize.
I wanted something that was easy enough to use that I could just run and forget about, and had any feature I may want to use. Also, I needed it to work on Linux because I only own Linux devices, including my phone, which is a PinePhone. This leads to the next requirement. I needed it to be easily cross-compiled so that I could use it on all my computers as well as aarch64 devices such as my PinePhone and SBCs. All of these reasons contributed to me deciding to make ITD and they are what I try to emphasize in my development.