Getting Started

The workflow for using django-selectable involves two main parts:
  • Defining your lookups
  • Defining your forms

This guide assumes that you have a basic knowledge of creating Django models and forms. If not you should first read through the documentation on defining models and using forms.

Including jQuery & jQuery UI

The jQuery and jQuery UI libraries are not included in the distribution but must be included in your templates. See the example project for an example using these libraries from the Google CDN. Django-Selectable should work with jQuery >= 1.4.3 and jQuery UI >= 1.8

{% block extra-css %}{% endblock %}
<script type="text/javascript" src=""></script>
<script type="text/javascript" src=""></script>

You must also include a jQuery UI theme stylesheet. In the example project we’ve included the “lightness” theme via the Google CDN.

<link rel="stylesheet" href="" type="text/css" media="screen">

Defining a Lookup

The lookup classes define the backend views. The most common case is defining a lookup which searchs models based on a particular field. Let’s define a simple model:

class Fruit(models.Model):
    name = models.CharField(max_length=200)

    def __unicode__(self):

In a we will define our lookup:

class FruitLookup(ModelLookup):
    model = Fruit
    search_field = 'name__icontains'

This lookups extends selectable.base.ModelLookup and defines two things: one is the model on which we will be searching and the other is the field which we are searching. This syntax should look familiar as it is the same as the field lookup syntax for making queries in Django.

Below this definition we will register our lookup class.


Defining Forms

Now that we have a working lookup we will define a form which uses it:

class FruitForm(forms.Form):
    autocomplete = forms.CharField(
        label='Type the name of a fruit (AutoCompleteWidget)',

This replaces the default widget for the CharField with the AutoCompleteWidget. This will allow the user to fill this field with values taken from the names of existing Fruit models.

And that’s pretty much it. Keep on reading if you want to learn about the other types of fields and widgets that are available as well as defining more complicated lookups.

Project Versions

Table Of Contents

Previous topic


Next topic

Defining Lookups

This Page