3

I have a table that contains "username" and "grades". The grades are in format of A+, A, A-, B+ and so on. I am trying to display a total grade for each user with numeric values. For example:

John A+

Jerry B+

John C-

Tom A-

Jerry B+

So if A+ = 10 and everything else following as A =9 and A- =8 and so on, how do I calculate the total grade John earned. I am trying to do this in a DJANGO template (.html) file and can't seem to implement a counter at all

summerNight
  • 1,446
  • 3
  • 25
  • 52

2 Answers2

4

You could write your own template filter for this. Create a new python file called 'grade_filters.py' in a folder called 'templatetags' in your template folder and declare a new templatetag as follows:

from django import template

register = template.Library()

def grade_to_number(grade):
    map_dict = {'A+': 10, 'A':9, 'A-':8}
    if grade in map_dict:
        return map_dict[grade]
    else:
        return 0


@register.filter(name='sum_of_grades')
def return_item(grade_list):

    new_grades_list = [grade_to_number(grade) for grade in grade_list]
    try:
        return sum(new_grades_list)
    except:
        return 0

@register.filter(name='get_list_for_student')
def return_item(student_list, name):

    return student_list.filter(name=name)

Now, in your template you can load the new templatetag with

{% load grade_filters %}

Calculate the grade total of one student with:

{{ gradelist|get_list_for_student:'John'|sum_of_grades }}
klasske
  • 2,164
  • 1
  • 24
  • 31
2

It's by design that you can't do that in the templates. The django philosophy is such that logic of that sort belongs in the views.

We see a template system as a tool that controls presentation and presentation-related logic – and that’s it. The template system shouldn’t support functionality that goes beyond this basic goal.

source: https://docs.djangoproject.com/en/dev/misc/design-philosophies/#separate-logic-from-presentation

Though they do allow you to break the tools and write custom tags and filters like alexcxe said, it's undoubtedly easier to just to include this sort of logic in your views and pass it as a context variable. I don't know what your models look like, but a dict or a tuple would be fitting in this situation. I've had to do both in similar situations. If you provide more details, I can give you a specific implementation.

Every now and then it's ok to break the rules, but im gathering that you're new to django, so at this point, until you know when it's ok, i'd suggest following the rules set by the django community, especially if your goal is to work with other django developers.

skzryzg
  • 1,020
  • 8
  • 25
  • Trying to give an answer--regardless of how wrong or right it is--to the wrong question isn't going to help anyone. – skzryzg Sep 01 '14 at 19:26
  • Well I think the information you were trying to offer is useful and important to know as long as it's accompanied by a disclaimer underlying when it should be used. I dont think you should've deleted it. It's definitely valid and relevant – skzryzg Sep 01 '14 at 19:37
  • 1
    Well what I was trying to get at was that you should've just edited your answer rather than deleting the whole thing because i thought both of our answers together provided a better perspective than just one alone. Software development is a new field. Web development, even more so. No one does it right and no one has everything figured out, so i think it's good for new comers to see this incongruence first hand – skzryzg Sep 01 '14 at 19:50
  • +1 for pointing out the philosophy, I don't think this is a bad response. – keni Sep 01 '14 at 23:11