Module Contents



Based on:


Base class for all field types

class oioioi.base.utils.color.ColorWidget(attrs=None)[source]

Bases: django.forms.TextInput

Based on: http://laktek.com/2008/10/27/really-simple-color-picker-in-jquery/ Requires jQuery > 1.2.6

Displays a fixed set of preselected color options. Hex value can also be edited manually. Only supports Hex values. Alpha channel not supported.

class Media[source]

Bases: object

js = ['js/jquery.colorPicker.js'][source]
render(name, value, attrs=None, renderer=None)[source]

Render the widget as an HTML string.

class oioioi.base.utils.color.ColorField(*args, **kwargs)[source]

Bases: django.db.models.CharField

Base class for all field types


Return a django.forms.Field instance for this field.


Return enough information to recreate the field as a 4-tuple:

  • The name of the field on the model, if contribute_to_class() has been run.

  • The import path of the field, including the class, e.g. django.db.models.IntegerField. This should be the most portable version, so less specific may be better.

  • A list of positional arguments.

  • A dict of keyword arguments.

Note that the positional or keyword arguments must contain values of the following types (including inner values of collection types):

  • None, bool, str, int, float, complex, set, frozenset, list, tuple, dict

  • UUID

  • datetime.datetime (naive), datetime.date

  • top-level classes, top-level functions - will be referenced by their full import path

  • Storage instances - these have their own deconstruct() method

This is because the values here must be serialized into a text format (possibly new Python code, possibly JSON) and these are the only types with encoding handlers defined.

There’s no need to return the exact way the field was instantiated this time, just ensure that the resulting field is the same - prefer keyword arguments over positional ones, and omit parameters with their default values.