| Age | Commit message (Collapse) | Author |
|
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 makes the code more readable.
|
|
The old name MainPage did not explain a lot.
|
|
This demonstrates how the UI should look like. The data is just for
visualization and never changes. Functionality is added later.
|
|
This was done using the following command.
flutter create \
--description "Sia app" \
--org "eu.xengineering" \
--project-name "sia_app" \
--platforms linux,android \
--empty \
.
|