| Age | Commit message (Collapse) | Author |
|
|
|
This is already the minimal viable product (MVP) for this app.
|
|
|
|
This map should be empty in the future and updated based on the incoming
MQTT messages.
A list was not the correct data structure for that since it requires to
iterate over the whole list to find the entry with a certain address.
But this is required to update the state of an already known contact.
|
|
|
|
This is now done with the refactored code organization and a strict UI /
data split.
|
|
The UI should not store the application logic state.
|
|
This follows recommendations [1] from the flutter documentation.
[1]: https://docs.flutter.dev/app-architecture/concepts
|
|
|
|
This demonstrates that the state of the contacts in the UI can be
changed at runtime.
|
|
This is required to change the contact states during runtime.
|
|
This is one script which checks the code quality of Python and Dart
sources.
It can be symlinked as `.git/hooks/pre-commit` to guard commits of
questionable quality.
|
|
This should help writing good flutter / Dart code from the beginning.
|
|
This makes the code more readable.
|
|
The old name MainPage did not explain a lot.
|
|
This library is the currently most often downloaded MQTT library on
pub.dev. This is at least a good starting point.
|
|
This demonstrates how the UI should look like. The data is just for
visualization and never changes. Functionality is added later.
|
|
Displaying the more technical name `sia_app` in the title bar is not
suitable.
|
|
|
|
This makes it easy to re-generate the files provided initially with
`flutter create`.
|
|
|
|
This was done using the following command.
flutter create \
--description "Sia app" \
--org "eu.xengineering" \
--project-name "sia_app" \
--platforms linux,android \
--empty \
.
|
|
|