improved readme #15

[Amanjakhetiya]

added documentation for the modules used for more understandibility and added about tkinter module which was missed.

[Vibhu-Agarwal]

Thanks for the PR @Amanjakhetiya

Currently, the dependencies are mentioned in the README, but in a python project, they're usually mentioned in a requirements.txt file.

We even have an issue (#16) raised for it. In fact, it's already being worked on. (#20)

Unfortunately, I'll have to close this one on account of the following reasons:

• The mode of installation will be changed from copy-pasting individual library installation commands to installing from a requirements file. This will replace libraries mention from README, so module links (of documentation) with library commands will eventually be removed.
• @akshgpt7 volunteered to work on the issue (See thread in #16) and got the nod from a maintainer, thus getting assigned to the issue. That means until he himself gives up on the issue or there has been no progress on the issue for a while (~2 weeks), no-one else should work on it. The only you can work on this issue is by asking @akshgpt7 if he's still working on the issue or not.

A few other learnings to take from this:

• Don't use issue/PR references in PR titles (as in this one). You can reference the issue in the PR description though. See how to use kewords. Neither should you use them in your commit titles as you've used in this commit.
• Match one PR with one issue. Don't try to tackle multiple issues in one PR as you did in this one (Issues #15 and #16)
• Make different branches on your fork to target a specific issue or feature development. You made the PR from your master branch. But you won't be able to work on a different issue locally because you didn't make a different branch in the first place. A MUST read for you.

What can you do now?

• If you think we missed to mention a library that needs installation, that's a bug. You can raise an issue for it. A separate PR can be made in order to fix that. But before you start working on an issue, make sure you get a nod from one of the maintainers.
• If you want users to pay attention to docs, you can add a separate section in README for it. You can even explain a bit about the library used, in-line.
• If you think that the whole process should've been documented. You can work on this issue (#9)