This release is a pre-release and may not be stable for production use.
A jQuery plugin for managing Django formsets
This jQuery plugin helps you create more usable Django formsets by allowing clients add and remove forms on the client-side.
The latest versions of these documents can be found on the Github web site for this application, which is located at https://github.com/mbourqui/django-dynamic-formset.
Requirements
Installation
Using PyPI
Run pip install django-formset-bootstrap
Using the source code
Make sure Pandoc is installed
Run ./pypi_packager.sh
Run pip install dist/django_formset_bootstrap-x.y.z-[...].wheel, where x.y.z must be replaced by the actual version number and [...] depends on your packaging configuration
Configuration
Add formset-bootstrap to the INSTALLED_APPS in your project’s settings (usually settings.py). This is required in order to be able to load the script from the static files of your project.
Usage
In your templates using formsets, be sure to load the static files:
{% load static %}Then include the script:
<script src="{% static 'formset_bootstrap/js/jquery.formset.js' %}" type="text/javascript"></script>Finally, set up your dynamic formset:
<script type="text/javascript">
$(function () {
$('#formset-id fieldset').formset();
});
</script>Setting up the demo project
Once you’ve got the source code, run the following commands to set up the SQLite3 database and start the development server:
::
cd demo virtualenv venv source venv/bin/activate pip install -r requirements.txt chmod a+x manage.py ./manage.py syncdb ./manage.py runserver
You can now browse to http://localhost:8000/ and view the examples.
Credits
This is a fork of django-dynamic-formset from elo80ka.
1 maintainer
Metadata
1 maintainer
Release files for django-formset-bootstrap 1.4.0.dev3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django-formset-bootstrap-1.4.0.dev3.tar.gz | 17.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_formset_bootstrap-1.4.0.dev3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.7 kB
Release files / django-formset-bootstrap-1.4.0.dev3.tar.gz
| Download URL | django-formset-bootstrap-1.4.0.dev3.tar.gz |
|---|---|
| Size | 17.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e4558b076e288f1b3e602503fd193a1ce71502c96205073a4ace964f1f05f095
|
|
BLAKE2b-256 checksum How to use checksums |
e521cf97a7c7758b8590f51cffafacba3bf22d5e9cf89267b200435c2d22d768
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.19.1 setuptools/39.1.0 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.5.2
|
Release files / django_formset_bootstrap-1.4.0.dev3-py3-none-any.whl
| Download URL | django_formset_bootstrap-1.4.0.dev3-py3-none-any.whl |
|---|---|
| Size | 15.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3a98132f15342e176e734af583024b5d3e0ed7bc78724d1e2bc21d4937d83af7
|
|
BLAKE2b-256 checksum How to use checksums |
c3b87563799072148fc9300bb4e9869af0faacc1203f76d4df8ebcf3343a8c07
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.19.1 setuptools/39.1.0 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.5.2
|
Security for django-formset-bootstrap 1.4.0.dev3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
