Mostly just code style, formatting and minor pedantic stuff but it's nice to cleanup.

It'll be a great improvement to setup GitHub Actions or something similar to run commands such as flutter analyze and flutter test in every repo on PRs and pushes.

this would be a nice addition to pangolin. if we were able to even traverse a basic Linux filesystem and run basic bash scripts it would already be a suitable os. that coupled with the hopeful success of sapphire for raspi 3 would make a nice os

Related to #6.

As I've closed this PR to make it easier for others to contribute, I'll be opening this issue to keep track of core features, outside of Discussions. All new issues with this branch should go into their own separate issue.

Pull request template

• Please make sure you read and fill this template out entirely
• PRs that don't have the template filled out will be ignored

Description

• Please include a summary of the change and which issue is fixed
• Please also include relevant motivation and context (Why is this change required? What problem does it solve?)
• List any dependencies that are required for this change
• If it fixes an open issue, plase link to the issue here

Fixes #(issue)

Screenshots (if appropriate):

Type of change

Please tick the relevant option by putting an X inside the bracket

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

Checklist:

• [ ] My code follows the guidelines of this project
• [ ] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] My changes generate no new warnings
• [ ] All current GitHub actions pass
• [ ] Any dependent changes have been merged and published in downstream modules
• [ ] I have checked my code and corrected any misspellings
• [ ] I have read the CONTRIBUTING document

Description

• Added tab closing when process exists
• Added app closing when no more tabs open

Type of change

Please tick the relevant option by putting an X inside the bracket

• [x] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)

(Bit of both I guess)

Checklist:

• [x] My code follows the guidelines of this project
• [x] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas; tf none of your code is commented. Easy to read anyways.
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] All current GitHub actions pass
• [x] Any dependent changes have been merged and published in downstream modules
• [x] I have checked my code and corrected any misspellings
• [x] I have read the CONTRIBUTING document