Add manual sort order to Django objects via an abstract base class and admin classes.
Project description
# Django Orderable
Add manual sort order to Django objects via an abstract base class and admin classes. Project includes:
* Abstract base Model
* Admin class
* Inline admin class
* Admin templates
## Demo
![django-orderable demo](https://cloud.githubusercontent.com/assets/30606/6326221/667992e0-bb47-11e4-923e-29334573ff5c.gif)
## Installation
Grab from the PyPI:
pip install django-orderable
Add to your INSTALLED_APPS:
...
'orderable',
...
Subclass the Orderable class:
from orderable.models import Orderable
class Book(Orderable):
...
Subclass the appropriate Orderable admin classes:
from orderable.admin import OrderableAdmin, OrderableTabularInline
class SomeInlineClass(OrderableTabularInline):
...
class SomeAdminClass(OrderableAdmin):
list_display = ('__unicode__', 'sort_order_display')
...
jQuery and jQuery UI are used in the Admin for the draggable UI. You may override the versions with your own (rather than using Google's CDN):
class SomeAdminClass(OrderableAdmin):
class Media:
extend = False
js = (
'path/to/jquery.js',
'path/to/jquery.ui.js',
)
## Notes
### `class Meta`
If your subclass of `Orderable` defines [`class Meta`](https://docs.djangoproject.com/en/2.0/ref/models/options/) then make sure it subclasses `Orderable.Meta` one so the model is sorted by `sort_order`. ie:
class MyOrderable(Orderable):
class Meta(Orderable.Meta):
...
### Custom Managers
Similarly, if your model has a custom manager, subclass `orderable.managers.OrderableManager` instead of `django.db.models.Manager`.
### Transactions
Saving orderable models invokes a fair number of database queries, and in order
to avoid race conditions should be run in a transaction.
### Adding Orderable to Existing Models
You will need to populate the required `sort_order` field. Typically this is
done by adding the field in one migration with a default of `0`, then creating
a data migration to set the value to that of its primary key:
for obj in orm['appname.Model'].objects.all():
obj.sort_order = obj.pk
obj.save()
### Multiple Models using Orderable
When multiple models inherit from Orderable the `next()` and `previous()`
methods will look for the next/previous model with a sort order. However you'll
likely want to have the various sort orders determined by a foreign key or some
other predicate. The easiest way (currently) is to override the method in
question.
Add manual sort order to Django objects via an abstract base class and admin classes. Project includes:
* Abstract base Model
* Admin class
* Inline admin class
* Admin templates
## Demo
![django-orderable demo](https://cloud.githubusercontent.com/assets/30606/6326221/667992e0-bb47-11e4-923e-29334573ff5c.gif)
## Installation
Grab from the PyPI:
pip install django-orderable
Add to your INSTALLED_APPS:
...
'orderable',
...
Subclass the Orderable class:
from orderable.models import Orderable
class Book(Orderable):
...
Subclass the appropriate Orderable admin classes:
from orderable.admin import OrderableAdmin, OrderableTabularInline
class SomeInlineClass(OrderableTabularInline):
...
class SomeAdminClass(OrderableAdmin):
list_display = ('__unicode__', 'sort_order_display')
...
jQuery and jQuery UI are used in the Admin for the draggable UI. You may override the versions with your own (rather than using Google's CDN):
class SomeAdminClass(OrderableAdmin):
class Media:
extend = False
js = (
'path/to/jquery.js',
'path/to/jquery.ui.js',
)
## Notes
### `class Meta`
If your subclass of `Orderable` defines [`class Meta`](https://docs.djangoproject.com/en/2.0/ref/models/options/) then make sure it subclasses `Orderable.Meta` one so the model is sorted by `sort_order`. ie:
class MyOrderable(Orderable):
class Meta(Orderable.Meta):
...
### Custom Managers
Similarly, if your model has a custom manager, subclass `orderable.managers.OrderableManager` instead of `django.db.models.Manager`.
### Transactions
Saving orderable models invokes a fair number of database queries, and in order
to avoid race conditions should be run in a transaction.
### Adding Orderable to Existing Models
You will need to populate the required `sort_order` field. Typically this is
done by adding the field in one migration with a default of `0`, then creating
a data migration to set the value to that of its primary key:
for obj in orm['appname.Model'].objects.all():
obj.sort_order = obj.pk
obj.save()
### Multiple Models using Orderable
When multiple models inherit from Orderable the `next()` and `previous()`
methods will look for the next/previous model with a sort order. However you'll
likely want to have the various sort orders determined by a foreign key or some
other predicate. The easiest way (currently) is to override the method in
question.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
django-orderable-6.0.0.tar.gz
(11.6 kB
view details)
Built Distribution
File details
Details for the file django-orderable-6.0.0.tar.gz
.
File metadata
- Download URL: django-orderable-6.0.0.tar.gz
- Upload date:
- Size: 11.6 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 98167c132e2e007c8f1551242d379a802defa1454531bda51ed30180e7e1acb1 |
|
MD5 | 936dfd8124e4f93976067a4caf368db0 |
|
BLAKE2b-256 | ab4d0242b29a2c976e0cbe07e569246e43292044a6f5c0f91967fb880fd951ab |
File details
Details for the file django_orderable-6.0.0-py2.py3-none-any.whl
.
File metadata
- Download URL: django_orderable-6.0.0-py2.py3-none-any.whl
- Upload date:
- Size: 17.5 kB
- Tags: Python 2, Python 3
- Uploaded using Trusted Publishing? No
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 75164e5be32f8f1cd7885ebc22278f365441497ae8871036808a49b177f05d4d |
|
MD5 | a3d3f8c222f5636ab919769595325da9 |
|
BLAKE2b-256 | fb0f87458b9176fcbe290f364653fbed5374091102c235c91dfa552ef5c04d91 |