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

Decouple the module ConfigParser from several classes #2

Open
GuillemCastro opened this issue Feb 23, 2017 · 2 comments
Open

Decouple the module ConfigParser from several classes #2

GuillemCastro opened this issue Feb 23, 2017 · 2 comments

Comments

@GuillemCastro
Copy link
Member

There are several classes unnecessarily coupled with the module ConfigParser. We should decouple it by creating a class that will use it (an adapter) that should be instantiated only once (in app.py), though multiple instances should be permitted through the app, and then pass it to the rest of the classes (to reduce further more the coupling, we should only pass the parameters the classes need).

@kafkasl
Copy link

kafkasl commented Jul 6, 2017

I would like to help with this issue, however I do not know how you test the code nor which kind of adaptor you have in mind.

@GuillemCastro
Copy link
Member Author

We won't be using this software anymore, and we don't plan on supporting it. Raspberry Pi is not suitable for real-time operations (this software was design to run in a Raspberry Pi Zero). The software for the new on-board computer is being developped at Intruder Cotrol.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants