A popup field for django which can create\update\delete ForeignKey and ManyToManyField instance by popup windows.
Project description
## django-popup-field
A popup field for django which can create銆乽pdate銆乨elete `ForeignKey` and `ManyToManyField` instance by popup windows.
### Requirements
- Python3
- Django
### Demo
You can get this demo at [popup.yinkh.top](http://popup.yinkh.top)
![popup demo](https://www.yinkh.top/media/summer_note/20180515-170605-512.gif)
### TODO
- internationalization
- optimize action in form
- css override
### QuickStart
1. Install `django-popup-field` with pip:
pip install django-popup-field
2. Install the dependencies `django-popup-field` to `INSTALLED_APPS` in your project's `settings.py`:
INSTALLED_APPS = [
...
'popup_field',
...
]
3. Assume I have a post app which `models.py` is:
class Category(models.Model):
name = models.CharField(max_length=255, verbose_name='name')
...
class Tag(models.Model):
name = models.CharField(max_length=255, verbose_name='name')
...
class Post(models.Model):
title = models.CharField(max_length=255, verbose_name='title')
category = models.ForeignKey('post.Category', related_name='post_category', on_delete=models.CASCADE,
verbose_name='category')
tags = models.ManyToManyField('post.Tag',
verbose_name='tags')
...
New `popups.py` in post app,the content is:
from popup_field.views import PopupCRUDViewSet
from .models import *
class CategoryForm(forms.ModelForm):
class Meta:
model = Category
fields = ['name']
class TagForm(forms.ModelForm):
class Meta:
model = Tag
fields = ['name']
class CategoryPopupCRUDViewSet(PopupCRUDViewSet):
model = Category
form_class = CategoryForm
template_name_create = 'popup/create.html'
template_name_update = 'popup/update.html'
class TagPopupCRUDViewSet(PopupCRUDViewSet):
model = Tag
form_class = TagForm
template_name_create = 'popup/create.html'
template_name_update = 'popup/update.html'
4. Change widget for category and tag used in `forms.py`:
from django import forms
from .popups import CategoryPopupCRUDViewSet, TagPopupCRUDViewSet
from .models import *
class PostForm(forms.ModelForm):
class Meta:
model = Post
fields = ['title', 'category', 'tags']
widgets = {
'category': CategoryPopupCRUDViewSet.get_fk_popup_field(),
'tags': TagPopupCRUDViewSet.get_m2m_popup_field(),
}
5. Custom your popup template, `popup/create.html`:
{% extends "popup/base.html" %}
{% block css %}
{% endblock %}
{% block js %}
{% endblock %}
{% block main %}
<div class="layui-container" style="margin: 4px">
<form class="layui-form" enctype="multipart/form-data"
action="{{ request.path }}{% if to_field %}?to_field={{ to_field }}{% endif %}"
method="post">
{% csrf_token %}
{{ form.media }}
{{ form }}
<div class="layui-form-item">
<div class="layui-input-block">
<button class="layui-btn">Add</button>
</div>
</div>
</form>
</div>
{% endblock %}
`popup/update.html`:
{% extends "popup/base.html" %}
{% block css %}
{% endblock %}
{% block js %}
{% endblock %}
{% block main %}
<div class="layui-container" style="margin: 4px">
<form class="layui-form" enctype="multipart/form-data"
action="{{ request.path }}{% if to_field %}?to_field={{ to_field }}{% endif %}"
method="post">
{% csrf_token %}
{{ form.media }}
{{ form }}
<div class="layui-form-item">
<div class="layui-input-block">
<button class="layui-btn">Edit</button>
</div>
</div>
</form>
</div>
{% endblock %}
The `object_name` inside template always is `popup`.The point is you must append `{% if to_field %}?to_field={{ to_field }}{% endif %}` in form action or keep set as `"{{ request.path }}{% if to_field %}?to_field={{ to_field }}{% endif %}"`.
6. All url for popup create\update\delete is generate by `PopupCRUDViewSet`, `urls.py` :
from .views import *
urlpatterns = [
path('', PostCreateView.as_view(), name='post_create'),
CategoryPopupCRUDViewSet.urls(),
TagPopupCRUDViewSet.urls(),
]
this will register the following urls:
path('category/', include([
path('popup/', cls.create(), name='category_popup_create'),
path('popup/<int:pk>/', cls.update(), name='category_popup_update'),
path('popup/delete/<int:pk>/', cls.delete(), name='category_popup_delete'),
])
path('tag/', include([
path('popup/', cls.create(), name='tag_popup_create'),
path('popup/<int:pk>/', cls.update(), name='tag_popup_update'),
path('popup/delete/<int:pk>/', cls.delete(), name='tag_popup_delete'),
])
### Advance
#### Set default `template_name_create` and `template_name_update`
`template_name_create` is the template used for create popup window, `template_name_update` is the template used for update popup window.
You can set default `template_name_create` and `template_name_update` in settings like:
POPUP_TEMPLATE_NAME_CREATE = 'popup/create.html'
POPUP_TEMPLATE_NAME_UPDATE = 'popup/update.html'
`PopupCRUDViewSet` will use this as default `template_name_create` and `template_name_update` if you don't have a special assignment in `PopupCRUDViewSet`.
#### Override template for `PopupCreateView` and `PopupUpdateView` in `PopupCRUDViewSet`
class CategoryPopupCRUDViewSet(PopupCRUDViewSet):
...
template_name_create = 'popup/create.html'
template_name_update = 'popup/update.html'
class TagPopupCRUDViewSet(PopupCRUDViewSet):
...
template_name_create = 'popup/create.html'
template_name_update = 'popup/update.html'
#### Override template for `ForeignKeyWidget` and `ManyToManyWidget`
If you want override template used by `ForeignKeyWidget` and `ManyToManyWidget`,you have to way to achieve this,first one is:
class PopupCRUDViewSet(object):
...
template_name_fk = 'popup/foreign_key_select.html'
template_name_m2m = 'popup/many_to_many_select.html'
second one is:
class PostForm(forms.ModelForm):
...
class Meta:
model = Post
fields = ['title', 'category', 'tags']
widgets = {
'category':CategoryPopupCRUDViewSet.get_fk_popup_field(template_name='popup/foreign_key_select.html')
'tags': TagPopupCRUDViewSet.get_m2m_popup_field(template_name='popup/many_to_many_select.html'),
}
#### Set parent class for `PopupCreateView銆丳opupUpdateView銆丳opupDeleteView` in `PopupCRUDViewSet`
You can set parent class for `PopupCreateView銆丳opupUpdateView銆丳opupDeleteView` in `PopupCRUDViewSet` like:
class IsStaffUserMixin(AccessMixin):
"""
request must be staff
"""
raise_exception = True
permission_denied_message = 'You are not a staff'
def dispatch(self, request, *args, **kwargs):
if not request.user.is_staff:
return self.handle_no_permission()
return super(IsStaffUserMixin, self).dispatch(request, *args, **kwargs)
class CategoryPopupCRUDViewSet(PopupCRUDViewSet):
model = Category
form_class = CategoryForm
parent_class = IsStaffUserMixin
class TagPopupCRUDViewSet(PopupCRUDViewSet):
model = Tag
form_class = TagForm
parent_class = IsStaffUserMixin
The usage is set common permission check for `PopupCreateView銆丳opupUpdateView銆丳opupDeleteView`. In demo we will check whether the operator is a staff.
#### Permission check for create銆乽pdate銆乨elete button
You can set `permissions_required` in `CategoryPopupCRUDViewSet` for different operation, if the operator don't has corresponding permissions,then the corresponding button will be hide and the corresponding view will ask this permission when operation.
If you want check permissions for popup fields, demo is here:
`popups.py` should like:
class CategoryPopupCRUDViewSet(PopupCRUDViewSet):
model = Category
form_class = CategoryForm
template_name_create = 'popup/create.html'
template_name_update = 'popup/update.html'
permissions_required = {
'create': ('post.add_category',),
'update': ('post.update_category',),
'delete': ('post.delete_category',)
}
`views.py` should like:
class PostCreateView(CreateView):
raise_exception = True
form_class = PostForm
template_name = 'post/create.html'
success_url = reverse_lazy('post_create')
def get_form_kwargs(self):
kwargs = super(PostCreateView, self).get_form_kwargs()
kwargs['request'] = self.request
return kwargs
The `request` kwarg passed to `form` is used for perms check.
`forms.py` should like:
class PostForm(forms.ModelForm):
def __init__(self, *args, **kwargs):
request = kwargs.pop('request')
super(PostForm, self).__init__(*args, **kwargs)
self.fields['category'].widget.request = request
self.fields['tags'].widget.request = request
...
#### Custom context for create and update
class CategoryPopupCRUDViewSet(PopupCRUDViewSet):
model = Category
form_class = CategoryForm
context_for_create = {'operation': 'create'}
context_for_update = {'operation': 'update'}
#### Custom popup title and url name
The default popup title is `operation+model's verbose_name`,you can custom `model's verbose_name` with:
class CategoryPopupCRUDViewSet(PopupCRUDViewSet):
class_verbose_name = 'Custom Category'
The default url name is `model name's lower case+_popup_+operation`,you can custom `model name's lower case` with:
class CategoryPopupCRUDViewSet(PopupCRUDViewSet):
class_name = 'custom_category'
### v 0.1.0
- take create銆乽pdate and delete to viewset
### v 0.1.1
- add gif and demo site
### v 0.1.2
- allow custom template_name for popup_field
### v 0.1.3
- compatible with django 1.x
- change viewset achieve logic
### v 0.1.4
- add default POPUP_TEMPLATE_NAME_CREATE銆丳OPUP_TEMPLATE_NAME_UPDATE in setting
- add template_name_fk銆乼emplate_name_m2m in PopupCRUDViewSet
- add parent_class in PopupCRUDViewSet
### v 0.1.5
- add class_name銆乧lass_verbose_name in PopupCRUDViewSet
- remove popup_name inside create and update url
- custom context for create and update
- custom popup title and url name
A popup field for django which can create銆乽pdate銆乨elete `ForeignKey` and `ManyToManyField` instance by popup windows.
### Requirements
- Python3
- Django
### Demo
You can get this demo at [popup.yinkh.top](http://popup.yinkh.top)
![popup demo](https://www.yinkh.top/media/summer_note/20180515-170605-512.gif)
### TODO
- internationalization
- optimize action in form
- css override
### QuickStart
1. Install `django-popup-field` with pip:
pip install django-popup-field
2. Install the dependencies `django-popup-field` to `INSTALLED_APPS` in your project's `settings.py`:
INSTALLED_APPS = [
...
'popup_field',
...
]
3. Assume I have a post app which `models.py` is:
class Category(models.Model):
name = models.CharField(max_length=255, verbose_name='name')
...
class Tag(models.Model):
name = models.CharField(max_length=255, verbose_name='name')
...
class Post(models.Model):
title = models.CharField(max_length=255, verbose_name='title')
category = models.ForeignKey('post.Category', related_name='post_category', on_delete=models.CASCADE,
verbose_name='category')
tags = models.ManyToManyField('post.Tag',
verbose_name='tags')
...
New `popups.py` in post app,the content is:
from popup_field.views import PopupCRUDViewSet
from .models import *
class CategoryForm(forms.ModelForm):
class Meta:
model = Category
fields = ['name']
class TagForm(forms.ModelForm):
class Meta:
model = Tag
fields = ['name']
class CategoryPopupCRUDViewSet(PopupCRUDViewSet):
model = Category
form_class = CategoryForm
template_name_create = 'popup/create.html'
template_name_update = 'popup/update.html'
class TagPopupCRUDViewSet(PopupCRUDViewSet):
model = Tag
form_class = TagForm
template_name_create = 'popup/create.html'
template_name_update = 'popup/update.html'
4. Change widget for category and tag used in `forms.py`:
from django import forms
from .popups import CategoryPopupCRUDViewSet, TagPopupCRUDViewSet
from .models import *
class PostForm(forms.ModelForm):
class Meta:
model = Post
fields = ['title', 'category', 'tags']
widgets = {
'category': CategoryPopupCRUDViewSet.get_fk_popup_field(),
'tags': TagPopupCRUDViewSet.get_m2m_popup_field(),
}
5. Custom your popup template, `popup/create.html`:
{% extends "popup/base.html" %}
{% block css %}
{% endblock %}
{% block js %}
{% endblock %}
{% block main %}
<div class="layui-container" style="margin: 4px">
<form class="layui-form" enctype="multipart/form-data"
action="{{ request.path }}{% if to_field %}?to_field={{ to_field }}{% endif %}"
method="post">
{% csrf_token %}
{{ form.media }}
{{ form }}
<div class="layui-form-item">
<div class="layui-input-block">
<button class="layui-btn">Add</button>
</div>
</div>
</form>
</div>
{% endblock %}
`popup/update.html`:
{% extends "popup/base.html" %}
{% block css %}
{% endblock %}
{% block js %}
{% endblock %}
{% block main %}
<div class="layui-container" style="margin: 4px">
<form class="layui-form" enctype="multipart/form-data"
action="{{ request.path }}{% if to_field %}?to_field={{ to_field }}{% endif %}"
method="post">
{% csrf_token %}
{{ form.media }}
{{ form }}
<div class="layui-form-item">
<div class="layui-input-block">
<button class="layui-btn">Edit</button>
</div>
</div>
</form>
</div>
{% endblock %}
The `object_name` inside template always is `popup`.The point is you must append `{% if to_field %}?to_field={{ to_field }}{% endif %}` in form action or keep set as `"{{ request.path }}{% if to_field %}?to_field={{ to_field }}{% endif %}"`.
6. All url for popup create\update\delete is generate by `PopupCRUDViewSet`, `urls.py` :
from .views import *
urlpatterns = [
path('', PostCreateView.as_view(), name='post_create'),
CategoryPopupCRUDViewSet.urls(),
TagPopupCRUDViewSet.urls(),
]
this will register the following urls:
path('category/', include([
path('popup/', cls.create(), name='category_popup_create'),
path('popup/<int:pk>/', cls.update(), name='category_popup_update'),
path('popup/delete/<int:pk>/', cls.delete(), name='category_popup_delete'),
])
path('tag/', include([
path('popup/', cls.create(), name='tag_popup_create'),
path('popup/<int:pk>/', cls.update(), name='tag_popup_update'),
path('popup/delete/<int:pk>/', cls.delete(), name='tag_popup_delete'),
])
### Advance
#### Set default `template_name_create` and `template_name_update`
`template_name_create` is the template used for create popup window, `template_name_update` is the template used for update popup window.
You can set default `template_name_create` and `template_name_update` in settings like:
POPUP_TEMPLATE_NAME_CREATE = 'popup/create.html'
POPUP_TEMPLATE_NAME_UPDATE = 'popup/update.html'
`PopupCRUDViewSet` will use this as default `template_name_create` and `template_name_update` if you don't have a special assignment in `PopupCRUDViewSet`.
#### Override template for `PopupCreateView` and `PopupUpdateView` in `PopupCRUDViewSet`
class CategoryPopupCRUDViewSet(PopupCRUDViewSet):
...
template_name_create = 'popup/create.html'
template_name_update = 'popup/update.html'
class TagPopupCRUDViewSet(PopupCRUDViewSet):
...
template_name_create = 'popup/create.html'
template_name_update = 'popup/update.html'
#### Override template for `ForeignKeyWidget` and `ManyToManyWidget`
If you want override template used by `ForeignKeyWidget` and `ManyToManyWidget`,you have to way to achieve this,first one is:
class PopupCRUDViewSet(object):
...
template_name_fk = 'popup/foreign_key_select.html'
template_name_m2m = 'popup/many_to_many_select.html'
second one is:
class PostForm(forms.ModelForm):
...
class Meta:
model = Post
fields = ['title', 'category', 'tags']
widgets = {
'category':CategoryPopupCRUDViewSet.get_fk_popup_field(template_name='popup/foreign_key_select.html')
'tags': TagPopupCRUDViewSet.get_m2m_popup_field(template_name='popup/many_to_many_select.html'),
}
#### Set parent class for `PopupCreateView銆丳opupUpdateView銆丳opupDeleteView` in `PopupCRUDViewSet`
You can set parent class for `PopupCreateView銆丳opupUpdateView銆丳opupDeleteView` in `PopupCRUDViewSet` like:
class IsStaffUserMixin(AccessMixin):
"""
request must be staff
"""
raise_exception = True
permission_denied_message = 'You are not a staff'
def dispatch(self, request, *args, **kwargs):
if not request.user.is_staff:
return self.handle_no_permission()
return super(IsStaffUserMixin, self).dispatch(request, *args, **kwargs)
class CategoryPopupCRUDViewSet(PopupCRUDViewSet):
model = Category
form_class = CategoryForm
parent_class = IsStaffUserMixin
class TagPopupCRUDViewSet(PopupCRUDViewSet):
model = Tag
form_class = TagForm
parent_class = IsStaffUserMixin
The usage is set common permission check for `PopupCreateView銆丳opupUpdateView銆丳opupDeleteView`. In demo we will check whether the operator is a staff.
#### Permission check for create銆乽pdate銆乨elete button
You can set `permissions_required` in `CategoryPopupCRUDViewSet` for different operation, if the operator don't has corresponding permissions,then the corresponding button will be hide and the corresponding view will ask this permission when operation.
If you want check permissions for popup fields, demo is here:
`popups.py` should like:
class CategoryPopupCRUDViewSet(PopupCRUDViewSet):
model = Category
form_class = CategoryForm
template_name_create = 'popup/create.html'
template_name_update = 'popup/update.html'
permissions_required = {
'create': ('post.add_category',),
'update': ('post.update_category',),
'delete': ('post.delete_category',)
}
`views.py` should like:
class PostCreateView(CreateView):
raise_exception = True
form_class = PostForm
template_name = 'post/create.html'
success_url = reverse_lazy('post_create')
def get_form_kwargs(self):
kwargs = super(PostCreateView, self).get_form_kwargs()
kwargs['request'] = self.request
return kwargs
The `request` kwarg passed to `form` is used for perms check.
`forms.py` should like:
class PostForm(forms.ModelForm):
def __init__(self, *args, **kwargs):
request = kwargs.pop('request')
super(PostForm, self).__init__(*args, **kwargs)
self.fields['category'].widget.request = request
self.fields['tags'].widget.request = request
...
#### Custom context for create and update
class CategoryPopupCRUDViewSet(PopupCRUDViewSet):
model = Category
form_class = CategoryForm
context_for_create = {'operation': 'create'}
context_for_update = {'operation': 'update'}
#### Custom popup title and url name
The default popup title is `operation+model's verbose_name`,you can custom `model's verbose_name` with:
class CategoryPopupCRUDViewSet(PopupCRUDViewSet):
class_verbose_name = 'Custom Category'
The default url name is `model name's lower case+_popup_+operation`,you can custom `model name's lower case` with:
class CategoryPopupCRUDViewSet(PopupCRUDViewSet):
class_name = 'custom_category'
### v 0.1.0
- take create銆乽pdate and delete to viewset
### v 0.1.1
- add gif and demo site
### v 0.1.2
- allow custom template_name for popup_field
### v 0.1.3
- compatible with django 1.x
- change viewset achieve logic
### v 0.1.4
- add default POPUP_TEMPLATE_NAME_CREATE銆丳OPUP_TEMPLATE_NAME_UPDATE in setting
- add template_name_fk銆乼emplate_name_m2m in PopupCRUDViewSet
- add parent_class in PopupCRUDViewSet
### v 0.1.5
- add class_name銆乧lass_verbose_name in PopupCRUDViewSet
- remove popup_name inside create and update url
- custom context for create and update
- custom popup title and url name
Project details
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distributions
No source distribution files available for this release.See tutorial on generating distribution archives.
Built Distribution
File details
Details for the file django_popup_field-0.1.5-py2.py3-none-any.whl
.
File metadata
- Download URL: django_popup_field-0.1.5-py2.py3-none-any.whl
- Upload date:
- Size: 83.6 kB
- Tags: Python 2, Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/39.0.1 requests-toolbelt/0.8.0 tqdm/4.25.0 CPython/3.6.5
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 037cd2203f8a9a3a9046e9809840e1bb88346a20e1fe1efd2900ef1d91bbcf47 |
|
MD5 | 2084b52139e0584854121bb93ccb78af |
|
BLAKE2b-256 | 152c120aeba313e8d6c164e0d5d1705b50d40968c4ba93ef07c0960c56025fa7 |