DEPENDENCIES.md

1
Dependencies
2
============
3
4
Since web apps (and everything web related) are known to suck at dependency handling (which is why we have Bower, NPM, cdnjs, docker, ... (I'll explain sometime somewhere why this is done, and why it's useless)), I've decided to take matters in my own hands; I'll just provide one simple markdown file listing all dependencies in human-readable format. I don't care whether this helps or not, but no harm is done, right?
5
6
Legend
7
------
8
9
The dependencies themselves have been ranked with a certain grade. I explain what they mean here:
10
11
 * A : This dependency is present inside the app. This will be in the form of ready-to-use source code files. As such, they need no further attention.
12
 * B : This dependency is present inside the app, or very easy to retrieve yourself. This will be in the form of an archive file (i.e. .tar.gz), OR this needs additional work to function properly. In these cases, I refer to their documentation which will be available at the location of the files.
13
 * C : This dependency does not come with the app, and requires manual effort to set up. These are often system packages, which often means (if you're on GNU/Linux) to search for it in your repositories. Their documentation is your last resort for these if it doesn't work as it should.
14
 
15
I hope I never will, but when it's necessary, I'll add a D grade, for unreadable, egregious bogus software that will give you all horrible kinds of diseases if you dare to work with it, but are indispensable to make the web app function. Just be happy I don't use it yet. (For example, PHP qualifies as D, so praise [our lord and saviour](https://rms.sexy) I write Python.)
16
17
A
18
-
19
 * [jQuery](https://jquery.com/): Necessary for Materialize to work properly.
20
 * [Materialize](http://materializecss.com/): The layout framework for the web app. (Material Design is the best)
21
22
23
B
24
-
25
* pytz: Handles timezone differences.
26
27
C
28
-
29