Open mykeels opened 5 years ago
@mykeels you are right. A design document is necessary. Should I write the document in Wiki or Issue? Which one will be convenient for all?
Thanks for your enthusiasm.
A Wiki is fine. That's where we go to, when we can't find what we're looking for in the README.md
I also want some parts to be modular so that we can support different schools' situation e.g.: Different grading and marking system.
What do you think?
Cool!
Right now, I'm thinking those can be functional, a clearly defined function that can be overridden by adopters to provide custom functionality.
But I don't know your idea for the grading system yet, so this might not fit in. If you explained, I might be able to help. How does the grading system work currently?
@mykeels I'm sorry for not being able to do the works because unfortunately my windows partition that I've been working in, have become unfixable.
I will try to provide info using my phone.
I've added some pages in wiki. You may give your feedback on these. It will help me to improve further documentation.
The layout looks okay.
@mykeels Exam document page added. I'm trying to continue documentation with software improvement. So it is getting bit slow :/
Thanks for your feedback.
Is there a feature where you can attach a fingerprint scanner to record the teacher's attendance?
I'd like to contribute when I can, but it's hard knowing your intentions for parts of the application that haven't been completed yet.
Could you provide a document that gives the design of the application? A good and simple format to begin with is:
Class
This is a description of a school's class. It does this and that ... Its properties are:
Section
A class can have multiple sections. It represents the divisions within a single class ... It's properties are: