Open nherman71 opened 8 months ago
What is our design for the interface between the frontend and backend of this project? I like Frontend.py
being the entrypoint, and love @Chrisvann1 UX so far. But I'm concerned with where the functionality will live.
I had thought we wanted the frontend to call the methods that will live in Backend.py
and get returned strings to print. I liked that design because it let us change the functionality on the backend in the future, and would let us customize the frontend look separate from that. It would basically separate concerns of style and formatting of input from the logic of finding files for example.
Is there a better way of doing this that I can't see? I would love everyone's thoughts on how we should structure this.
@tferrelCOW @Chrisvann1 If you are having problems with the backend can you open an issue for the backend and assign Nicco or me as an assignee? That way we can understand what the expected behavior is and what bug you are having, and we can fix backend for you. Here is a way to write issues I ripped from a GitHub template
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.
Earn rewards and secure your financial future by staking your ETH with Binance. By participating in the Binance staking program, you can potentially double your ETH while supporting the blockchain network.
Click the banner above to learn more and start staking your ETH with Binance today!
This is a place to discuss anything related to the early development of ideas and similar, if you have psuedocode or notes to share this is a good place.
ex:
Planned directory structure
Noteworthy/ code.py code2.py configs.txt etc.otherfiletype Notes mathnotes1.md mathnotes2.md whatWeNeedToDo.md