Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

simple skin with routing on components #175

Merged
merged 4 commits into from
Apr 11, 2021
Merged

simple skin with routing on components #175

merged 4 commits into from
Apr 11, 2021

Conversation

vaslabs
Copy link
Owner

@vaslabs vaslabs commented Apr 11, 2021

Very simple main view, with mob friendly side panel and routing outlet in the main screen to navigate components

  • Libary updates

@vaslabs vaslabs requested a review from agalazis April 11, 2021 10:52
@vaslabs vaslabs merged commit 98c27d6 into remaster Apr 11, 2021
@vaslabs vaslabs deleted the ui/skin branch April 11, 2021 20:50
vaslabs added a commit that referenced this pull request May 3, 2021
* Restructure

* More scaffolding and config format changes

* Initialise angula app

* Build recipe for development

* Clean

* Workflow for remaster

* Fix syntax

* Fix syntax

* Update readme

* Add badge

* Update README.md

* No apache in remaster

* simple run

* Run with input fix

* [158]feat(dev-environment): configured angular proxy / added instruct… (#159)

* [158]feat(dev-environment): configured angular proxy / added instructions in readme

* [158]chore(readme): update readme

* Fixed some typos, used correct port

* Remove vscode

* Working unit test for os release info

* Add test for backend to CI

* Add os info handler

* Enrich system info response with temperature

* Add kernel info to the api

* Api cosmetics

* Trim new line suffix

* Landing page scaffolding

* periodic poll update

* Feature/websocket comms (#163)

This PR provides the scaffolding for single connection communication between the UI and the backend (sitting on the raspberry pi)

Leaving the logs for now but we should remove some chatty ones before final release (which is gonna take a while)

Inception
The FE and BE commincation will be in a biderectional Command => Event driven approach.
The FE implementation splits the websocket (on inteface level) into a source (for reading the events) and a sink (for sending the commands) .
A sink is essentially a consumer and a source a producer. In this case the interface is exposing the Source for consumers (component views) to process events and the sink for sending commands (i.e. with a service call interfacing a component) (thus replacing http calls )

* pre commit

* Switch to pre-commit

* Fix linting

* Instructions for pre commit

* unused method

* Feature/dev environment setup (#171)

* fiear(dev-environment): add install-dev section in makefile update go.sum

* feat(install-dev): add git to dev dependencies

* Feature/poweroff component (#172)

## Feature
- Simple component that provides a poweroff and reboot interface
- Simple backend implementation - no scheduling
- Connecting the component calls to the websocket e2e
## Fixes
- Try to reconnect if websocket closes

Resolves #172

* feat(websockets): add rfc ping pong, incremental backoff, handle subscriptions in liveinfo (#173)

* feat(websockets): add rfc ping pong, incremental backoff, handle subscriptions in liveinfo

* chore(linting): remove unneeded printf

* chore(configration): update interval

* Reboot and shutdown by issuing syscalls instead of calling shell commands (#174)

Currently the poweroff function inherits the priviledges of the gui since we are running this from the e.g. gnome-terminal and poweroff and reboot work without needing root priviledges as they inherit the gui ones (I think). However when it runs as a service this will not apply.

Go has also a linux syscall API that we can use instead of issuing shell commands which will dramatically decrease response times (although not a big deal for power management, having this paradigm in would be beneficial for later)

* simple skin with routing on components (#175)

Very simple main view, with mob friendly side panel and routing outlet in the main screen to navigate components

Libary updates

* Feature/166 online indicator (#176)

* feat(websockets): add rfc ping pong, incremental backoff, handle subscriptions in liveinfo

* chore(linting): remove unneeded printf

* chore(configration): update interval

* feat(OnineIndicator): added online indicator module/ updated websocket service to report connectivity

* chore(linting): update precommit hook

* - Servified pi-web-agent (#177)

* - Servified pi-web-agent (currently tested on fedora)
- Created convenient make commands for installation/uninstallation - only for dev usage but anyone can use
- Fixed an issue with the routing that was refreshing the page
- Fixed an issue with golang routing to be able to serve all assets

* Feature/package deb (#181)

- Major cleanup of unused files
- Auto releases debian packages on a new tag

* Update README.md

* Update README.md

* Feature/new logo (#186)

* favicon + logo

* Update README.md

* Attempt to fix installation scripts for updates

* Scaffolding for configuration + preparation for setting passphrase (#192)

* Scaffolding for configuration + preparation for setting passphrase

* Setup config on dev & user installation

* dev installation/uninstallation fixes

* Feature/165 certificate setup (#194)

Https with certificate setup on install

* Feature/background update check (#196)

- cron daily for update checks
- Update + output terminal to show progress

* Fix syntax

Co-authored-by: Andreas Galazis <agalazis@users.noreply.github.com>
Co-authored-by: NANOUU <59022292+antoniasymeonidou@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants