home

============

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?

Legend

------

The dependencies themselves have been ranked with a certain grade. I explain what they mean here:

 * 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.

 * 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.

 * 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.

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.)

A

-

 * [jQuery](https://jquery.com/): Necessary for Materialize to work properly.

 * [Materialize](http://materializecss.com/): The layout framework for the web app. (Material Design is the best)

B

-

C

-

from .models import *

# Down here, all models are registered, making them suitable for administration (In essence; making them pop up in the admin interface).

admin.site.register(Card)

admin.site.register(Principle)

admin.site.register(Program)

admin.site.register(Stack)

admin.site.register(Quote)

admin.site.register(Hack)

admin.site.register(AboutMe)

admin.site.register(SecurityMeasure)

admin.site.register(Goal)

class WinkellijstConfig(AppConfig):

    name = 'about'

# Cards: Describes a card that will be loaded in the main page, providing links to useful information and other apps.

class Card(models.Model):

    title = models.CharField(max_length=20) # 20 should sustain well.

    description = models.CharField(max_length=256) # 256 as well.

    link1 = models.CharField('First link', blank=True, max_length=50) # I could make this a URLField, but that doesn't accept cases like "/ITdays".

    linkName1 = models.CharField('Name of first link', blank=True, max_length=20)

    link2 = models.CharField('Second link', blank=True, max_length=50) # This may be empty.

    linkName2 = models.CharField('Name of second link', blank=True, max_length=20) # This too.

    image = models.ImageField(upload_to='about/images/cards', blank=True) # Sometimes the cards should get an image.

    def __str__(self):

        return self.title

# What you're about to see, is a very rare case of where multi-level inheritance

# is actually done correctly. Notes should be taken. (Also worth mentioning

# Django is so well built it actually makes this possible.)

# First, it should be said all objects have an extremely similar structure. That

# doesn't qualify them yet for multilevel inheritance, but it's a good sign.

# Also, note how Card, even though it has both title and description, is NOT

# inherited from this base class. This is deliberate; Card is not an object with

# a comparable behavior, and thus, differs too much as an object to derive from

# this one.

class Subject(models.Model):

    """ This class should not be instantiated. Look at it as being an abstract

    class. """

    title = models.CharField(max_length=50)

    description = models.TextField()

    def __str__(self):

        return self.title

    """ This Meta is important, because it tells Django that Subject is

    'abstract', in that it just has some fields that should be passed to its

    children. """

    class Meta:

        abstract = True

# Now you may say: Well, some subjects have links, why not make another object,

# and use it for just that? Well, because that would imply multiple inheritance,

# which is not necessary here*, and (if that second object would inherit Model

# again) cause a diamond inheritance.

# *Most of the time people use inheritance because it's convenient. While that

# may be a reason, it shouldn't be the only reason for it. Inheritance is not

# made to make programming convenient, that's what programming languages are

# for. Inheritance is to inherit behavior from another object. And since that's

# my goal here, inheritance is a passable programming decision.

# Also, I'm referring here to OOP inheritance, which means "inheriting state AND

# behavior". Languages that implement other paradigms can also have inheritance.

# Clojure, for example, is not OOP, but fully functional, and its inheritance

# capabilities are WAY better.

class Principle(Subject):

    pass

class AboutMe(Subject):

    pass

class Program(Subject):

    link = models.URLField()

class Stack(Subject):

    link = models.URLField()

class Hack(Subject):

    pass

class SecurityMeasure(Subject):

    pass

class Goal(Subject):

    pass

# A last pick on inheritance (I feel so obliged to defend my decision because I

# decided to use inheritance, apologies if you're sick of taking notes):

# Note that I could've easily solved this problem without inheritance. Some

# objects even lack any other variable or function of some sort.

# But also, note how easy it now becomes to edit all those objects at once: If I

# want to increase the length (And yes, that length should be the same, I like

# that), I can now do that all at once. THIS is when inheritance can be a good

# thing: To increase code maintainability for a lot of different objects.

class Quote(models.Model):

    text = models.TextField()

    author = models.CharField(max_length=256)

    link = models.URLField(blank=True)

# Really, these max_lengths... Sometimes I look at my code and just think what an arbitrary asshole I can be to my database.

# Create your tests here.

from . import views # Imports the views from the same directory (which is views.py).

urlpatterns = [

        url(r'^$', views.index, name='about-index'),

        url(r'^myself$', views.myself, name='main-myself'),

        url(r'^principles$', views.principles, name='about-principles'),

        url(r'^hacking$', views.hacking, name='about-hacking'),

        url(r'^me$', views.me, name='about-me'),

        url(r'^webstack$', views.webstack, name='about-webstack'),

        url(r'^software$', views.software, name='about-software'),

        url(r'^security$', views.security, name='about-security'),

        url(r'^roadmap$', views.roadmap, name='about-roadmap'),

        ]

from datetime import date

from django.shortcuts import get_object_or_404, render # This allows to render the template with the view here. It's pretty cool and important.

from django.http import HttpResponseRedirect, HttpResponse # Why?

from django.core.urlresolvers import reverse # Why?

from django.utils.translation import ugettext as _

from .models import *

# First, I list some standard variables that are common for most of the sites of this app.

def get_age():

    """Returns my current age."""

    today = date.today()

    birthday = date(1996, 8, 28)

    age = today - birthday

    years = str(int(age.days / 365))

    return years

def footer_description():

    years = get_age()

    """

    Grandpa easter egg: The Dutch version of the most ingenius algorithm I ever wrote:

    vandaag = datum.vandaag()

    geboortedatum = datum(28-08-1996)

    leeftijd = vandaag - geboortedatum

    jaren = leeftijd.jaren()

    This will help me explain what programming has brought me. =3

    """

    return "Main pages of Maarten's website, a " + years + " year old Belgian programmer. Also an undergraduate informatics student @ UHasselt."

def footer_links():

    footer_links = [

            ["Contact", "mailto:maarten.vangeneugden@student.uhasselt.be"],

            ["UHasselt", "https://www.uhasselt.be"],

            ]

    return footer_links

# TODO: Move this stuff to the template module. This is basically a description

# of HOW to display data, but the view module is only responsible for WHAT data

# to display.

def standard_context():

    context = {

            'materialDesign_color': "blue",

            'materialDesign_accentColor': "orange",

            'navbar_backArrow': True,

            'footer_title': "Home pages",

            'footer_description': footer_description(),

            'footer_links': footer_links(),

            }

    return context

def get_current_status():

    """Returns a string specifying my current state.

    This function is actually based on my weekly schedule. I'd normally hook it

    up to my iCal files, but that doesn't include things like sleeping. I

    figured a simple function would do the job just as well.

    """

    import datetime

    current_date = datetime.datetime.now()

    current_time = current_date.time()

    status = _("Current status/location: ")

    if current_time.hour <= 8:  # 00:00 - 08:00

        status = status + _("I'm asleep. See you tomorrow! =D")

    elif current_time.hour > 8 and current_time.hour <= 17: # 09:00 - 17:00

        if current_date.weekday() >= 5:  # Saturday (5) or Sunday (6)

            if current_time.hour == 13:

                status = status + _("Watching the news, or eating something delicious...")

            else:

                status = status + _("Studying from home, so not really available now. Maybe in a couple of hours...")

        else:  # Midweek

            if current_time.hour < 11:

                status = status + _("Attending classes. See you later!")

            elif current_time.hour == 11 or current_time.hour == 12:

                status = status + _("Lunch @ UHasselt. I'm available if you need me! <3")

            else:

                status = status + _("Studying at university! Send me a mail, or visit me in C23!")

    else:

        status = status + _("At home, relaxing a bit. Feel free to talk! =D")

    return status

# Views:

def index(request):

    status = get_current_status()

    template = "about/index.html"

    cards = Card.objects.order_by('?') # The '?' indicates the objects must be ordered randomly.

    quotes = Quote.objects.all()

    randomQuote = random.choice(quotes)

    largeSizes = []

    mediumSizes = []

    for i in range(0, len(cards)):

        newLargeSizes = [6, 4, 2]

        newMediumSizes = [8, 4]

        random.shuffle(newLargeSizes)

        random.shuffle(newMediumSizes)

        largeSizes.extend(newLargeSizes)

        mediumSizes.extend(newMediumSizes)

    contextList = []

    i = 0

    for card in cards:

        contextList.append([card, mediumSizes[i], largeSizes[i]])

        i += 1

    # TODO: Move this stuff to the template module. This is basically a description

    # of HOW to display data, but the view module is only responsible for WHAT data

    # to display.

    context = {

            'status': status,

            'materialDesign_color': "blue",

            'materialDesign_accentColor': "orange",

            'navbar_title': "Maarten's website",

            'navbar_fixed': False,

            'parallax_src': "/media/about/images/parallax.png",

            'footer_title': "Home pages",

            'footer_description': footer_description,

            'footer_links': footer_links,

            'cards': contextList,

            'quote': randomQuote,

            }

    return render(request, template, context)

def myself(request):

    template = "about/about.html"

    context = {

            'subject': "Myself",

            'navbar_title': "Myself",

            'age': get_age(),

            }

    context.update(standard_context())

    return render(request, template, context)

def principles(request):

    template = "about/principles.html"

    data = Principle.objects.order_by('title')

    context = {

            'subject': "principles",

            'navbar_title': "Principles",

            'data': data,

            }

    context.update(standard_context())

    return render(request, template, context)

def hacking(request):

    template = "about/hacking.html"

    data = Hack.objects.order_by('title')

    context = {

            'subject': "hacking",

            'navbar_title': "Hacking",

            'data': data,

            }

    context.update(standard_context())

    return render(request, template, context)

def me(request):

    template = "about/me.html"

    data = AboutMe.objects.order_by('title')

    context = {

            'subject': "me",

            'navbar_title': "Me",

            'data': data,

            }

    context.update(standard_context())

    return render(request, template, context)

def webstack(request):

    template = "about/webstack.html"

    data = Stack.objects.order_by('title')

    context = {

            'subject': "web stack",

            'navbar_title': "Web stack",

            'data': data,

            }

    context.update(standard_context())

    return render(request, template, context)

def software(request):

    template = "about/software.html"

    data = Program.objects.order_by('title')

    context = {

            'subject': "software",

            'navbar_title': "Software",

            'data': data,

            }

    context.update(standard_context())

    return render(request, template, context)

    # WARNING:

    # Because I haven't been able to figure out yet how to add colors to hyperlinks, I put them hardcoded in the database. IF YOU FIND A WAY TO DO IT RIGHT, DO SO ASAP!

def security(request):

    template = "about/security.html"

    data = SecurityMeasure.objects.order_by('title')

    context = {

            'subject': "security",

            'navbar_title': "Security",

            'data': data,

            }

    context.update(standard_context())

    return render(request, template, context)

def roadmap(request):

    template = "about/roadmap.html"

    data = Goal.objects.order_by('title')

    context = {

            'subject': "roadmap",

            'navbar_title': "Roadmap",

            'data': data,

            }

    context.update(standard_context())

    return render(request, template, context)